Link Protector automatically forwards URL parameters from the Entry Link to the Protected Link or Termination Link. This allows tracking values (e.g., RID=, PID=, utm_source= ) to pass through without additional forwarding setup in dtect. The sending platform must still populate any values required by the destination.
Correct placement of URL parameters is required to ensure IDs are captured properly.
How It Works
Link Protector follows one simple rule:
Dynamic URL parameters belong on the Entry Link. Static parameters may remain on the Protected Link or Termination Link.
When a participant accesses the Entry Link, dtect will:
- Redirect them to the Protected Link if they pass security checks
- Redirect them to the Termination Link if they fail security checks and blocking is enabled
- In flag-only mode, allow them through to the Protected Link even when checks fail
For either redirect destination, all URL parameters received on the Entry Link are forwarded automatically.
Link Protector does not create, modify, or overwrite parameters.
Correct Link Setup
Entry Link
This is where dynamic parameters belong.
Example:
https://link.dtect.io/entry/abc123?ID=12345
Dynamic parameters include things like:
- Participant IDs (ID, RID)
- Supplier or panel IDs
- Any value that changes per respondent
Protected Link
Use the destination URL, including any required static parameters.
Do not include dynamic parameters such as ID=, RID=, or supplier IDs.
Correct:
https://survey.example.com/start https://survey.example.com/start?lang=en&study=abc
Incorrect:
https://survey.example.com/start?ID=
https://survey.example.com/start?RID={entry.RID}Link Protector does not populate dynamic parameters saved on the destination. A blank parameter remains blank; place the populated dynamic parameter on the Entry Link instead.
Termination Link
Use the termination destination URL, including any required static parameters.
You can use either:
- The default dtect termination page, or
- A custom termination URL
Example:
https://link.dtect.io/terminate https://client.example.com/terminate?reason=security
Do not include dynamic parameters such as ID=, RID=, or supplier IDs.
Example Flow
Participant enters:
https://link.dtect.io/entry/abc123?ID=12345
Passes security checks → redirected to:
https://survey.example.com/start?ID=12345
Fails security checks with blocking enabled → redirected to:
https://link.dtect.io/terminate?ID=12345
Who Populates the Respondent ID?
The supplier or sending platform must insert each participant's ID before they arrive at dtect. Link Protector forwards the value it receives; it does not replace supplier placeholders or fill an empty ID.
If you manage both the survey and the supplier platform, you must configure both:
- Add the survey destination as the Protected Link in dtect.
- Use the dtect Entry Link as the destination in the supplier platform.
- Configure that platform to populate the exact ID parameter required by the survey, including capitalization.
- Test from the supplier platform and verify the incoming and redirected IDs.
A parameter name, a supplier placeholder, and a populated value are different:
-
RIDis a parameter name. - A supplier placeholder is a token the sending platform replaces with a participant's ID. Its syntax depends on the platform and integration.
-
RID=test001contains an actual test value.
A blank ?RID= identifies the parameter but is not a complete live-traffic configuration. Sharing it with a supplier requires the supplier to configure how the value will be populated.
Configuring the Entry Link in the Sending Platform
Use the generated dtect Entry Link as the sending platform's destination. Configure that platform to populate the respondent-ID parameter required by the survey.
Some platforms use a placeholder in the URL; others provide a field or mapping setting. Follow the sending platform's documentation or ask its support team to confirm the configuration. There is no universal placeholder syntax.
In this example, the survey requires uppercase RID. Other surveys may require a different name. By the time a participant reaches dtect, the parameter must contain the actual ID, not an empty value or unresolved placeholder.
For a survey that always requires list=114, keep that static value on the Protected Link:
https://survey.example.com/start?list=114
Do not also add list=114 to the Entry Link. If the list value changes by supplier, supply it on the Entry Link instead and remove the fixed value from the Protected Link.
When the sending platform launches a participant, the URL arriving at dtect should contain an actual value:
https://link.dtect.io/entry/YOUR_LINK_PROTECTOR_ID?RID=participant123
The resulting survey URL should contain the same value:
https://survey.example.com/start?list=114&RID=participant123
Do not copy placeholder syntax from another platform without verifying that your sending platform supports it. A literal placeholder reaching the survey is not a unique participant ID.
Testing Before Launch
Manual forwarding test: Open the Entry Link with a fresh test value, such as ?RID=test001. Check that the same value appears in the redirected URL and that the survey accepts it. This verifies forwarding for that test, not automatic supplier substitution.
Supplier configuration test: Launch two separate test participants from the sending platform. Verify that each arrives at dtect with a populated ID, that the two IDs differ, and that each is preserved in the redirect and accepted by the survey.
Opening a URL template directly in a browser does not perform the sending platform's ID substitution.
In the export, compare dtect Entry Link, Entry Link Data, and Redirected Link for the same session. Check the survey record separately. An allowed status or recorded redirect does not establish that the survey accepted the ID or that the participant progressed or completed.
Common Issues
Missing ID: If the incoming Entry Link contains a blank ID, check the sending platform's configuration. If the ID is populated on entry, compare it with the redirected URL and check for a blank dynamic parameter already saved on the destination.
Literal Placeholder or Duplicate-ID Error: If the survey receives the same placeholder text for multiple participants, check supplier substitution. Do not treat those values as unique IDs or disable survey duplicate checks as a fix.
Different Parameter Name: If an ID appears under another name, such as participant_id, confirm what it represents before changing the supplier mapping or survey configuration. Link Protector does not rename it to RID.
Repeated Static Parameter: If a redirected URL contains list=114 twice, check whether it was included on both the Entry Link and Protected Link. Keep it in one location.
Survey Error After Redirect: Check the survey's error and required inputs. A recorded redirect alone does not prove successful survey entry.
Key Takeaways
- Dynamic URL parameters belong only on the Entry Link
- Protected and Termination links should remain static
- Link Protector automatically forwards parameters to the redirect destination selected by the security checks and blocking configuration
- No dtect substitution placeholders are required for forwarding. The sending platform may require its own placeholder or ID configuration.
- Confirm automatic ID population through supplier-launched tests before launch.
Comments
0 comments
Article is closed for comments.