What is the Quantcast Easy Tag?
What data does the tag collect?
What do you do with my data?
Your data is used for your campaign and insights. We do not share or sell your audience with any other advertiser. Rather, the data is used to understand what makes your online audience unique compared to the rest of the internet population.
How long do you keep information from an individual cookie?
We will continue to capture data on a cookie until it is cleared or it expires. Expiry for our first and third party cookie is 13 months. When it comes to your campaign, we use the freshest data only looking back 45-days for modeling.
Why do I need to supply additional information (data passback) such as User ID variable?
We highly recommend populating the User ID variable to take full advantage of Quantcast capabilities, achieving higher accuracy with audience insights on people visiting your website, and higher targeting precision and efficiency across retargeting campaigns.
With the UID parameter, you can send us customer identifiers along with your pixel events. Quantcast’s code immediately applies a one-way hash to your user identifier passed before it is transmitted back to Quantcast’s servers. As a result, Quantcast will never see the actual value of your user identifier. Please note that Quantcast does not use or collect any Personally Identifiable Information (PII) protecting users’ privacy. More info within our data passback guide here.
Does the tag slow down my site?
No, the tag will not affect the load time of your site. The tag loads asynchronously, or independently, of your page load. If for any reason the tag didn’t load, or loaded slowly, your page would load normally.
- Ensures accurate traffic measurement, specifically, uniques
- Allows you to configure rules to capture different activity on your site (e.g., a visit to the homepage)
- Automatically captures data in open graph labels
- Honors consent managers like Quantcast Choice or any IAB Europe Framework CMP for setting first and third party cookies
- Is compatible with the flow of user consent needed under GDPR when sent from a CMP using the IAB Europe Transparency and Consent Framework
How do I implement my tag?
There are multiple ways to implement the tag. The tag can be implemented directly on your site between the <body> … </body> HTML markers. You can also implement the tag within a container tag such as an Adserver, Tag Manager, or Platform (platform-specific implementation guides). If the platform you are using isn’t there, we are happy to help, but have limited knowledge of other vendors’ platforms. Reach out to your platform’s support team, and loop us in for any additional information.
Why do I need to supply additional information (data passback) such as orderID, revenue, and product category on the purchase confirmation tag?
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 may be shared with you to validate our conversions, and product categorization may be used to provide demographics/interest differences between various products.
Is there a preferred method to implement the tag?
No, we are agnostic about how you implement your tag. Use any method as long as the complete tag is implemented and is firing.
How can I check my tag is firing?
Use the Quantcast Tag Inspector to confirm your tag is firing accurately.
Should I change my secure tag to https:// instead of implementing the secure pixel?
There is no need for differentiating. The pixel is designed to detect the security of the page it is placed on (that’s why you don’t see http or https in the tag), and fire a secure or non-secure pixel, accordingly.
What happens if I alter/edit the tag?
Any edits to the code may result in the tag not firing. Share the reason for what you’d like to modify with us, so that we can address your concerns.
Can multiple Quantcast pixels fire on one site?
Yes, as long as they have different account ID (p-code). If you implement a tag with the same p-code, for example, an all-page tag implemented in a footer and a conversion specific tag (a common implementation practice), only the first tag on the page will fire. Make sure you put the conversion tag above the all-page tag.
I have Quantcast Measure tags on my site; do I need to place an additional tag if I want to run a campaign?
Yes, data is not shared between Advertise and Measure. You will need to implement a second tag with a different p-code across the site (see how to Implement the Quantcast Tag Directly on Your Site). If you are unsure whether you need a new tag, reach out to your Customer Team.
Do I need to implement a tag on mobile landing pages in addition to desktop landing pages?
Tagging mobile web provides more information for insights and robust data to power your campaign (now, or in the future, when you run a bundle or mobile web specific campaign). Most websites use the same page for mobile web and desktop web, so tagging can be accomplished by placing one tag. The only time you would need to implement the tag again is when you have a mobile-specific page with a distinct URL (e.g., m.yoursite.com). Check with your web developer or Ad Operations team; they will be familiar with our mobile implementation process.
If a mobile device or web browser has 3rd-party cookies blocked, will we track the cookie?
No, while you will see the Quantcast tag fire, a third party cookie will not be set. Thus, we will not track the cookies or use it in modeling.
Can I tag my Facebook Fan Page?
Unfortunately, no, Facebook does not allow a Quantcast tag on your Facebook-owned fan pages. Alternative options to tag Facebook include Instant Ads, Apps, or adding a pixel to the Facebook button on your websites.
What pages should I tag to ensure the best performance on a campaign?
The more pages tagged, the better the model! Tags provide us rich data about your audience to power your campaign and provide insights. We recommend tagging all pages the site. If that is not possible, we request tagging the conversion event, conversion funnel (e.g., checkout pages), and homepage.
I implemented my tag and do not see it firing. How do I troubleshoot?
First, make sure you have a pixel detection tool. We recommend using the Quantcast Tag Inspector. The tool allows to easily see whether the tag is firing, and which label is being captured. Once the detection tool is enabled, follow these steps:
- Confirm the tag has been moved to production (your live site, not staging).
- Give it some time. It may take a few minutes for the tag to begin firing, and up to 15 minutes to see a label.
- Check that the tag has not been modified by checking the source code if implemented directly on the site, or by accessing the 3rd party container tag. Any modification may cause the tag to not fire.
If these steps do not resolve the problem, connect with your Customer Team.
I implemented the tag. Why don’t I see any data in my account?
It will take 24 to 48 hours after placing a tag for your data to populate into your account, depending on traffic volume. If you see the tag firing using the Quantcast Tag Inspector, check back in a day or two to see your insights.
I checked my tags. Why is there a default label?
The default label is used to capture data from your site that does not have a label name (e.g., Homepage, Product Pages, Newsletter sign up) specified. This is not a bad thing, and does not harm your campaign or insights. It is there as a catch-all for your site traffic. If you would like that page/section to have a different title, let your Customer Team know.