Tracking 0% responses for website intercept surveys

Hi,

Have you also considered the metrics coming from the intercept itself? You have number of impressions (number of time your intercept has been seen) and clicks (number of time the visitors have interacted with the intercept by clicking on it. Closing it does not count as a click). You can see these metrics in your intercept project but you can now also use them as a dashboard source to view the data as you want to see it in dashboards.

As for your survey, if you record partial responses (via the options in your survey) you would be able to use the variable ‘’Finished’’ which will be equal to 1 if the survey is completed. You could also use the variable ‘’Progress’’ to see the % of completion of the survey for each respondent. 

Hope this helps!

Hi Alexandre,

Thanks for the response.  Let me clarify the challenge.

We need user‑level response records for “survey seen,” not just aggregate intercept metrics. Intercept impressions/clicks are helpful for volume, but they don’t create individual records we can join to Adobe Analytics reporting flows.

“Finished” and “Progress” only exist after a response is created. Our issue is:

• User sees survey and closes immediately → no response created
• User interacts but closes before clicking Next → no response created

So there’s nothing to record Finished=0 or Progress=0%.

Question: Is there any supported way to create a response on survey load, so we can capture “survey seen” at the user response level? If not, is there another recommended approach for user‑level funnel tracking?

Thanks again for your help. 

Hi ​@Vinay Kumar - One option to explore is to repurpose the Q_PopulateResponse and Q_PopulateValidate fields that are typically only used with inline questions in email distributions.

When distributing emails with an inline question, the standard is to use the ChoiceLink piped text fields which outputs to your survey link with these two additional fields on them.

• Q_PopulateResponse is set to the question ID + value that should be auto-filled in the survey when clicking on that link (ie auto-fill an NPS question with a 10 when clicking on the 10 button in an email).
• Q_PopulateValidate is set to 1 in the URL, which I have found is what makes inline question survey links save the response even when the customer does not progress past the first page.

I have done a little bit of testing and you can recreate this functionality outside of email distributions by just manually inserting those two fields in your URL. For example, you can take a test survey and append this onto your anonymous URL: “?Q_PopulateResponse=%7B"QID1":"10"%7D&Q_PopulateValidate=1”

Assuming your QID in the test survey is an NPS question, this will auto-fill the NPS question to a score of 10. Even if you don’t press next to go to the next page or submit the survey, the response will still be saved. This is because Q_PopulateValidate is set to 1. You can test this by manually closing out the partial survey response and seeing that it saves the response.

As you are doing this in a digital intercept this may complicate things, but you could try passing through the Q_PopulateResponse and Q_PopulateValidate in as embedded data, or by using a custom survey URL in your web intercept configuration. If that works, you may then need to hide the pre-populated question with display logic or a more custom solution. I hope this helps!

Hi,

I don’t know what the traffic is on your website or what your intercept’s display logic criteria are, but you’ll most probably end up with a very large number of recorded surveys if you choose to create a response for every survey seen. Keep in mind that they will all count against your license usage.

Hello ​@jake_dufinetz,
 

Thanks for the detailed suggestion. Since we're using Website Intercepts, we don't have the option to modify the survey URL directly. I tried setting Q_PopulateResponse ({"QID16": "10"}) and Q_PopulateValidate(1) as embedded data in the survey flow before the question blocks (as you mentioned), but unfortunately it doesn't trigger the same behavior as passing them via URL parameters.

Looks like those special variables need to come in through the URL to work, and intercepts don't give us that control.
 

Thanks for the idea Jake. Do you know if there's any other way to force response creation on survey load within Website Intercepts. 

Hi ​@vgayraud,

Thanks for mentioning this, it's a valid concern we're actively thinking through.

Along with exploring the Qualtrics approach, we're also looking at an alternative: using custom JavaScript to fire Tealium tags when the survey loads/starts, sending the data to Adobe Analytics to build the funnel there (survey seen/started/completed/closed).

With this approach, since a Qualtrics response wouldn't be created for "survey seen" events, I believe it shouldn't impact our license usage - we'd only have response records for users who actually interact with the survey.

Does this sound like a reasonable approach? Thanks again for flagging the license consideration.

Hi ​@Vinay Kumar 

I think that would be a better approach yes.