How to Calculate Blended ROAS Across Meta Ads, Google Ads, and Shopify

A blended return on ad spend report answers a simple but important ecommerce question: for every dollar spent on paid media, how much store revenue did the business generate?

The arithmetic takes one line. The reporting discipline takes more care. Shopify offers several sales metrics. Meta Ads and Google Ads each report attributed conversion value using their own measurement systems. Refunds can land in a later period. Recent Google Ads data can still be affected by conversion lag. If you mix those concepts, you can produce a polished report with a misleading number.

This guide gives you a repeatable blended ROAS formula, a worked Shopify example, a spreadsheet-ready method, and a checklist for presenting the result without double-counting revenue.

What is blended ROAS?

Blended ROAS measures the efficiency of the paid-media program as a whole. Instead of asking which platform claims a purchase, it compares actual store revenue with total included ad spend.

If your Shopify store generated $80,000 in net sales and you spent $12,000 on Meta Ads plus $8,000 on Google Ads, your blended ROAS is:

The result means the store generated $4.00 in the selected revenue metric for each $1.00 spent across those paid channels. It does not mean the store made $4.00 in profit. Product costs, fulfillment, payment fees, returns, discounts, and overhead still matter.

Blended ROAS versus channel ROAS

Channel ROAS and blended ROAS are both useful, but they answer different questions. Do not force them to match.

Google Ads describes target ROAS as the average conversion value you want for each dollar spent on ads. Its conversion values documentation also explains that the conversion value per cost column can help you monitor return. Those Google Ads numbers are useful for optimization inside Google Ads. They are not a replacement for your Shopify store revenue numerator.

Meta similarly uses event data for ad optimization and measurement. Meta's Conversions API documentation describes measurement and attribution across the customer journey. That makes Meta's attributed purchase value useful for Meta decisions, but not a store ledger.

Why you should not add Meta Ads and Google Ads revenue

A single order can have several marketing touchpoints:

1. A shopper sees a Meta video ad.
2. They click a Meta retargeting ad three days later.
3. They search for your brand and click a Google Ads result.
4. They return directly and buy a $200 product.

Meta Ads can attribute purchase value to Meta interactions. Google Ads can assign conversion value within its own conversion and attribution settings. Shopify still records one order. If you add the two platform revenue figures, you risk counting the same $200 journey twice.

For a deeper explanation, read why Meta Ads and Shopify sales numbers do not match . The rule for blended ROAS is straightforward: add spend, not attributed platform revenue.

Which Shopify revenue number should you use?

There is no invisible Shopify field called "the only correct blended ROAS numerator." Choose a revenue definition that fits the decision, write it down, and use the same definition every reporting period.

Shopify's sales reports documentation defines the relevant terms:

For many ecommerce operating reports, Shopify net sales is a clear starting point because it reflects discounts and sales reversals without treating taxes and shipping as product revenue. Some teams use total sales. Others use a custom contribution-revenue figure. Any of those approaches can be valid if the definition is explicit and consistent.

Shopify notes that returns appear as negative values on the date the return is processed. That means a monthly net-sales numerator can include adjustments for purchases made in earlier periods. This is useful operationally, but it is one reason a weekly or monthly trend matters more than overreacting to one day.

How to calculate blended ROAS step by step

Step 1: Choose one reporting period and time zone

Start with one date range, such as June 1 through June 30. Use the same time zone in Shopify, Meta Ads, and Google Ads. A midnight boundary can move spend or orders between days, which is especially noticeable in daily reports.

Step 2: Choose and label your Shopify revenue metric

Select net sales, total sales, or your documented store-level revenue definition. Put the metric name in the report title or footnote. A reader should not need to guess whether taxes, shipping, discounts, or reversals are included.

Step 3: Export Meta Ads spend

Pull Meta Ads spend for the same date range and account scope. If your business advertises from multiple Meta ad accounts, include all accounts that are intended to drive the Shopify revenue in your numerator.

Step 4: Export Google Ads cost

Pull Google Ads cost for the same period. Include all relevant campaign types and accounts. Do not accidentally include one Google account in your numerator's business scope while excluding its spend from the denominator.

Step 5: Add any other included paid-media spend

If TikTok Ads, Pinterest, affiliate commissions, creator whitelisting, or another paid channel is part of the program, decide whether it belongs in the denominator. The calculation is only as honest as its scope. If a material spend category is excluded, name the metric "Meta + Google blended ROAS" instead of presenting it as total marketing efficiency.

Step 6: Divide Shopify revenue by total included spend

Keep the raw inputs beside the calculated ratio. A stakeholder should be able to reproduce the number from the report without opening three dashboards.

Step 7: Compare with prior periods and business economics

Compare blended ROAS month over month, week over week, and against your break-even threshold. A ratio by itself is not a decision. The trend and the margin model provide the meaning.

Worked example: Meta Ads, Google Ads, and Shopify

Imagine a Shopify store reports the following results for one month:

Notice what does not happen: the report does not add $62,000 of Meta attributed value and $51,000 of Google conversion value. That would produce $113,000 of claimed platform value even though Shopify net sales were $96,000. The platform values remain valuable diagnostic metrics. They simply do not become the blended numerator.

Spreadsheet-ready blended ROAS template

A simple monthly reporting sheet can use these columns:

In a spreadsheet, the core formula is:

Is blended ROAS the same as MER?

Many ecommerce teams use "blended ROAS" and "MER" interchangeably. MER usually means marketing efficiency ratio. In common usage, both refer to a topline revenue-to-spend ratio.

The names are less important than the definition. One company may divide total sales by paid-media spend. Another may divide net sales by all marketing spend, including agency fees and creator costs. Put the formula under the metric the first time it appears in a report.

How to calculate a break-even blended ROAS

A 4.00 blended ROAS can be excellent for one store and unsustainable for another. The answer depends on contribution margin.

A simplified break-even formula is:

If your contribution margin before advertising is 35%, the simplified break-even ROAS is:

This simplified threshold is a planning tool, not an accounting statement. Decide whether product cost, fulfillment, payment fees, returns, discounts, and variable support costs are included in your contribution margin. If overhead or cash-flow constraints matter, build those into the target as well.

Seven common blended ROAS mistakes

1. Adding platform-attributed revenue

Meta Ads revenue plus Google Ads revenue is not store revenue. Use one Shopify numerator.

2. Mixing gross sales and net sales between periods

A silent revenue-definition change can make performance look better or worse without any change in the business. Add the numerator name to the report.

3. Forgetting an ad account or paid channel

Missing spend inflates blended ROAS. Review account scope before each reporting cycle, especially after expansion into a new market.

4. Comparing different date ranges or time zones

Compare the same dates. Document the time zone. Daily and weekly reports are particularly sensitive to mismatched boundaries.

5. Treating ROAS as profit

ROAS is a revenue ratio. It does not automatically subtract product cost, fulfillment, payment fees, returns, or overhead.

6. Judging recent Google Ads data before conversions settle

Google Ads documents that conversion lag affects recent data more than older data. Its conversion lag reporting guide recommends using days-to-conversion reporting and notes that recent periods can be impacted. Keep that in mind when you interpret platform-level Google Ads ROAS.

7. Ignoring returns and reversals

Shopify net sales can change when reversals are processed. Look at the monthly trend and keep a return-rate view nearby.

What should a blended ROAS report include?

A strong ecommerce report separates the store result from the platform diagnosis:

Shopify's marketing reports documentation explains that reports with a sales metric and a marketing dimension can use attribution models. That attribution view is valuable for analysis. Keep it separate from the store-revenue metric used in the blended calculation.

How often should you calculate blended ROAS?

• Daily: use as a directional pulse, not a final verdict.
• Weekly: use for budget pacing and early trend detection.
• Monthly: use for stakeholder reporting and strategic review.
• Quarterly: use alongside margin, cohort, and customer-acquisition analysis.

A monthly number is usually easier to interpret because refunds, time-zone edges, and delayed conversions have less power to distort the story. Keep the same method across periods so the trend remains meaningful.

Can ParseBase calculate blended ROAS from Meta Ads, Google Ads, and Shopify files?

Short answer: ParseBase supports Meta Ads, Google Ads, and Shopify exports, but it does not currently calculate blended ROAS from three raw exports as a one-click auto-insight. The File Transformer/Merger can calculate the ratio when each input is already summarized to one row per matching reporting period.

ParseBase is built for file-first reporting. Upload your exports, review platform-specific insights, and bring the right metrics into one presentation. With ParseBase, you can:

• Review Meta Ads performance, funnel, cost, and creative signals.
• Review Google Ads spend, ROAS, CPA, campaign, device, and search-term insights.
• Review Shopify revenue trends, orders, AOV, products, customers, and returns.
• Build a branded report that separates store outcomes from channel diagnostics.
• Ask follow-up questions in plain English and share the report as a tracked page.

How to use the ParseBase File Transformer/Merger for blended ROAS

Prepare three period-summary files with the same date grain. For example, use one row per month in each file:

• Shopify: reporting month and your chosen store-revenue metric, such as net sales.
• Meta Ads: reporting month and Meta Ads spend.
• Google Ads: reporting month and Google Ads cost.

Then use the Transformer/Merger in two passes:

1. Join the three summary files by the matching reporting-period column.
2. Create a Total ad spend column by adding Meta Ads spend and Google Ads cost.
3. Preview the merged output and confirm that each reporting period appears once.
4. Review blank spend values. Replace a blank with zero only when that channel truly had no spend in the period.
5. Use the merged output as the source for a second transformation.
6. Create a Blended ROAS column by dividing Shopify revenue by total ad spend.

The final transformed file behaves like a normal processed ParseBase file. You can review it, ask follow-up questions, use it in analytics, and add the result to a presentation.

Should you merge the raw exports directly?

Usually, no. A Shopify export can contain one row per order while Meta Ads and Google Ads exports can contain multiple campaign rows for the same day. Joining those raw files by date can create repeated matches and inflate revenue or spend. Summarize each source to the same reporting grain before joining.

Row stacking, also called a union, is useful only when files already use a compatible structure. It does not automatically reconcile Shopify revenue with ad-platform spend, attribution windows, or differently shaped exports.

If you only have raw exports today, use ParseBase to review the platform-specific insights and bring the source metrics into your report. Prepare the period-summary inputs or calculate the final ratio in a spreadsheet until an automated multi-file blended ROAS insight is available.

The point is not to collapse every dashboard into one unexplained ratio. It is to give stakeholders a clean topline number and preserve the detail needed to make the next decision.

Frequently asked questions

What is the formula for blended ROAS?

Blended ROAS equals store revenue divided by total ad spend across every included channel for the same date range. If Shopify net sales are $80,000 and Meta Ads plus Google Ads spend is $20,000, blended ROAS is 4.00.

Should I use Shopify gross sales, net sales, or total sales for blended ROAS?

Use one documented Shopify revenue definition consistently. Net sales is a useful operating choice because Shopify defines it as gross sales minus discounts and sales reversals. Total sales can also be used when your reporting policy intentionally includes taxes, duties, shipping charges, and fees. Do not switch definitions between reporting periods.

Should I add Meta Ads revenue and Google Ads revenue together?

No. Do not add Meta Ads attributed revenue and Google Ads attributed revenue to calculate blended ROAS. Both platforms can claim credit for the same customer journey. Use one Shopify store revenue number as the blended ROAS numerator and add platform spend for the denominator.

Is blended ROAS the same as MER?

Many ecommerce teams use blended ROAS and marketing efficiency ratio, or MER, for the same topline calculation: store revenue divided by total marketing spend. Naming conventions vary, so define the numerator and denominator in your report.

What is a good blended ROAS?

There is no universal good blended ROAS. The sustainable target depends on gross margin, fulfillment costs, payment fees, returns, overhead, and the mix of new and returning customers. Calculate your break-even level from your own economics.

Can ParseBase calculate blended ROAS from Meta Ads, Google Ads, and Shopify exports?

ParseBase supports all three export types, but it does not currently calculate blended ROAS from three raw exports as a one-click auto-insight. The File Transformer/Merger can help when the inputs are already summarized to one row per matching reporting period. Join the summary files, add Meta Ads spend and Google Ads cost, then divide Shopify revenue by total ad spend in a second transformation. Do not join raw order and campaign rows directly by date because duplicate matches can inflate the result.

Sources and further reading

• Shopify Help Center: Sales reports and sales metric definitions
• Shopify Help Center: Marketing reports and attribution models
• Google Ads Help: About conversion values
• Google Ads Help: About Target ROAS bidding
• Google Ads Help: Find your conversion lag reporting data
• Meta Business Help Center: About Conversions API