Data passback is the process used to “pass back” to Quantcast data specified within your tag. This process may be used to track many different types of data about your users (e.g., customer type, product category of purchases, order ID, country, etc).
Data passback data allows us to refine optimizations, validate campaign performance, and share detailed insights. For example, revenue allows us to optimize to higher revenue purchases, order IDs can be shared with you to validate our conversions, and product categorization provides demographics/interest differences between various products. Please remember not to pass back any directly identifiable information.
Implementing Data Passback
The setup process depends on how you implement tags. Tips by implementation type:
1. Tag is implemented directly on your site:
- Note: the code your developer writes is unique to your page code. We cannot provide a generic code to pass us the information.
2. Tag is implemented in an AdServer
- Many customers are capturing additional variable within their tags. If this is the case, your AdServer has a macro that may be used to pull in the corresponding information. Check our platform-specific implementation guides. If macro information isn’t there, help can be found in your AdServer’s Help Center or from your AdServer rep.
3. Tag is implemented in a Tag Manager/Platform
- You can configure data passback within your Tag Manager/Platform UI. Check our platform-specific implementation guides. If instructions for your specific platform aren't there, help can be found in your Tag Manager’s Help Center or from your Tag Manager rep.
Example Tag Template with data passback placeholders:
- This code is a template. To customize it to your account, you will need to insert your p-code in the tag, or ask your customer team for assistance.
- The template should only include the data passback fields relevant for the site. E.g., if you will not be passing customer type, delete
- When using a Tag Manager/Platform with a Quantcast integration, you will not need the template. Further details are in our platform-specific implementation guides.
Glossary of variables (Note: OrderID and Revenue must be passed as a string, a number inside quotes, e.g., “100.00”):
- Order ID – Unique order number used to validate your campaign conversions.
- Revenue – Total amount purchased. Revenue may be used to optimize to higher value converters to drive ROAS.
- User ID – a unique customer identifier. We recommend populating the User ID variable [UID_email] to take full advantage of Quantcast capabilities such as better accuracy in your reporting to understand the impact of your ads on website conversions, increase overall ads targeting precision and efficiency across retargeting campaigns. All the values are hashed, so Quantcast will never see the actual value of your user identifier.
- Product Category (pcat) – the category of the product. (E.g., Retailer might capture: pants, shirts, or shoes to view insights for those specific categories)
- Customer – the type of customer (e.g., New vs Returning)
- Additional Information (1 & 2) – may capture any type of data that provide more details to drive campaign performance and insights. E.g., Hotels might capture: nights booked, membership type, promo code, etc.
For any questions, please contact your Quantcast Customer Team.