The Quantcast tag fires each time the page loads. While the Quantcast ad server has deduplication logic to help prevent double counting in the campaign reporting, you may still see duplicates that will inflate your reporting.
To avoid duplication, work with your web developer to make sure that:
- Users cannot access the confirmation page more than once without placing a new order. (Or if user can revisit the confirmation page, ensure the conversion tag only fires on the first visit.)
💡 Tip for tag implemented directly on the site: The Quantcast tag is totally stateless: If it’s on the page, the conversion event is getting fired. The only way around this is for the developers to implement logic for tracking transaction state. This may be accomplished by storing a unique transaction identifier in the browser (possibly via first-party cookies or local storage) and using this to determine if the Quantcast tag should be included on the page. But be cautious about storing sensitive data here and use irreversible hashes.a
- If a user is redirected to another page, e.g., booking confirmation redirects to track your order and fires the same tag. Make sure the “conversion” tag is placed on only one page.
- User cannot refresh the page. If this isn’t possible, make sure the tag is not executed on the reload/refresh of the page.