Duplicate conversions

A single purchase counted several times distorts your statistics and your advertising conversions. Here is how Kixell Tag prevents it and what you should check on your side.

Kixell Tag's safeguards

A single purchase per order: the order is marked as "tracked" as soon as the confirmation page renders. Even if the page is reloaded or revisited, the event is not sent again.
bfcache: a dedicated cookie prevents double counting on a restore from the browser's back/forward cache.

What to check on your side

The most frequent cause of double counting is a duplicate tag in Google Tag Manager.

Make sure you have not kept an old conversion tag (Google Ads, GA4, pixels) alongside the Kixell Tag configuration.
When importing the GTM container, if you chose Merge, check for the absence of duplicate tags (see Client Side GTM).
Check that a conversion identifier or a label is not entered both in Kixell Tag and in a manual GTM tag.
Use GTM's Preview mode to confirm that a single trigger occurs per purchase.