The Quantcast tag fires each time the page loads. While the Quantcast adserver has deduplication logic to help prevent double counting in the campaign reporting, you may still see duplicates that will inflate your reporting. It’s important to work with your web developer to make sure:
- User cannot access the confirmation page more than once without placing a new order OR if user can revisit confirmation page, conversion tag only fires on the first visit.
- Tip for tag implemented direct on 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--beware of storing sensitive data here; use irreversible hashes), and using this to determine if the Quantcast tag should be included on the page.
Once you have made these updates, reach out to your rep who can pull a report and confirm we are no longer receiving duplicate conversations.
Need further assistance? Please reach out to your rep.