Meta vs Google Ads vs Shopify: Why Your ROAS Numbers Don’t Match

Meta says your ROAS was 4.2x last month.
Google Ads reports 3.8x.
Shopify shows a revenue number that reconciles with neither.
Then your lifecycle team opens Klaviyo and produces another six figures of “attributed revenue.”
At that point, the question usually becomes: Which dashboard is wrong?
Possibly none of them.
The problem is that these systems are not measuring the same thing under the same rules. Meta is trying to understand what happened after people interacted with Meta ads. Google Ads is assigning credit across interactions in Google's advertising ecosystem. Shopify records commerce activity and can separately apply attribution models to marketing interactions.
Those are different jobs.
If you treat every platform's attributed revenue as interchangeable, you can make bad budget decisions even when every dashboard is technically functioning as designed.
The goal is not to force Meta, Google, and Shopify to produce identical numbers.
The goal is to establish which system governs which decision.
Quick Answer: Why Meta and Google ROAS Don't Match
Meta and Google ROAS don't match because each platform uses different signals, attribution rules, conversion settings, and customer interactions to assign credit. Shopify then records the underlying commerce activity and can apply its own attribution methodology.
A single $150 order might legitimately appear in Meta reporting, Google Ads reporting, and Shopify marketing attribution.
Financially, however, the business still generated one $150 order.
That distinction (revenue versus attributed revenue) is the starting point for reconciling paid media reporting.
First: Revenue and Attributed Revenue Are Not the Same Thing
Actual commerce revenue answers:
What did customers buy?
Attributed revenue answers:
Which marketing interaction should receive credit for what customers bought?
Those are fundamentally different questions.
Your commerce platform, ERP, payment system, or accounting stack records transactions. Depending on the report you are using, that might mean gross sales, net sales, refunds, discounts, taxes, shipping, or another defined financial measure.
Attribution systems take those transactions or conversion events and assign marketing credit according to a model.
That is why one order can exist once financially while appearing in several marketing reports.
Suppose a customer spends $200.
Your business has one $200 transaction.
But Meta may associate the order with an earlier Meta interaction. Google may assign conversion value to a Google ad interaction. Shopify may attribute the sale to one channel under last-click reporting and another under first-click reporting.
The order has not multiplied.
The credit has.
Attribution is a model for assigning credit. It is not the accounting ledger.
That sounds obvious until leadership receives a monthly report where attributed revenue from every channel is quietly added together.
Why Meta, Google Ads, and Shopify Show Different Numbers
The most useful way to reconcile the dashboards is not to ask which one is universally correct.
Ask what each system knows and what question it is designed to answer.
Attribution & Reporting Matrix
| System | What it primarily knows | What it is trying to answer | Best used for |
|---|---|---|---|
| Meta Ads | Meta ad exposures, clicks, engagement signals, and conversion events sent back to Meta | How did Meta campaigns contribute under Meta's attribution settings? | Optimizing activity inside Meta |
| Google Ads | Supported Google advertising interactions and configured conversions | Which Google ad interactions contributed to conversions? | Optimizing Google campaigns, ads, and bidding |
| Shopify | Store sessions, referrers, customers, orders, and commerce data | How did identifiable marketing interactions relate to store sales under a selected model? | Commerce reporting and channel analysis |
| Cross-channel reporting layer | Normalized data from multiple channels | How do channels compare under the same rules? | Budget allocation |
| Finance / contribution reporting | Revenue, discounts, refunds, COGS, fees, and other costs | Did the growth produce economic value? | Profitability and capital allocation |
The conflict starts when a business uses a system built for one row of this table to answer a question from another.
What Meta Is Trying to Tell You
Meta is trying to measure and optimize performance inside Meta's advertising environment.
It observes interactions with Meta ads and combines those signals with conversion events received through mechanisms such as the Meta Pixel and Conversions API. Reported results then depend on the attribution settings and conversion signals available to the platform.
Meta's current documentation continues to distinguish attribution according to configured click-, view-, and in eligible situations engaged-view behavior.
This makes Meta's reporting operationally valuable.
If you are deciding whether Campaign A, Ad Set B, or Creative C deserves another $10,000 inside Meta, Meta's own campaign-level signals should be part of that decision.
But that does not mean Meta-attributed revenue should automatically become the company's neutral number for comparing Meta with Google, email, affiliates, organic search, or every other demand source.
Meta is useful for optimizing Meta.
That is a different job from calculating the company's definitive cross-channel contribution.
What Google Ads Is Trying to Tell You
Google Ads is solving a similar problem inside a different measurement environment.
Google's current data-driven attribution model uses advertiser conversion data to distribute credit across relevant ad interactions. Google says the model evaluates interactions including clicks and video engagements across supported Search—including Shopping—YouTube, Display, and Demand Gen advertising, then uses conversion-path patterns to determine how credit should be allocated.
Google also states that data-driven attribution is now the default attribution model for most conversion actions.
That is considerably more sophisticated than simply saying, “the final Google click gets everything.”
But sophistication does not change the scope of the question.
Google Ads is still primarily helping you understand how Google advertising interactions contributed to the conversions the system can observe and model.
That information can be excellent for bidding and campaign optimization.
It does not automatically make the Google Ads conversion-value column a neutral accounting framework for comparing Google with Meta.
What Shopify Is Trying to Tell You
Because Shopify sits close to the transaction, teams often react to conflicting platform ROAS by saying:
“Fine. We'll just trust Shopify.”
That is directionally useful but incomplete.
You need to separate Shopify's commerce data from Shopify's marketing attribution.
Shopify's reporting currently supports five attribution models for marketing analysis:
- Last non-direct click
- Last click
- First click
- Any click
- Linear
The selected model changes how marketing credit is distributed without changing the underlying order.
Shopify's documentation also explicitly notes that its “any click” model gives full credit to each clicked channel and can therefore allocate more attribution credit than the number of orders received.
That is the distinction leadership needs to understand.
Shopify can be a strong system of record for ecommerce transactions while Shopify attribution remains a model.
Its reporting does not transform marketing attribution into objective causal truth merely because the checkout happened on Shopify.
One Customer Can Legitimately Appear in Multiple Dashboards
Consider a simple customer journey.
Monday: A prospect discovers your product through a Meta ad and clicks to your site.
Wednesday: They search your brand on Google and click a paid search result.
Thursday morning: They open a promotional email.
Thursday afternoon: They return and purchase for $180.
Now look at the journey through each measurement system.
Meta has evidence that the customer interacted with a Meta campaign before converting.
Google Ads has evidence that a Google advertising interaction occurred in the conversion path.
Your email platform may connect the purchase with the email interaction.
Shopify records the order and can distribute marketing attribution differently depending on the selected model.
None of this requires four purchases to have occurred.
There was one.
$180 in commerce revenue can generate multiple versions of marketing credit.
That is why different ROAS across dashboards is not, by itself, proof that somebody broke the tracking.
The discrepancy becomes a problem when your organization does not know why the numbers differ and uses incompatible figures interchangeably.
ONE PURCHASE → MULTIPLE VERSIONS OF CREDIT
This is also why a multi-touch attribution methodology can be useful for brands that need a more deliberate framework for analyzing interactions across the customer journey. It should not, however, be confused with proving incrementality.
So Which ROAS Number Should You Trust?
There is no single ROAS number that should govern every marketing decision. The correct measurement source depends on the decision you are making.
That distinction is where most executive reporting processes break
Measurement Prioritization Framework
| Decision | Measurement source to prioritize |
|---|---|
| Which Meta campaign should we scale? | Meta's campaign-level signals plus downstream business metrics |
| Which Google campaign, query, or campaign type deserves a budget? | Google Ads measurement plus downstream business metrics |
| How much revenue did the store generate? | Commerce/accounting system under an agreed revenue definition |
| Should we move budget from Meta to Google? | Normalized cross-channel measurement— not native ROAS versus native ROAS |
| Did advertising cause sales that would otherwise not have happened? | Incrementality tests or other causal evidence where feasible |
| Is acquisition economically healthy? | Blended CAC, MER, contribution margin, payback, cohort LTV, and related financial metrics |
This gives you a useful measurement hierarchy.
Native platforms answer tactical optimization questions extremely well because they have granular information about their own ecosystems.
Their usefulness declines when the decision becomes:
“Where should the company's next $100,000 of acquisition budget go?”
At that point, comparing a 4.2x Meta-reported ROAS directly with a 3.8x Google-reported ROAS is usually an apples-to-oranges exercise.
The two numbers may have different attribution windows, conversion inclusion rules, view treatment, modeled signals, and customer journeys underneath them.
A larger number does not automatically mean a higher incremental return.
And neither number, by itself, tells you what happened to contribution margin.
This is where understanding why strong platform ROAS can still hide weak business performance becomes relevant, but that financial consequence is a separate question from the dashboard reconciliation problem addressed here.
Why You Cannot Add Meta and Google Attributed Revenue Together
You cannot safely add platform-attributed revenue because multiple systems can claim credit for the same underlying transaction. Summing those claims can create revenue that never existed financially.
Consider this illustrative example, not a benchmark:
Actual ecommerce revenue for the month:
$500,000
Platform-attributed revenue:
- Meta: $320,000
- Google Ads: $240,000
- Email: $110,000
Total marketing systems claim:
$670,000
The company did not make $670,000.
It made $500,000 under the revenue definition used in this example.
The extra $170,000 exists because attribution credit overlaps.
This is not necessarily evidence that the platforms fabricated conversions. Different systems may legitimately associate the same order with different interactions in the path.
The management error happens later, when somebody treats attribution credit as additive financial revenue.
Once that happens, budget allocation gets distorted.
A channel owner can show a strong ROAS while total acquisition efficiency deteriorates. Finance and marketing can argue over which report represents reality. Agencies can optimize toward incompatible scorecards. Leadership may shift spend toward the platform presenting the most generous version of contribution.
The issue stops being an analytics inconvenience.
It becomes a capital-allocation problem.
Before Blaming Attribution, Reconcile the Basics
Not every Meta-vs-Google-vs-Shopify discrepancy is caused by sophisticated attribution overlap.
Sometimes you are comparing reports that were never configured to reconcile in the first place.
Before redesigning your measurement architecture, audit the basics:
- Date range: Are all systems measuring the exact same period?
- Timezone: A conversion around midnight can fall into different reporting days across accounts.
- Currency: Are accounts reporting in the same currency and using the same exchange assumptions?
- Gross versus net revenue: Are you comparing gross sales in one system with net sales elsewhere?
- Taxes: Are taxes included in conversion value?
- Shipping: Is shipping revenue counted?
- Discounts: Are pre- or post-discount values being sent back to ad platforms?
- Returns and cancellations: Does the ad platform retain revenue from orders Shopify later refunds?
- Customer definitions: Are “new customer” and “returning customer” defined consistently?
- Attribution windows: How long after an interaction can a platform claim the conversion?
- View versus click attribution: Are non-click ad exposures receiving conversion credit?
- UTM governance: Are channel, source, medium, and campaign conventions actually standardized?
- Event duplication: Could browser and server-side purchase events be counted twice because deduplication is misconfigured?
- Missing events: Are some purchases never being sent back to the ad platform?
- Identity and device gaps: Can the measurement stack recognize the same customer across browsers, devices, and sessions?
Google itself notes that different account timezones can create reporting discrepancies between Google Analytics and Google Ads, which is a good example of a mundane configuration difference producing numbers that look like an attribution problem.
Do this reconciliation before buying another analytics tool.
Software cannot repair definitions your organization has never agreed on.
Build a Measurement Hierarchy, Not One Magical Dashboard
The solution is not to find a dashboard with a larger “truth” button.
You need a measurement hierarchy that separates different kinds of truth.
Layer 1: Transaction Truth
Question: What happened?
This layer should establish facts such as:
- Orders
- Gross and net revenue
- Discounts
- Refunds
- Product margin
- Customer status
- Cost of goods
- Transaction-level economics
The governing systems are typically Shopify, your ERP, payment records, and accounting infrastructure.
The important point is not that one software platform is universally superior.
It is that your organization has a documented definition of revenue that does not change depending on which marketer is presenting the slide.
Layer 2: Marketing Attribution
Question: Which interactions deserve credit?
This is where systems such as Shopify Analytics, GA4, attribution platforms, BI models, or a warehouse-driven reporting layer can help.
Your priority here is consistency.
If leadership is comparing Meta against Google, both channels need to be evaluated through the same methodology.
That does not require destroying the native platform data.
Your Meta buyer can still use Meta's reporting to optimize Meta. Your Google buyer can still use Google's conversion data to manage Google.
But executive channel comparison needs a common framework.
For brands that need more depth here, multi-touch attribution for D2C brands is the next layer of the conversation.
Layer 3: Causal and Economic Evaluation
Questions: Would this revenue have happened anyway? And was the growth profitable?
Attribution cannot fully answer either question.
Causal evaluation can include:
- Holdout experiments
- Geo tests
- Lift studies
- Other incrementality methodologies
- Economic evaluation can include:
- MER
- Blended CAC
- Contribution margin
- CAC payback
- Cohort LTV
- New-customer revenue
- Incremental contribution dollars
This creates an important operating rule:
The higher the decision moves, from ad optimization toward company-level capital allocation, the less comfortable leadership should be relying exclusively on a channel's self-reported ROAS.

What a “Single Source of Truth” Actually Means
A marketing single source of truth is not one dashboard that produces perfect attribution. It is a shared measurement framework that defines revenue, attribution, taxonomy, tracking rules, and reporting ownership consistently across the organization.
For a scaling D2C business, that usually means agreeing on:
One revenue definition.
When the CEO asks for monthly revenue, everyone should know whether the number means gross sales, net sales, recognized revenue, or another clearly documented metric.
One cross-channel attribution methodology.
Meta and Google can retain their native reporting, but budget allocation should not depend on whichever platform reports the highest self-attributed return.
Standardized measurement windows.
Teams should know the periods used for cross-channel reporting and why.
One channel taxonomy.
Paid search, branded search, paid social, affiliates, lifecycle, organic, referral, direct, and other categories should not change between dashboards.
Consistent UTMs.
Campaign naming becomes infrastructure once multiple teams and agencies depend on the data.
Reconciled transaction data.
Reporting should ultimately tie back to an agreed store and financial revenue definition.
Clear reporting ownership.
Somebody must own the definitions, QA process, and reconciliation, not merely the visualization layer.
A common executive scorecard.
Agencies and internal teams should enter leadership meetings using the same business-level metrics.
That is what makes a source of truth operationally useful.
You do not eliminate disagreement by hiding every other dashboard.
You eliminate ambiguity about what each dashboard is allowed to decide.
Signs Your Brand Has Outgrown Platform-Level Reporting
You probably need to audit your marketing measurement infrastructure when Meta and Google both claim the same transactions and nobody can explain the overlap.
The same is true when total attributed revenue repeatedly exceeds actual sales, finance cannot reconcile marketing's monthly numbers, or channel managers arrive at the same meeting with incompatible definitions of ROAS.
Other warning signs are structural rather than technical.
Budget moves depending on which agency is presenting.
Returning customers continually appear as new acquisition successes.
Branded search collects large amounts of credit after demand was created elsewhere.
Nobody can state the attribution window without opening the ad account.
Monthly reporting requires days of spreadsheet manipulation.
A performance conclusion changes when someone switches from one dashboard to another.
At that stage, adding another dashboard will rarely solve the core problem.
You need measurement governance: agreed definitions, reliable event capture, normalized channel reporting, and clear rules about which data governs which class of decision.
This is why VAM treats attribution as part of the growth infrastructure rather than a reporting widget bolted onto paid media after the fact.
The measurement system affects how you allocate capital, judge agencies, evaluate creative, forecast CAC, and decide whether growth is producing contribution margin.
The Practical Rule
If your team remembers only four lines from this article, use these:
- Use platforms to optimize within platforms.
- Use normalized cross-channel measurement to allocate across platforms.
- Use transaction and financial data to judge the business.
- Use incrementality when you need to understand causation.
Meta does not need to match Google perfectly.
Google does not need to match Shopify perfectly.
What matters is whether your organization understands what each number means before using it to make a decision.
Final Takeaway
Three dashboards showing three ROAS numbers is not automatically evidence that your tracking is broken.
It may simply mean the systems are performing three different measurement jobs.
The more important question is:
Does your organization understand why the numbers differ, and has it agreed which measurement system governs each decision?
If Meta's numbers decide how you optimize Meta, Google's numbers help optimize Google, transaction data governs revenue, and a consistent cross-channel framework governs allocation, the disagreement becomes manageable.
If every platform's attributed revenue is treated as an interchangeable version of company performance, the discrepancy becomes expensive.
You stop debating analytics methodology and start allocating real acquisition dollars using incompatible evidence.
At that point, attribution is no longer merely a reporting problem.
It is a growth infrastructure problem.
Not sure which dashboard your team should actually use for budget decisions?
If Meta, Google Ads, Shopify, and your lifecycle stack are reporting different versions of revenue, the problem may be deeper than a dashboard configuration.
VAM can audit the tracking architecture, attribution rules, revenue definitions, channel taxonomy, and reporting workflows behind your growth system: then show you where the numbers stop reconciling and which measurement layer should govern each decision.
Start with BUILD: growth architecture and execution.
Frequently Asked Questions
Why does Meta ROAS not match Shopify?
Meta and Shopify can use different signals, attribution windows, and rules for assigning marketing credit. Shopify also separates the underlying commerce transaction from the attribution model used to credit marketing channels, so the same order can appear differently across the two systems.
Why does Google Ads revenue not match Shopify?
Google Ads assigns conversion credit according to its configured conversion and attribution environment, while Shopify records the ecommerce order and separately applies its own marketing attribution models. Differences in timezones, revenue definitions, tracking, and attribution settings can widen the gap.
Can I add Meta and Google attributed revenue together?
Not safely. The same transaction can receive attribution credit from both platforms. Adding native attributed revenue can therefore double-count sales and produce a claimed marketing-revenue total greater than the revenue the company actually generated.
Which ROAS number should I use?
Use native platform ROAS for optimization inside that platform. For budget allocation between channels, use a consistent cross-channel measurement framework. For evaluating overall business performance, use transaction and financial metrics such as blended CAC, MER, contribution margin, and payback.
Is Shopify the most accurate source of truth?
Shopify is highly valuable as a record of ecommerce transactions, but Shopify marketing attribution is still model-dependent. Transaction truth and attribution truth are different: one records what was purchased, while the other decides which marketing interaction receives credit.
What is a single source of truth for marketing?
A single source of truth is a shared measurement framework with consistent revenue definitions, attribution rules, tracking standards, channel taxonomy, and reporting ownership. It does not mean forcing every advertising platform to display the same attribution number.
Recent Posts










