A high reported Meta ROAS can coexist with a weak store month. The platform may credit a different set of interactions, while the store includes discounts, refunds or other revenue treatments. This workflow reconciles the definitions first, then asks whether the economics support a budget decision. It does not equate attributed revenue with incremental profit.
Make this useful for your client. Follow the worksheet, or use the ready-to-copy task with your connected data.
Try this task in 1ClickReport → · See the product workflow →Evidence → Decision → Review
How to run the investigation
Write the revenue basis
Ask which store measure the client uses: gross sales, net sales, total sales or collected cash. Record taxes, shipping, discounts, refunds and currency treatment. A ROAS comparison is meaningless when the numerator changes silently between systems.
Match the measurement period
Align the store and ad account dates and time zones. Mark recent orders or refunds that may change. Keep store-wide revenue separate from channel-attributed revenue; a campaign should not inherit all sales just because it ran during the period.
Investigate the gap
Review the Meta attribution configuration and available purchase-event diagnostics. Inspect the destination and checkout with the store owner when collection is suspect. Use evidence to identify specific differences rather than forcing a balancing adjustment.
Return to contribution economics
Ask for margins and variable costs if the decision concerns profitability. Use approved business inputs to evaluate the next test. If those inputs are absent, state that a ROAS headline cannot answer whether additional sales make money.
Decision worksheet
Use these rows to turn the investigation into an action. Add the actual account, date range, evidence and owner before sharing it with a client.
| What you find | Interpretation | Next move |
|---|---|---|
| Refunds excluded in one report | Revenue bases differ | Compare on a documented common definition. |
| Store revenue flat, Meta credit up | Attribution or mix may explain it | Check the operational outcome before scaling. |
| Margins unknown | Profitability is unresolved | Request inputs rather than inventing a target ROAS. |
Download this worksheet (CSV) ↓
Worked example: an illustration, not a customer result
A hypothetical store spends $2,000 and Meta credits $8,000, giving reported ROAS of four. If a substantial share is refunded or the promoted product has low contribution margin, four is not a profit guarantee. The reconciliation should show the verified revenue basis and ask for the missing economics before proposing higher spend.
MAKE THIS YOUR NEXT CLIENT TASK
Run the review on your own data.
Start with one client in 1ClickReport. Connect GA4 and the relevant ad or commerce source, select the correct client and use the task below. The analyst keeps client-specific context as you work.
Read the ready-to-use task
Compare Shopify and Meta revenue for this client. Define the store revenue measure, refund and tax treatment, currency, dates and attribution settings. Explain observed differences without forcing totals to match. Ask for margin and variable-cost inputs before a scaling recommendation. Keep total spend unchanged unless separately approved.
3-day free trial · No credit card required.
- Copy the task, then create your account in the new tab.
- Finish setup and connect the relevant client data.
- Return to this page and open the task in AI Analyst ↗. Review the prompt before sending.
Missing order, CRM or application evidence must be provided by its owner. No cross-system match is assumed.
A question worth asking
Does lower Shopify revenue prove Meta is overcounting?
Not by itself. First check what each report measures and which interactions it credits. Event duplication is one possible issue, but timing, definitions and incomplete observation can also contribute.
References and method
Reviewed November 12, 2026. The decision process and worksheets are 1ClickReport’s editorial recommendations. Examples are hypothetical, not customer results. Platform behavior and access can vary; use the current native account view to verify settings.