Platform ROAS vs Shopify revenue: how to read both without double-counting

Compare the value attributed by Google Ads or Meta with the orders and sales activity recorded by Shopify, while keeping each source useful for the decision it can support.

Published 20 October 2026 · Approximately 11 minutes

Google Ads, Meta and Shopify can report different revenue for the same period without any one report being useless. They answer different questions.

Platform purchase ROAS describes the purchase value an advertising platform attributes to its campaigns relative to that platform’s spend. Shopify records store activity through defined fields such as orders, gross sales, net sales and total sales. One is an attribution view. The other is a business record. A useful review keeps both and labels each one clearly.

The mistake is to add Google-attributed revenue, Meta-attributed revenue and Shopify revenue as though they were three separate pools of sales. The same order can appear in more than one attribution view. Read each platform inside its own decision context, then use Shopify to assess actual store activity.

Start with the decision, not one blended number

Choose the question before choosing the metric.

Decision	Primary view	Keep beside it
Which Google campaign should receive the next budget test?	Google Ads conversion value, cost and conversion value per cost for the agreed purchase action	Conversion action, attribution model, date range, currency and campaign status
Which Meta campaign or creative deserves another controlled test?	Meta reported purchase value or purchase ROAS and spend	Attribution setting, market, placement, creative and delivery context
Did the store record more orders or sales?	Shopify orders and the exact sales field selected for the store scope	Discounts, sales reversals, payment state, currency and comparison period
Is total marketing spend producing enough store revenue?	A clearly defined blended measure such as MER	Included channels, total spend, store revenue basis and margin limits
Did the business make more profit?	A contribution or profit view built from actual cost inputs	Product cost, fulfilment, shipping subsidy, fees, discounts, reversals and service overhead

Campaign ROAS does not answer the whole-store or profit question. Shopify sales do not identify which ad platform deserves credit by themselves. MER can help with a total-business question, but it should not be relabelled as a campaign’s ROAS.

Freeze the comparison rules first

Before comparing reports, write down:

the exact start and end dates, time zone and currency;
the store, country or market included;
the campaigns, channels and spend sources included;
the purchase conversion action used by each ad platform;
the platform attribution setting and reporting date basis;
whether Shopify value means gross sales, net sales, total sales or another named field;
how discounts, taxes, shipping, sales reversals and unpaid orders are treated; and
whether test orders, duplicate events or internal traffic are excluded.

If two reports use different periods, currencies or definitions, fix the scope before explaining the gap. A neat percentage built from mismatched inputs is still a weak business answer.

Keep three ledgers separate

1. Platform attribution ledger

Record each platform independently. Keep Google and Meta purchase value, spend, ROAS, campaign and conversion settings in separate rows. Do not sum their attributed purchase value and call the result deduplicated store revenue.

Use this ledger for decisions inside each platform: budget allocation, search terms, audience, placement, creative, product group or landing-page tests. A stronger platform result can justify a controlled next test. It does not prove incremental revenue or profit on its own.

2. Shopify business ledger

Record orders and sales from Shopify with the exact field names and status rules used. Keep discounts, sales reversals and payment state visible. Shopify defines net sales as gross sales minus discounts and sales reversals, while total sales also includes taxes, duties, shipping charges and fees. Its sales reports do not track the movement of payments between the store and customers.

Use this ledger to answer what the store recorded. It remains separate from the credit assigned by an advertising platform.

3. Reconciliation ledger

Put the platform and store views side by side by date and market. The goal is not to force them to match. The goal is to identify which difference changes a decision.

Useful notes include:

a known attribution-window or reporting-date difference;
orders that were reversed, cancelled or unpaid;
campaigns that changed market, product mix or offer;
missing or duplicated purchase events;
currency conversion or tax and shipping treatment;
demand captured by direct, organic, email or another source; and
a reporting limitation that remains unresolved.

Label an unexplained difference as unexplained. Do not invent a tracking cause from the size of the gap alone.

A simple duplicate-credit example

Imagine one shopper sees a Meta ad, later searches on Google and then completes one Shopify order. Depending on the active attribution settings, both ad platforms may report purchase value connected to that journey. Shopify still has one store order.

The review should retain all three facts:

Meta attributed value under its own rules.
Google attributed value under its own rules.
Shopify recorded one order under the store’s rules.

Adding the two platform values to the Shopify value would count different views of the same business event as extra sales. Use the platform views to make platform decisions and the store record to evaluate actual commerce activity.

Read disagreements as investigation prompts

If platform ROAS improves while Shopify orders stay flat, check whether the platform is claiming a different mix of existing demand, whether reversals or payment states changed, whether spend moved between channels, and whether the period is long enough for the buying cycle. The pattern does not identify the cause by itself.

If Shopify grows while platform results weaken, inspect direct, organic, email, returning-customer and offline influences, along with tracking health and reporting lag. Do not automatically assign the difference to one unmeasured channel.

If platform and Shopify results move in the same direction, the combined view is more useful, but profitability is still a separate calculation. Product margin, fulfilment, discounts, reversals and support cost can change the business value of the same revenue.

Ask these questions before an agency changes spend

Which source owns each number in the report?
Which purchase action and attribution setting are used in Google and Meta?
Which Shopify sales or order field is being reported?
How are sales reversals, cancellations, test orders and currency handled?
Are attributed values kept separate across platforms?
What business constraint is the next campaign or CRO test meant to address?
What evidence would cause the team to hold, change or stop the test?

The Pandorium e-commerce service connects acquisition, product discovery, CRO, customer support and retention while keeping platform and store outcomes labelled by source. The RIVAL4x4 case shows one dated first-party example and states the period and source basis beside its results. That case is evidence of the recorded engagement; it is not a promise that another store will produce the same outcome.

Official references reviewed

References were reviewed on 20 October 2026. Platform fields, attribution settings and report definitions can change. Verify the current account configuration and exact report fields before making a budget decision.