Skip to main content
Quick check: Open the Real-Time Events feed (System → Events Manager) and filter by Purchase events. If you see two events with identical timestamps and order IDs, you likely have both a native pixel and the Upstack server-side integration firing for the same conversion. Likely cause: Both a client-side pixel (e.g., Shopify’s native conversion tracking or a custom script) and Upstack’s server-side integration are capturing the same purchase event. Without matching event_id values, Upstack treats them as separate events. Fix:
  1. Go to Real-Time Events and click on the duplicate purchase events. Compare their source field:
    • If one shows pixel (client-side) and the other shows webhook or server — this confirms the overlap.
  2. Recommended approach — rely on server-side only: In your Shopify admin, go to Settings → Customer events and disable any custom purchase tracking scripts that duplicate what Upstack already captures directly from Shopify.
  3. Alternative — keep both with deduplication: If you need client-side events for latency reasons, make sure your client-side purchase sends the Shopify order ID as event_id. Upstack deduplicates events sharing the same event_id within a 5-minute window.
  4. After making changes, monitor the Real-Time Events feed for 30 minutes to confirm duplicates have stopped.
Still stuck? Contact support@upstackdata.com with your Pixel ID and a description of the issue. We typically respond within a few hours.

Disable existing tracking

Turn off redundant tracking pixels and integrations to prevent duplicate events.

Disable Facebook data sharing

Disable the Facebook and Instagram Sales Channel data sharing in Shopify.

Disable TikTok data sharing

Disable TikTok Sales Channel data sharing in Shopify to prevent duplicate conversions.