Quick Take: Ecommerce attribution numbers never match because each platform uses different rules to assign credit, each observes a different slice of the customer journey, and multiple systems claim the same purchase at the same time. Your store’s order record is the only reliable anchor for actual revenue totals. Ad platform dashboards are built to optimize campaigns, not to generate your business P&L.
Pull up Meta Ads Manager, Google Ads, GA4, and Shopify for the same date range and you will get four different answers to the same revenue question. Each system measures a different thing, with different data, under different rules. Disagreement between them isn’t a bug. It’s the expected output of incompatible measurement systems running in parallel.
Ecommerce attribution is the set of rules a system uses to decide which touchpoint, or set of touchpoints, receives credit when a customer completes a purchase. Every platform applies its own version of those rules to its own data within its own reporting window. Shopify records the transaction. GA4 observes the browser session. Google Ads tracks interactions with its own ads. Meta Ads Manager tracks interactions with Meta’s inventory. None of these systems shares a unified ledger or resolves credit conflicts with the others.
The practical result: a single customer journey generates multiple conversion records across platforms, each technically correct within its own frame of reference. An operator who tries to reconcile dashboards by finding one “true” number is solving the wrong problem. The goal is to understand what each system is designed to report and use each one for the job it was built to do. For a detailed breakdown of how GA4 handles attribution, the Google Analytics attribution documentation covers model settings and channel grouping rules.
Attribution Windows Shift Credit Between Platforms
Attribution windows directly control how much credit each platform claims for a sale, because the window setting alone determines whether an ad earns credit for a given purchase. Changing a window changes reported performance with no change in what customers actually bought.
As of this writing, Meta’s default attribution setting covers both a multi-day click window and a short view-through window. Google Ads defaults vary by conversion action type, and data-driven attribution models further distribute credit based on observed conversion paths. GA4 applies its own data-driven model across the touchpoints it can observe within its identity graph. If a shopper clicks a Google Shopping ad on Monday, sees a Meta ad on Wednesday, and completes a purchase on Friday, Google Ads, Meta Ads Manager, and GA4 can each record a full conversion at the full order value. Shopify logs one order. The sum reported across platforms can be three or more times the actual transaction count.
Shortening a window from 30-day click to 7-day click causes a platform’s reported ROAS to drop without any change in what customers actually bought. Operators sometimes interpret window-driven drops as performance decay and cut spend in response, compounding the problem. Document your window settings before comparing performance across periods or across channels. For specifics on how Google Ads assigns credit to conversion actions, see the Google Ads conversion tracking documentation.
Double-Counting: How Every Ad Platform Claims Full Credit
Ad platforms measure independently and assign credit independently. When Meta’s pixel and Google’s conversion tag both fire on the same order confirmation page, each records a full purchase event and credits it to their own ads, without deducting anything because another platform was also present.
Field Note: Pull your store’s actual order count for any given week, then total the purchase conversions reported by each active paid channel. In most multi-channel setups, the platform sum exceeds the real order count by a wide margin. That gap represents overlapping credit claims, not pixel errors or fraud. Knowing the exact size of that gap is useful input when you run incrementality tests to find out which channel, if removed, would actually reduce orders versus which one is just claiming credit for demand that would have converted anyway.
View-through attribution amplifies the overlap. If Meta credits 1-day view conversions, any shopper exposed to a Meta ad within 24 hours of purchasing is counted as a Meta conversion, regardless of what they actually clicked. A shopper who saw a Meta ad, ignored it, and then clicked a Google Shopping ad to complete a purchase can appear in both dashboards as a full conversion. Meta records a view-through conversion. Google records a click-through conversion. Both report the full order value. Neither flags the conflict.
This isn’t platform manipulation. It’s the inherent structure of self-attributing systems. Each platform reports the value it delivered according to its own defined rules. Adding those figures together and treating the total as a business revenue metric is what generates most of the confusion operators run into.
What Shopify, GA4, and Ad Platforms Actually Measure
Shopify, GA4, Google Ads, and Meta Ads Manager were built for different jobs and overlap only partially. That structural mismatch is a core reason why ecommerce attribution numbers never match across dashboards.
| System | Primary Data Source | Attribution Logic | Best Used For |
|---|---|---|---|
| Shopify | Order records, UTM session data | Last-click on converting session UTM | Total orders, revenue, order status |
| GA4 | First-party browser cookies, Google signals | Data-driven across observed sessions | Cross-channel path analysis, on-site behavior |
| Google Ads | GCLID, GBRAID, WBRAID click IDs, modeled data | Data-driven or last-click within Google ecosystem | Google campaign optimization and bidding |
| Meta Ads Manager | FBCLID, pixel events, Conversions API, modeled data | Click-through and view-through within Meta window | Meta campaign optimization and creative testing |
GA4’s measurement depends heavily on cookie acceptance and JavaScript loading. Apple’s App Tracking Transparency framework, detailed in Apple’s user privacy documentation, restricts cross-app tracking on iOS, reducing the signal available to Meta’s pixel for purchases completed in mobile browsers. In many stores, a meaningful share of purchases lands in GA4 as “direct” or remains unattributed, not because those purchases had no marketing origin, but because the attribution chain broke before GA4 could record it.
Ad platforms compensate with modeled conversions. When raw signal is incomplete, Meta and Google estimate credit based on aggregate behavioral patterns across similar users, not individually observed paths. This is why Meta’s reported conversion volume can hold relatively stable even as iOS restrictions reduce direct pixel signal. The numbers include modeled estimates, not only directly observed events. Operators evaluating channel performance need to account for this when interpreting swings in reported ROAS, especially during periods of high iOS traffic.
Diagnosing Why Ecommerce Attribution Numbers Never Match: A Practical Setup
Discrepancies across dashboards are permanent. The fix is to design your measurement setup around that reality rather than waiting for one tool to reconcile everything.
Anchor all revenue and order reporting to your store’s order record. Shopify and equivalent order management systems record whether a transaction occurred, the exact value, and the order status. These facts don’t shift based on attribution rules or window changes. No ad platform can replicate this function reliably. Build business reporting on order-level data first, then layer attribution context on top.
Preserve ad click IDs against each order in your database or CRM. Google passes GCLID, GBRAID, and WBRAID through URL parameters. Meta passes FBCLID. TikTok passes TTCLID. Microsoft Advertising passes MSCLKID. Capturing these at the order level creates a first-party dataset connecting specific ad clicks to specific purchases without depending entirely on platform attribution models or browser cookies that may have expired or been blocked.
Implement server-side purchase events alongside browser-side pixels. The Meta Conversions API, documented at Meta’s Conversions API documentation, sends purchase signals directly from your server to Meta, improving signal quality when pixel visibility is limited by browser restrictions or consent declines. Google enhanced conversions work on the same principle for Google Ads. When both browser and server events fire for the same purchase, use a consistent event ID to deduplicate them. Without deduplication, you inflate platform conversion counts beyond the already-inflated baseline.
Use ad platform dashboards for what they were built to do: campaign optimization within their own ecosystem. Use Google Ads data to drive Google bidding decisions. Use Meta’s reported ROAS to guide Meta creative and budget allocation. Before cutting a channel because its attributed ROAS looks soft, run a holdout test for two to three weeks. In many multi-channel setups, a channel’s attributed conversions fall sharply in holdout while actual order volume barely moves. Attribution credit and incremental contribution are not the same thing, and conflating them is where most paid media budget decisions go wrong.
Quick Takeaways
- Each platform assigns credit using its own rules, data sources, and attribution windows, making cross-platform dashboard comparisons inherently misleading without a shared measurement framework.
- Summing conversions across Google Ads, Meta, and TikTok will almost always exceed your actual order count because all three can claim the same purchase independently and simultaneously.
- Your Shopify order record is the ground truth for total revenue and order volume; ad platform dashboards are campaign optimization tools, not a substitute for order-level business reporting.
- Server-side integrations with consistent event deduplication and a clean UTM schema reduce signal loss and improve the reliability of your first-party attribution dataset.
- Attribution shows which channel earned credit within its own model. Incrementality testing shows how actual purchase volume shifts when a channel goes dark, which are two entirely different measurements.
Frequently Asked Questions
- Why does Meta Ads Manager show more conversions than my Shopify order count?
- Meta records a conversion whenever a purchase falls within its attribution window after an ad click or impression. A single completed order can trigger full conversion credit in Meta, Google Ads, and TikTok at the same time because each platform attributes to itself without coordinating with the others. Summing these platform totals produces a figure well above your actual transaction count.
- What is the difference between click-through and view-through attribution?
- Click-through attribution credits a purchase only when the shopper clicked an ad before buying. View-through attribution also credits purchases following an ad impression where no click occurred. Because view-through captures any purchase made within the window after an exposure, it produces higher reported conversion counts and tends to favor platforms with broad reach and high impression volume, such as Meta.
- Which platform should serve as the single source of truth for orders and revenue?
- Your order management system, whether Shopify or another platform, holds the authoritative record of each confirmed transaction, its exact value, and current order status. That data is fixed; it does not change based on how attribution windows are configured or which credit model a platform applies. Ad platforms, by contrast, report conversion figures that overlap across channels and include modeled estimates, making them a poor foundation for business-level revenue reporting.
- How do iOS privacy changes affect what my ad platforms report?
- When iOS users decline tracking permission, Meta’s pixel and similar tags receive less direct signal about those users’ purchase behavior. Platforms compensate by estimating conversions from aggregate behavioral patterns across similar audiences. ROAS figures during high-iOS-traffic periods carry a modeled component that can’t be verified at the individual user level, making direct comparisons to pre-ATT periods unreliable.
- What is the difference between attribution and incrementality testing?
- Attribution shows which channel received credit for a conversion based on that platform’s own rules and data. Incrementality testing measures whether a channel actually caused additional purchases by withholding ads from a random segment of your audience and comparing conversion rates between exposed and held-out groups. A channel can show strong attributed ROAS while contributing little or no incremental lift, which is why attribution figures alone are not sufficient for budget allocation decisions.
