Avoiding double counting
How Converlay keeps every purchase counted exactly once — and how to configure Shopify’s native Meta and Google channels so they don’t double-report your conversions.
How Converlay deduplicates
Every purchase gets a stable event ID derived from the checkout, so the same order is recorded exactly once even when it is seen twice — by the storefront pixel and by Shopify’s order webhook.
Converlay’s server events also carry the browser signals ad platforms use for matching — the Meta browser ID (fbp), click IDs, user agent and IP — captured by our pixel and attached server-side. You don’t need a separate browser pixel for match quality.
Why numbers double with the native Meta app
The Facebook & Instagram sales channel reports every purchase to Meta on its own — from the browser and from its own server connection. Each app labels events with its own IDs, so Meta cannot recognize the channel’s purchase and Converlay’s purchase as the same sale, and counts both.
Meta: turn data sharing off
- In Shopify Admin, open the Facebook & Instagram app and go to Settings → Data sharing.
- Switch data sharing off. Ads, catalog and shop features keep working — only the app’s tracking stops.
- Converlay remains the single source for conversions. Events Manager numbers typically align with your Shopify orders within a day or two.
Avoid the “limited” (pixel-only) setting
Limited mode keeps the channel’s browser pixel running next to Converlay’s server events. The two apps cannot share event IDs, so Meta cannot reliably pair them — sometimes it merges them via the browser ID, often it doesn’t. Because Converlay’s server events already include the browser signals, turning data sharing fully off loses nothing and removes the uncertainty.
Google: keep one Primary conversion action
In Google Ads, open Goals → Conversions and look at your purchase conversion actions.
- If there is only one purchase action (usually from the Google & YouTube channel), there is nothing to change.
- If two exist, keep the one you want to bid on as Primary and set the other to Secondary. Google reports and optimizes on the primary only; the secondary stays visible as a cross-check.
- Never delete a conversion action — that removes its history. Secondary is the safe way to stop double counting.
Verifying who sends what
In Meta Events Manager, open your dataset and use “Manage integrations” to see every connected integration. The per-event view only splits Browser vs. Server and does not name apps.
After changing settings, allow a day or two: platform dashboards aggregate over trailing windows, so recent double counting fades gradually rather than instantly.