Duplicate GA4 Purchases: Causes & Fixes

Revenue in GA4 looks too high, purchase counts are inflated, and the numbers don't match your store's orders. Duplicate purchase events are one of the most common, and most damaging, tracking bugs, because they quietly corrupt the metric you care about most. Here's why they happen and how to stop them.

The five usual causes

• Thank-you page reloads. Fire on page load and every refresh or back-button revisit re-counts the sale.
• Two integrations. A native/app purchase tag and your own GA4 tag both send it.
• Browser + server, unaligned. A browser tag and a server event without a shared id count twice.
• Trigger fires twice. Overlapping triggers, or one that matches more than you intended.
• SPA re-render. A single-page-app confirmation that re-mounts and re-pushes the event.

Fix 1: send a unique transaction_id

This is the single most important defense. GA4 deduplicates purchases that share a transaction_id, so a refreshed thank-you page won't create a second sale, as long as the id is present and stable.

dataLayer.push({
  event: "purchase",
  ecommerce: {
    transaction_id: "T-10492",   // unique + stable → GA4 dedups repeats
    currency: "USD",
    value: 129.0,
    items: [/* … */]
  }
});

Fix 2: fire once per order

• Set the purchase tag's firing option to Once per page where an order can only happen once per page load. (Once per event won't help: a re-pushed purchase is a new event, so the tag fires again.)
• Prefer a dataLayer success event over a raw thank-you page-load trigger.
• In a SPA, guard the push so a re-render can't re-emit the event.

Fix 3: one source of truth

Pick a single integration to send the purchase, your GTM tag or a platform/app integration, never both. On Shopify especially, an app pixel plus a custom pixel is a classic double-count. Then reconcile GA4's purchase count against your store's order count.

Fix 4: align browser and server

If you send the purchase both client-side and server-side (e.g. Meta Pixel + Conversions API), give both the same event_id so the vendor recognizes them as one conversion. Mismatched ids are a silent doubling.

How to confirm it's fixed

• In Tag Assistant, complete a test order and confirm the purchase fires once.
• Refresh the thank-you page, GA4 should not add another purchase.
• Compare GA4 purchases to your store's orders for the same window; they should be close.