Live Survey Access

Open the running survey and use the live experience.

This page is for collaborators who can open the running AXP web survey. Here, live survey access means access to the public or deployed survey page, not code or repo access. The public participant entry point is alteredxproject.com. Collaborators can use alteredxproject.com/dev/ for test runs that should not count as ordinary participant data.

Custom survey links Comparison tokens Google Sheets workflow Data examples Diagrams

What live survey access lets you do

Open the current live questionnaire URL that was shared for testing.
Choose a language and walk the actual running flow.
Submit a response and reach the feedback view.
Check how wording, options, and required behavior appear in the running survey.
Use the feedback comparison controls, legend, reading guide, and share or download image actions after submission.

Live survey workflow

1
Open the current app URL.
Use the public participant link for real collection, or the dev link for collaborator test runs. Start in the running survey rather than a local or static copy.
2
Choose your language.
Check the live wording in the language that matters for the current task.
3
Complete the combined entry step.
The live app shows substance, dose, optional context, and the app-side consent checkbox together before the slider pages.
4
Answer the slider pages and optional final free-text page.
Slider order may be randomized by the current questionnaire definition. The optional q_free page, when present, is the last page before feedback.
5
Submit and review the feedback screen.
Do not stop before submit if the task depends on feedback or downstream behavior. The stored duration is measured from the context/consent step display to submit.

Custom survey links

Prefill induction and the second context field

You can share survey links that preselect the first two context fields. For Berlin Breathwork Days, use the participant link when responses should count as ordinary survey submissions:

https://alteredxproject.com/?lang=en&induction=breathwork&dose=Berlin+Breathwork+Days+2026

For collaborator testing, use the dev link. It opens the same live app with the same prefilled values, but submissions made through /dev/ are marked as test submissions and excluded from analysis:

https://alteredxproject.com/dev/?lang=en&induction=breathwork&dose=Berlin+Breathwork+Days+2026

How the link is put together

lang=en opens the English version directly. Other public language values are de and es.
induction=breathwork preselects Breathwork as the induction method.
dose=Berlin+Breathwork+Days+2026 preselects Berlin Breathwork Days 2026 in the second field.
The + signs stand for spaces in the URL.
/dev/ is only for collaborator testing. Do not share it as a participant collection link.

General participant pattern:

https://alteredxproject.com/?lang=en&induction=breathwork&dose=Your+Option+Here

General dev-test pattern:

https://alteredxproject.com/dev/?lang=en&induction=breathwork&dose=Your+Option+Here

For standard peer-comparison buckets, use canonical English tokens:

Induction: cannabis, psilocybin, alcohol, mdma
Dose: low, medium, high

Best practice: include induction whenever you include dose, because the available second-field options depend on the selected induction.

URL-prefill and feedback comparison are related but not identical. The questionnaire can accept options such as Breathwork and Berlin Breathwork Days 2026. The feedback comparison controls only show stable rows that are enabled in the comparison_tokens sheet tab.

Open participant link Open dev-test link Back to onboarding

What a submitted response stores

The questionnaire answers needed for scoring and feedback.
The questionnaire version, language, definition hash, and presented item order needed to interpret the response later.
Context values used for peer comparison, while participant-facing comparison controls remain limited to enabled stable rows from comparison_tokens.
Broad timing and operational quality metadata used to review whether the submitted response looks like a reasonable completed run.

The public guide intentionally does not publish the exact review criteria. The goal is to document that this metadata exists and is stored without exposing implementation details that would make quality review less reliable.

What the feedback screen now includes

A radial violin comparison view that uses the selected canonical induction and dose bucket.
Comparison controls populated from enabled comparison_tokens rows. The current production-enabled buckets are cannabis, psilocybin, alcohol, MDMA, and low, medium, high.
A purple self profile over the selected peer distribution, plus a legend that names the current submission and peer group.
A peer count note showing how many complete comparison profiles were used for the selected bucket.
A reading guide toggle that explains the violin, quartiles, whiskers, and median marks.
Share or download image actions for the current feedback snapshot.

What reload does

Opening or refreshing the survey page starts a new Shiny session, but the same browser tab can resume an in-progress questionnaire from session storage when the saved draft still matches the loaded definition.
The in-app questionnaire reload keeps the current session open and attempts a best-effort answer restore after the sheet definition refreshes.
If item_id values and input types stay stable, already entered values are the most likely to survive reload.
If the questionnaire structure changes, affected fields can re-render or reset, so questionnaire reload is safest before someone starts answering.

Need the big picture?

Open the diagrams when you want to connect the running survey to upstream Google Sheets edits and downstream data examples and exports.

Open diagrams Google Sheets Data examples