One $500 order can look like $1,000 in platform revenue. That is the gap I want a combined Google and Meta waste report to expose before anyone moves another dollar.
Consider a shopper who sees a Meta ad, searches the brand, and buys. If the purchase falls within both platforms’ attribution windows, Meta can claim a view-through conversion and Google can claim the search click. The order is real. Adding the claims together does not create another order.
Summed platform revenue can run 20–30% above Shopify or CRM actuals. That reported range is context, not a correction factor I would apply to every account. It also does not mean the same percentage of spend is wasted.
The useful question is what happens between the dashboards: which campaigns create demand, which close it, and which keep spending without a defensible return. I use one assistant reading both accounts through groas to build one waste table, with thresholds I can check. Here is the method, the prompt, and the decision the numbers support.
Define waste before asking AI to find it
Waste is spend past an agreed threshold without the required return, after allowing for conversion lag. It is not simply a row I dislike.
I used to tell clients to pull the last month and kill anything with zero conversions. I was wrong. That rule punishes longer sales cycles and rewards branded search for closing demand another campaign created.
The platforms also use different attribution rules. Meta’s click and view windows differ from Google’s attribution settings, so placing their conversion columns beside each other does not make them comparable. I first state the purchase event, target CPA, reporting windows, and revenue source.
Then I apply platform-specific screening rules:
| Screen | Rule | What it means |
|---|---|---|
| Google search-term waste | Cost exceeds target CPA, with zero conversions after the lag exclusion | Candidate for a negative keyword |
| Google watch list | Cost approaches target CPA, with zero conversions and repeated clicks | Monitor rather than automatically exclude |
| Meta zero-conversion waste | Spend exceeds twice the ad set’s CPA target, with zero conversions | Candidate for a pause |
| Meta high-CPA test | At least three conversions, with CPA above three times the ad set average | Review as a potential loser |
The Google search-term method uses a 90-day window ending 7–14 days ago. That exclusion matters because conversions can arrive after the click and be credited back to its date. Recent spend can look worse before its conversions arrive.
The Meta method supplies the twice-target zero-conversion threshold and the three-conversion, three-times-average test. These are operating rules, not proof that every flagged row is useless. I still check relevance, tracking, and campaign context before acting.
The threshold earns a row a review. It does not earn the assistant permission to press every red button.
Pull comparable inputs, not matching-looking columns
Through groas, I have one assistant read Google search terms and keyword costs alongside Meta spend by ad set and ad, placement costs, and frequency against ROAS. I connect the accounts once; connecting Meta to ChatGPT without the CSV shuffle covers that side of the workflow.
Then I stop being the join key. What the deck calls “cross-channel synergy,” I call not exporting two CSVs and VLOOKUPing at midnight.
One assistant can assemble the evidence; it cannot make incompatible attribution rules disappear. The report must state its date ranges, exclusions, and conversion definitions before showing a total. I use the Google lag exclusion above and a Meta window that leaves out the most recent estimated days, as specified in the prompt below. Comparable does not mean pretending the windows are identical.

For Meta, I inspect the report in this order:
- Budget concentration: spend share versus ROAS share by ad set.
- Purchase-cost outliers: unusually expensive results relative to the account.
- Placements: spend and cost per result, with zero-result slices shown separately.
- Fatigue: rising frequency alongside falling ROAS, or falling link CTR alongside rising CPM.
That sequence follows the Meta audit checklist’s budget, cost, placement, and fatigue checks. Audience Network rewarded video belongs in the placement review, not on an automatic blacklist.
A default ROAS sort will not answer all those questions. Ask for the checks explicitly.
The prompt: make the assistant show its rules
I want the assistant to state its math before recommending an action. A report without visible thresholds is an opinion wearing a spreadsheet.
The figures below are illustrative inputs, not universal settings. The Google window follows the search-term filtering method; the Meta thresholds follow the zero-conversion and high-CPA method. I replace the targets with the account’s actual economics before running it.
Build one waste-review table across Google Ads and Meta through groas.
Use the last 90 days ending 14 days ago for Google search terms. For Meta, use a stated window of 30–90 days, excluding the last 3 days. Explain the chosen windows and flag any longer conversion lag that makes them unsuitable.
For this example, use a $60 Google target CPA. Flag search terms above $60 with zero conversions; watch-list terms spending $30–$60 with zero conversions and at least 3 clicks. Keep search-term detail beneath campaign and ad-group totals.
Use each Meta ad set’s stated CPA target. Flag zero-conversion ad sets only after spend exceeds twice that target. Keep high-CPA tests separate from zero-conversion waste.
Show platform, campaign, ad group or ad set, spend, conversions, target, threshold calculation, verdict, and proposed action. Separate confirmed threshold breaches, watch-list rows, and insufficient data. Do not double-count overlapping rows in the total.
Compare platform-reported revenue with CRM or backend revenue separately. Identify possible attribution overlap without presenting it as proven wasted spend.
Propose changes for approval. Do not execute them.
The hands-on Google version of this workflow covers the search-term half. This version adds Meta and the cross-platform check without quietly adding their revenue columns together.
Worked example: the table supports less than the sales pitch
Here is an illustrative report, not a client result. The Google example uses the target in the prompt; the Meta examples use the published $900-target scenarios. The placement row is a review example, not an additional saving.
| Platform / slice | Spend in window | Conversions | Threshold calculation | Verdict |
|---|---|---|---|---|
| Google search terms | $480 across 6 terms | 0 | Each term exceeds the $60 target | Review relevance; add confirmed junk as negatives |
| Google watch-list terms | $30–$60 each, with 3+ clicks | 0 | Not above the $60 target | Watch |
| Meta retargeting | $4,800 | 0 | Above twice the $900 target | Pause candidate after checks |
| Meta broad prospecting | $2,100 | 2; CPA $1,050 | Too few conversions for the high-CPA test | Hold; insufficient evidence |
| Meta Audience Network rewarded video | $640 | 0 | No finite cost per conversion to compare | Investigate; do not automatically exclude |
The defensible action set is the $480 in confirmed junk terms and the $4,800 zero-conversion ad set. The prospecting row does not become waste because its CPA looks uncomfortable. The placement row needs investigation, and it may overlap an ad set already shown. Adding it again would inflate the total.
Those two action rows contain $5,280 of spend in their respective reporting windows. That is not automatically $5,280 saved next month: the windows differ, and historical spend is not a forecast. I ask for an expected monthly saving separately, with the calculation shown.
If the row cannot name its threshold, it does not get to touch budget.

Find the gap between creating demand and claiming it
The combined table matters because a campaign can look efficient while depending on spending elsewhere. I look for these patterns:
- Overfunded closers. Branded search and retargeting can show attractive CPAs while harvesting demand created elsewhere. Cutting prospecting to feed those closers can undermine the system that makes them look good.
- Prospecting feeding retargeting. A weak-looking prospecting row may refill the audience that retargeting converts. The cross-channel attribution discussion describes retargeting CPA rising after prospecting cuts. I treat that dependency as something to examine, not a guaranteed outcome.
- Overlapping credit. A Meta view and a Google brand click can both receive credit for the same purchase. That proves overlapping claims, not that either touch was unnecessary.
Double-counted revenue is not, by itself, evidence of double-paid waste. This distinction keeps an attribution cleanup from turning into an indiscriminate budget cut.
I use consistent UTMs, a neutral reporting layer such as GA4, and CRM or backend revenue as the sales ground truth. Platform revenue stays visible, but I do not sum it and call the result business revenue.
Branded search taking a large share of Google spend while Meta prospecting frequency rises and ROAS falls deserves investigation. It does not establish which campaign caused the problem. Where appropriate, feeding CRM outcomes back through Google enhanced conversions and Meta Conversions API helps both platforms optimize against those outcomes. It does not make their attribution claims additive.
I judge closers on their incremental contribution and creators on new-customer cost. The combined report points to the question; it does not manufacture the answer.
Turn findings into approved changes
A waste table that never produces an action is a second dashboard. Every proposed change needs a reason, a scope, and approval.
I turn the reviewed rows into these moves:
- Exclude confirmed irrelevant Google queries. Propose exact-match negatives at the appropriate scope. A term that fails in one campaign does not automatically belong on an account-wide exclusion list.
- Pause qualifying Meta ad sets. Check the conversion event, lag, and threshold before pausing a zero-conversion row.
- Propose budget moves separately. Favor prospecting with the lowest supported new-customer cost, not retargeting simply because its reported ROAS is prettier.
For each move, I ask the assistant for the exact proposed command, the expected monthly saving with its calculation, and a review date. Nothing runs on autopilot for this first pass.
The approval line matters more than the automation.

Keep the reason beside the change
Every proposed fix records the number observed, the threshold applied, and who approved it. I also require reason, approved_by, and review_on in the action log.
A reversible change still needs an explanation. Native platform histories and undo options have different limits; this change-log overview describes the differences between Google and Meta histories and reversal support. I do not want the rationale scattered across those interfaces.
If a paused ad set turns out to support demand elsewhere, I want to find the decision and reverse it without a forensic dig through two platforms. Logging the action is useful. Logging why it happened is what makes the next decision better.
Know where the evidence stops—and make the smaller decision
One table is not complete visibility. Google hides some low-volume search terms for privacy, so visible query spend will not necessarily reconcile to campaign spend. That is a reporting limit, not permission to label the difference waste.
The search-term reporting limitations also affect campaign coverage: grouped insights are not interchangeable with raw queries, and Display and Video do not supply the same search-term rows. Meta audience overlap is not exposed through the API in this workflow. Similar targeting can suggest overlap; it cannot prove the same buyer was unnecessarily reached twice.
Small samples are the other trap. A couple of conversions or an ad set still in learning is not enough to justify a confident loser label. I mark insufficient evidence, consider consolidation where appropriate, and avoid turning uncertainty into an automatic pause.
For low-spend accounts, this may be more reporting machinery than the decision needs. If tracking is broken, I fix that first. No prompt makes missing purchases reappear.
The worked example supports a narrow decision: exclude the confirmed irrelevant Google terms, pause the qualifying zero-conversion Meta ad set after checks, and hold the prospecting row with insufficient evidence. Any budget transfer needs its own case. None of those decisions proves that every remaining campaign contributes to the funnel.
I run the combined report monthly through groas, with explicit thresholds and CRM revenue kept separate from platform claims. The point is not a bigger waste number. It is a smaller set of changes I can defend.
Separate reports leave the gap between platforms unexamined. One report makes it reviewable. Before buying more ads on the strength of summed Google and Meta revenue, reconcile the sales—and act only on the waste the evidence supports.

