Help Center

Prevent duplicate purchase events

Understand TrackVerity deduplication and the settings required in Shopify, Meta, TikTok, and Google.

4 min read · Updated 2026-07-22

How TrackVerity deduplicates

  • Repeated store webhooks are deduplicated by store, order ID, and event type.
  • Meta and TikTok receive the store order ID as event_id.
  • Google receives the order ID as transactionId.
  • Purchase relays wait about 15 minutes to absorb post-purchase order edits.

Shopify and Meta

Do not leave Shopify's Facebook and Instagram data sharing on Maximum while TrackVerity also sends server Purchase events. Change it to Standard and retain the browser pixel.

Shopify and TikTok

If the native TikTok channel sends server-side purchases, change it to browser-pixel-only before enabling TrackVerity's server events.

Verify the result

  1. Place one controlled order.
  2. Confirm one order in the TrackVerity Event log.
  3. Confirm the expected single purchase in each connected platform.
  4. If two purchases remain, compare their event IDs and find the second server-side source before running more traffic.

Related articles

Troubleshoot missing or failed eventsFind where the tracking path stopped: storefront script, order webhook, channel credential, or relay.Get started with TrackVeritySign in, connect your store, add an ad channel, and confirm that orders are flowing.Sign in when the email does not arriveFind the one-time code, correct a mistyped address, and request a fresh sign-in email.