When a viewer enters a Lumiere video, all the data collected from that viewer is saved in Lumiere. If a viewer enters the same video again, Lumiere will recognize that user's device and not allow the user to submit additional answers to prompted questions or change the question answers they previously submitted.

While this is critical to maintaining data security and ensuring the integrity of your video's results, it's not ideal for testing your viewer-facing video setup multiple times before sending the video out to your audience.

Luckily, Lumiere offers a few ways for you to test your video setup from the same device!

To test your Lumiere Video, we recommend the following:

Upon clicking the preview button, a new tab will open with your viewer-facing video with &preview added to the end of the URL.

This &preview flag will do 2 things:

Incoming data that is flagged as ‘Test Data’ will automatically be filtered out of your video’s Insights Dashboard, but can be filtered back in using the data filter.

See the sections below for more information on how we use these flags to optimize, and how you can use them to thoroughly test your video.

By appending &testdata to a viewer URL, Lumiere will mark any data collected during that viewer experience as a 'test' record.

All testdata records are excluded from Video Insights by default. However, users can utilize the Test Data filter on the video’s Insights Dashboard to reveal test records.

Use the ‘Test data’ filter on your video’s Insights Dashboard to view or exclude viewer responses that were flagged as ‘test data’ via their video URL

Lumiere saves viewer response data for each unique device that enters the video. To allow any one user to enter your video multiple times, you’ll need to ensure they're generating a new ViewerID each time they enter the link- ensuring they see a fresh viewer experience each time. You can do this by adding an “Incognito” flag to your video URL.

Simply type &incognito to the end of your activity URL, and a user will get a fresh viewer experience every time you enter that video from the same device.

Adding the &Preview flag to the end of your video URL has the same functionality as adding both &incognito and &testdata to the end of your video URL

Be sure that all text included in question prompts, labels, and rows is spelled correctly and uses proper grammar.

Be careful not to ask questions using verbiage that may affect how your audience will respond. Loaded questions can skew results and leave you with inaccurate or inflated data.

For example, instead of asking your audience “What did you like about this scene?”, consider asking “What did you like or dislike about this video?”. The former assumes that the audience enjoyed the video, while the latter asks the audience to identify something they liked or did not like about the video.

Make sure that your questions are appearing where and when you want them to. Question timing and positioning are especially important for Hotspot questions, where users select from highlighted areas on the screen. Miss-timed questions can leave out important context leading up to the question or provide too much information. Questions in an incorrect position can hide important video content that viewers may use to make their decisions.

Do you want to force your audience to answer some, or all, of the questions that have been added to your video? Double-check that the required status of each of your questions matches your intended setup.

Conversations are a powerful feature of Lumiere. To use it to its full potential, make sure to test your follow-up goal to ensure it’s facilitating conversations to reach your desired outcome and asking the right questions to uncover the insights you’re looking for. Don’t be afraid to make adjustments to your follow-up goal before sending your video out to the masses.

If you’ve added custom variables to your video URL for filtering purposes, be sure to check the video’s insights Dashboard filter to ensure your variables and activity link are functioning as intended. Be on the lookout for Misspelled Variable names and Misspelled/Inaccurate values, as well as missing variables and missing values.