google-adspaid-acquisitionmeasurement

The paid-acquisition audit: eight detectors for profit leaks attributed ROAS hides

Audit paid acquisition in eight passes to find profit leaks without treating platform-attributed ROAS as incremental profit.

The short version

Do not start a paid-acquisition audit by ranking campaigns on platform ROAS. First prove that purchase values, refunds and transaction IDs reconcile to commerce; then use eight detectors to find the largest decision-changing leak.

Keep three ledgers separate: platform attribution, analytics attribution and canonical commerce. Only attach profit, customer status or lifetime value to campaigns, products or queries when a measured click-to-order or transaction bridge supports the join.

Build the evidence base before diagnosing performance

Use a closed reporting window older than the normal conversion-lag tail. Record account IDs, currencies, time zones, attribution windows, conversion-time versus interaction-time reporting, campaign types, bidding goals and material change-history events.

Then inventory every conversion action used for bidding. For each purchase action, check:

  • primary or secondary status;
  • count method;
  • dynamic value and ISO currency coverage;
  • transaction-ID presence and uniqueness;
  • duplicate imports;
  • refund and cancellation adjustments;
  • reconciliation to canonical orders in a closed period.

Define the economic measure before calculating it. Net item revenue after discounts and refunds is not contribution profit. Call a measure “contribution after media” only when it includes all material variable costs and ad spend; otherwise name exactly what is included.

Finally, measure bridge coverage. Canonical margin, refunds, new-customer status and LTV can be assigned to a campaign, advertised product or query only through a unique click/order or transaction key. Report unmatched spend and orders instead of silently dropping them.

Detector 1: bidding objective and measurement mismatch

Build one row per campaign, selected goal and conversion action. Flag campaigns bidding toward duplicate purchases, micro-events, static values, stale actions, wrong currencies, missing transaction IDs or gross sales that never receive refund adjustments.

A configuration defect can be the main finding even when its exact financial effect is unknown. State the affected spend, the decision it can distort and the retest that proves the repair; do not invent an uplift.

Detector 2: advertised product versus sold-product profit

Shopping and cart-data reports can show which product was advertised and which products were sold, but those values remain platform-attributed. Join canonical sold line items, COGS, refunds and contribution only through the measured bridge.

Look for two inversions:

  • high attributed ROAS that becomes weak or negative after returns and COGS;
  • low attributed ROAS that acquires high-margin baskets or valuable repeat customers.

Keep unmapped spend visible and repeat the result in a second closed period.

Detector 3: new-customer economics and payback

Define a new customer from canonical completed-order history, including the identity rules and limits for guest checkout. For mature acquisition cohorts, calculate CAC, first-order contribution, 60-, 90- and 180-day cumulative contribution, repeat rate and payback.

Do not compare cohorts at horizons they have not reached. Compare canonical customer classification with the platform’s new-customer flag and quantify disagreement before using either for bidding.

Detector 4: brand, non-brand and intent leakage

Define brand, competitor, category, product and informational query rules before looking at performance. Keep privacy-hidden search terms explicit.

Search-term reports support query cost and standard conversion metrics. They do not support canonical query-level profit unless the bridge reaches that grain. Validate any negative-keyword or exclusion candidate in a second period, and do not call brand spend waste from high ROAS or low new-customer share alone. Material brand-budget decisions need an incrementality test.

Detector 5: landing-page and journey mismatch

Join query or theme, asset group, landing page, device, availability and funnel data only at compatible grains. Rank material-spend pages against matched peers with similar intent, device, country, price band and campaign role.

Treat a click-to-session gap as a measurement or consent problem first. A weaker spend-to-peer result is an opportunity scenario until a controlled landing-page intervention proves recovery.

Detector 6: feed eligibility and profitable inventory exposure

Join active, in-stock catalogue offers and margin to Merchant Center status, item issues and paid product reporting. Find high-margin, high-demand products that are missing, disapproved, excluded or not serving, then weight the gaps by demand, margin, spend history and issue duration.

Keep the gates separate. Approved does not mean included in a campaign, and zero impressions do not prove a feed defect. Check listing groups, inventory filters, market scope, bids, budgets and demand before assigning the cause.

Run the free product feed scanner to catch source-file defects, then verify processed status and serving inside Merchant Center and Google Ads.

Detector 7: marginal budget opportunity or saturation

Budget decisions depend on the return from the next unit of spend, not average historical ROAS. Review spend, incremental conversion value, budget-limited status, target changes, seasonality and simulator output.

Treat observational spend-response slopes and simulators as scenarios. Recommend one controlled budget or bid experiment with a guardrail and stopping rule.

Be careful around known platform boundaries. Product reporting expanded across networks in June 2026. From August 17, 2026, budget-limited Target CPA and Target ROAS campaigns are pulled more consistently toward their set target, so a campaign that previously overperformed a loose target may appear to decay. Split windows at these definition or behavior changes instead of calling the discontinuity a business trend.

Detector 8: attribution and incrementality gap

Compare platform, analytics and canonical-commerce views at explicitly matched settings. Show whether the proposed decision changes under reasonable attribution assumptions.

Data-driven attribution distributes observed credit; it does not estimate causal lift. For a material budget decision, specify an eligible Google Ads experiment, conversion-lift study or geo holdout, including the primary outcome, guardrails, power check, contamination risks and stopping rule.

Turn the audit into one decision

Prefer one decision-changing result over a catalogue of weak observations. A finished report states:

  • spend, clicks, conversions, orders and customers;
  • value and the exact profit definition;
  • attribution settings and conversion lag;
  • bridge and reconciliation coverage;
  • sample sizes and unmatched share;
  • the comparator and a second-period result;
  • uncertainty, owner, reversible test and verification condition.

As practical defaults when no decision-specific model is better, a high-confidence observational comparison should have at least 90% relevant order or value mapping, 50 mature observations per major group, the same direction in two non-overlapping periods and an interval excluding the null. Medium confidence can use at least 80% coverage and 30 mature observations when the next step is reversible.

Do not change budgets, goals, negatives, feeds or tracking during the research pass. Produce the evidence, identify the mechanism and hand the owner a bounded test.

Sources