Skip to main content

Forwarding the dtect Security Token to Your Links

Victor @ dtect
Updated

Link Protector lets you associate each dtect session with your own respondent or supplier identifiers (such as RID, UID, or PID) so you can reconcile dtect sessions with your downstream data. To do this, Link Protector can pass the Security Token (also referred to as the session ID) through to your Protected Link and Termination Link.

You add a placeholder to your link, and Link Protector replaces it with that session's Security Token at redirect time.

The Placeholder

Use the following placeholder wherever you want the Security Token to appear in your URL:

{dtect.token}

At redirect time, Link Protector replaces {dtect.token} with the Security Token for that session. This is the same value shown as the Security Token in your dashboard and CSV export, so the values will always match.

How It Works

  1. Add {dtect.token} to your Protected Link, your Termination Link, or both.
  2. When Link Protector redirects the participant, {dtect.token} is replaced with the Security Token generated for that session.
  3. The replacement happens on every redirect, whether the participant passed or was blocked.

If the placeholder is not present in your link, behavior is unchanged and nothing is added to the URL.

Example

Configured Protected Link:

<https://survey.example.com/start?dtect_id={dtect.token}>

Resolved at redirect:

<https://survey.example.com/start?dtect_id=8f3c1e2a-4b9d-4f7a-9c11-2a6e8b9f0d12>

The Termination Link behaves the same way.

Where You Can Use It

  • Protected Link - Supported.
  • Custom Termination Link - Supported.
  • The placeholder is replaced wherever it appears in the URL, so you can use it in more than one parameter if needed.

Tips

  • Keep your parameter name consistent from end to end. Decide on one variable name (for example, dtect_id) and use it the same way in your link and in your downstream system.
  • If you need to trace a specific session, match the value passed in your URL to the Security Token in the CSV export.
  • Customer-generated variables such as RID, UID, and PID still belong on the Entry Link, where Link Protector forwards them automatically. The {dtect.token} placeholder is different: because the Security Token is generated by dtect during the session, it can only be added to the Protected Link or Custom Termination Link.

Key Takeaways

  • Add {dtect.token} to your Protected Link and/or Termination Link to forward the Security Token.
  • The placeholder is replaced on every redirect, for both passed and blocked sessions.
  • The value matches the Security Token in your CSV export.
  • If the placeholder is not present, your links work exactly as before.

FAQ

Can I use {dtect.token} alongside my existing query parameters?

Yes. You can combine {dtect.token} with your own parameters in the same URL. Link Protector only replaces the placeholder and leaves your other parameters untouched.

Configured URL:

<https://survey.example.com?RID=12345&dtect_id={dtect.token}>

Resolved URL:

<https://survey.example.com?RID=12345&dtect_id=8f3c1e2a-4b9d-4f7a-9c11-2a6e8b9f0d12>

Related Articles

Comments

0 comments

Please sign in to leave a comment.