Your store, analytics and ad platforms can report different conversion totals even when each is functioning as designed. They may measure different events, use different attribution windows or place the same order on different dates. The fix starts with a shared definition, then follows the event from collection to delivery and reporting.
Three questions hidden inside one number
| Stage | Question | Useful evidence |
|---|---|---|
| Collection | Did the site or integration record the event? | Order or lead ID, event name, value and timestamp |
| Delivery | Was the event sent and accepted? | Destination status, response and retry history |
| Attribution | Which campaign gets credit? | Model, lookback window and reporting date |
A successful API request answers a delivery question. It does not prove the destination attributed the event to the campaign you expected, or that every reporting interface has finished processing it.
Align the reports before changing the tracking
Check time zone, currency, event definition, refunds, test orders and date attribution. Compare purchases with purchases and qualified leads with qualified leads. Revenue that includes tax or shipping will not necessarily match a report using a different value field.
Google documents reasons Ads and Analytics figures can differ, including the difference between clicks and sessions and the timing of attribution. See Google’s discrepancy guidance.
Look for missing and duplicated collection
Follow a known test transaction through the actual integration. Check whether the checkout generated the intended event, whether consent allowed the relevant collection and whether browser or network conditions interrupted the request. Inspect any server-side path independently.
If more than one integration reports the same action, validate deduplication. Consistent identifiers, event names and source handling matter. A second tracking script can increase duplicate reporting if it is added without a clear integration plan.
How ConversionOS helps
ConversionOS brings event collection, delivery visibility and visitor context into one workflow. Documented integration paths include Shopify, WordPress, WooCommerce, tag passthrough and a custom API. Eligible configured events can be delivered to Meta Conversions API, Google Enhanced Conversions and GA4.
Delivery health helps separate captured events from pending or failed destination requests. Fraud-aware handling uses AdProtektor verdicts in the eligible flow. Standalone True Tracking and the ConversionOS add-on provide different ways to fit conversion tracking into your setup.
More visibility, not a promise that every total will match
Destination acceptance, attribution and platform reporting remain separate. Source data, consent, integration settings and fallback behavior can affect what is available and where it is sent.
A useful reconciliation routine
- Select a small set of known orders or qualified leads.
- Match event identity, time, currency and value to your source system.
- Check the intended destination and its delivery status.
- Inspect duplicate sources and test-event handling.
- Apply the same attribution and date rules before comparing report totals.
- Classify the remaining differences: collection, delivery, attribution or processing delay.
A trustworthy conversion workflow explains where a number came from.
Explore ConversionOS or use the server-side tracking comparison to define the evidence you need from a provider.