Why Deduplication Matters
When running both browser and server-side tracking, the same conversion can be sent twice:
- Once from the Web Pixel (browser)
- Once from the CAPI (server)
Without deduplication, your conversion data would be inflated by 2x.
How TrackShift Deduplicates
TrackShift uses a multi-layer deduplication strategy:
Layer 1: Browser-Side (Web Pixel)
- Generates unique event ID using
browser.localStorage - 1-hour TTL (Time To Live)
- Same event ID sent with CAPI event
Layer 2: Server-Side
- Matches event IDs from browser and server
- Platforms recognize matching IDs
- Only one conversion counted
Event ID Format
{shopId}-{orderId}-{provider}-{eventName}-{timestamp}Example: abc123-order456-meta-purchase-1705432800000
What You See
In your ad platform, you may see:
- Web events: Counted by browser pixel
- Server events: Counted by CAPI
- Deduplicated: Combined without double-counting
—