Pass context between forms

Use a fixed destination form link with a small amount of non-sensitive query context. Verify both forms independently.

2 min read · Last reviewed

On this page

Select a screenshot to enlarge it.

Steps

  1. In the destination form, define and save the hidden fields that should receive context.
    Definitions identify the fields expected in the respondent URL. Supply harmless URL-encoded values when testing.
  2. Copy that form’s actual respondent link from Share.
  3. Configure a supported explicit link to that destination, or confirm the ending URL process first. The current logic REDIRECT_TO selector chooses an ending rather than accepting a destination URL. Use value recall only in a destination field that explicitly supports it.
    The current action selects an ending; this selector does not provide a direct destination-URL field.
  4. Preserve the destination’s required URL parameters and encode the added values.
  5. Test the source-to-destination path and a direct visit to the destination without any context.

Check before you rely on it

Passing a value does not copy a respondent record or authenticate the same person in another form.

If you need help

If redirect recall is unavailable or does not encode values correctly, use a fixed link and a supported integration rather than inventing template syntax.

Contact support with the relevant screen, time, and a redacted description. Keep credentials and private respondent information out of screenshots.

Related tasks