About Embedded Data in Website Feedback
Any information that can be tracked by Website Feedback can also be sent to your target website or target survey. For example, if your target is a website satisfaction survey, you can choose to save information about how long the participant was on the website or how many pages they visited. This information is not saved within the intercept or creative itself, but is passed over to your website or survey.
You can pass information to surveys or your site by setting embedded data. Embedded data are custom variables that can be named and set equal to any values you desire. For example, you may have an embedded data named Location that can have a value of United States, Canada, Ireland, and so on.
Setting Embedded Data
You typically specify embedded data for individual actions in your intercept. For example, let’s say you’re randomizing two different action sets. On one action you might add an embedded data field called “Condition” with a value of “Version 1,” and on another action you might add an embedded data field called “Condition” with a value of “Version 2.”
To set Embedded Data on any Action
- On any action, click Options.
- Select Embedded Data.
- Enter a name for your first embedded data field.
- Select the value type.
Qtip: A Static Value means the value of the embedded data field will be the same for each visitor who receives this action (e.g., assigning one action “Condition” with a value of 1 and the other “Condition” with a value of 2). The other embedded data value options are dynamic, meaning that they’ll adjust depending on the particular visitor (e.g., which page the visitor was viewing when they saw the creative).
- If a field is provided, enter a value for your embedded data.
- If you would like to add additional embedded data fields, click the plus (+) sign to the right of your first field and repeat steps 4–6.
- Click Save.
Multiple Embedded Data Fields
Due to browser limitations, only 2,000 characters of data may be sent to the target website. Certain fields (such as Recorded Site History) will take more of this space than others. Should there not be enough room to send all embedded data fields to the target website, fields at the top of the list will be prioritized.
You can set the priority of embedded data fields simply by clicking the dots to the left of any field and moving the item up or down the list.
Setting Embedded Data to a Creative
The steps above described how to save embedded data for a specific action. However, if you would like all actions using a given creative to have the same embedded data, you can also set embedded data on the creative itself. The steps will be exactly the same, but you’ll find the embedded data menu by right clicking on your creative’s target, clicking the dropdown arrow in the above toolbar, and selecting Embedded Data.
This can also be found in the Edit section of your creative.
<div onclick="window._qLastClicked = 'Happy';">
Embedded Data Value Types
When you set the value of your embedded data, you get to choose what kind of variable this embedded data is. Below, you’ll find an explanation of what each type of embedded data captures, and related intercept conditions.
- Static: Create a custom embedded data and define its values.
- Intercept ID: This captures the internal ID of the intercept. This ID can be used to see which intercept a visitor saw if you have multiple intercepts linking back to the same site/survey.
- Creative ID: This captures the internal ID of the creative. This ID can be used to see which creative a visitor saw if you have multiple creatives linking back to the same site/survey.
- Recorded Site History: This captures all the sites your visitor has visited that have the project code on the page. This information is stored in a cookie, which Website Feedback places on the browser.
Qtip: The amount of history recorded is dependent on limits placed on this cookie. The limit is set on the Admin page.
- Event Tracking: Allows you to set up Event Tracking.
- Adobe Analytics: See Adobe Analytics.
- Adobe Experience ID: See Adobe Analytics.
- Unique Visited Page Count: This captures the number of different pages the user visited on your site. For example, visiting the same page twice counts as one page. See Page Count Conditions.
- Total Visited Page Count: This captures the number of total pages the user visited on your site. See Page Count Conditions.
- Time Spent On Site: Time Spent On Site records two metrics: the Time Spent On Site and the Time Focused On Site. Time Spent On Site refers to how long the visitor has had your website open in a browser window. Time Focused On Site refers to how long the visitor has had your website open as the front, “in-focus” window on their computer. See Time Spent on Site or Time Focused On Site.
- Current Page URL: The page the visitor is on when the Intercept appears. See Current Page URL.
- HTML on Site: Specify the HTML on the page you want to capture the value for. For example, you may have an element for your Shopping Cart and want to know how many items are in the visitor’s cart. See HTML on Site.
- Value from Cookie: Capture the value from a specific cookie on your site. For example, you may have a cookie named return_visitor which captures whether someone has visited your site before or not. See Cookie condition.
- URL Parameter: If your website has parameters added to the URLs, this option lets you capture the value of any parameter you want.
- URL Regex: This captures Regex coding.
Qtip: Regex is a custom coding feature. Unfortunately, Qualtrics Support cannot advise you on custom coding. You can always try asking our community of dedicated users instead.
- Page Referrer: The page the visitor was on before arriving at the page with your intercept. See Page Referrer.
- Site Referrer: The website the visitor was on before arriving on your website. See Site Referrer.
- Search Term: Captures the term the visitor searched to arrive at your website. See Search Term.
Saving Embedded Data in a Qualtrics Survey
If your target is a Qualtrics survey, embedded data sent to it will be available for use in survey logic with no additional action needed. However, if you want to save this embedded data in the survey results, you’ll need to add it to your survey flow.
Follow the steps on the embedded data support page to add it to your survey flow.
Using Embedded Data with Other Targets
Even if your target isn’t a Qualtrics survey, you can still leverage embedded data and pass the information over, just as you would with a Qualtrics survey. The embedded data will be passed in the request body (POST method), so that you can capture and send multiple embedded data elements to the Qualtrics XM platform without having to see them in the visible survey URL.