We often incorporate Lumière activities into larger surveys, and it’s a great way to use the software. If you’re linking out to Lumière activities from survey software (or an email campaign) and want to be able to track specific people, you’ll need to take a few steps to ensure that your survey participants are correctly tagged, which will help us associate your survey data and Lumière data later. If you’re not planning to upload additional panel data, this probably doesn’t isn’t something you’ll need to do.
To include a participant identifier in your links to Lumiere, you can append a participant id to the activity URL:
For example, to invite someone with an id of ’103′, your URL might look like:
Participant identifiers can be any combination of letters, numbers and symbols (only ‘@’, ‘_’, ‘-’, and ‘.’) up to a total of 50 characters in length.
See Getting participants into your activities to learn how to find your Activity URL.
You have two options for customizing where participants are sent after they complete your activity.
If you want to redirect all participants to the same URL, you can configure it under the Panel Management tab on the Activity Setup page.
If you want to customize the redirect location for each participant (if there are unique identifiers that you want to include in the URL, for example), you can pass a customized redirect URL in as part of the activity invitation link:
For example, to redirect a participant with id 103 to http://lumiere.is on activity completion, your invite URL might look like:
An important note on encoding redirect URLs:
Note the encoded special characters in the following redirection url:
If you want to test your passthrough integration and links, you can append an additional &is_test=true variable to your activity links. This will allow you to enter the activity in preview mode, even if the activity hasn't been launched yet.
IMPORTANT NOTE: Make sure to remove the test variable from your links before sending participants into your survey, otherwise they will be flagged as test sessions and their data won't be included in outputs!