Google Ads Measurement common mistakes
Google Ads Measurement · Understand the traps and how to avoid them.
When asked which conversion actions to import into a Google Ads account from Google Analytics, the candidate selects every goal in the property, including micro-conversions such as scroll events and page views, so the Ads-reported conversions are inflated and bidding is trained on low-value actions.
Candidates conflate 'any measurable event' with 'a conversion action worth importing'. They have learned that Analytics collects events and assume more imported goals give the bidding algorithm more signal, without considering that Smart Bidding optimizes toward whatever is imported and will chase cheap, low-intent actions.
What to do instead
Before selecting goals, classify each goal as a macro-conversion (revenue or lead) versus a micro-conversion (engagement signal). Import only macro-conversions as primary conversion actions for bidding; mark micro-conversions as secondary or leave them out. In the Ads conversion import flow, verify which goals map to which conversion actions and set primary/secondary status per the advertiser's business objective.
The candidate describes how to set up conversion tracking by saying 'add the Google tag and it will track conversions', without distinguishing the Google tag (site-wide base tag) from a conversion event snippet or a conversion linker, and without explaining what must be configured in the Ads account for the action to record.
The candidate has memorized the phrase 'Google tag' as the modern replacement for the old global site tag and collapses all tagging into one step. This produces answers that cannot explain why a conversion shows in Tag Assistant but not in the Ads conversion report.
What to do instead
Structure the answer as three layers: (1) the Google tag loads on every page and establishes the measurement ID/destination; (2) the conversion event (event snippet or Analytics-imported goal) fires on the thank-you page or on the button click; (3) the conversion action must exist in Google Ads with the correct counting setting (one vs. every), attribution window, and value rule. Check each layer separately when diagnosing a missing conversion.
When asked about attribution, the candidate answers that 'last-click is the default and is accurate' and does not mention that Google Ads uses data-driven attribution as the default for most conversion actions, nor that attribution model and lookback window change which clicks get credit.
The candidate learned attribution from older material where last-click was the assumed default and has not internalized the shift to data-driven attribution. They also treat the attribution model as a reporting cosmetic rather than something that changes the numbers they will later be asked to interpret.
What to do instead
State explicitly that data-driven attribution is the default model for most conversion actions and that last-click, first-click, linear, time-decay, and position-based remain selectable. Explain that the model plus the lookback window (for example 30-day click, 1-day view for display/video) determine credited conversions. When comparing Google Ads conversions to Analytics conversions, align model and window before calling it a discrepancy.
The candidate treats a difference between Google Ads conversions and Google Analytics conversions as a bug and recommends 'fixing' one of the two systems, instead of explaining the legitimate reasons the two numbers differ.
Candidates assume two Google products should always agree. They do not know the structural causes of variance: different attribution models and windows, different counting (one vs. every conversion), Analytics session-based vs. Ads click-based attribution, cross-device and modeled conversions, and filtering of invalid traffic.
What to do instead
List the reconciliation factors in order: attribution model, lookback window, conversion counting method, session vs. click scoping, modeled conversions, and consent mode effects. Recommend comparing on the same dimension (same date range, same time zone, same model where possible) and accepting a documented variance band rather than forcing the numbers to match. Use Google Ads conversion data for bidding decisions and Analytics for on-site behavior.
When asked to evaluate campaign performance, the candidate reads only the conversion rate or only ROAS and makes a recommendation without checking volume, statistical confidence, or the cost side of the equation.
Candidates latch onto the single most quotable metric and skip the diagnostic chain. They do not habitually ask whether the sample is large enough, whether the observation window covers a full conversion lag, or whether a high ROAS came from a tiny spend base.
What to do instead
Use a fixed diagnostic order: impressions to click-through rate (creative and targeting), clicks to cost per click (auction and quality), clicks to conversions (landing page and offer), conversions to cost per conversion and ROAS (efficiency). Before recommending a change, confirm the data volume is sufficient and the window exceeds the conversion lag; otherwise label the finding directional and propose a longer test.
The candidate interprets a metric without checking its definition in the specific context, for example treating 'conversions' as identical across campaigns that use different conversion actions, or comparing 'clicks' to 'sessions' as if they were the same unit.
Metric names look universal, so the candidate assumes a single definition. In practice conversions depend on which actions are counted as primary, clicks are not sessions, and cost metrics differ by what is included (for example cost vs. spend with or without fees).
What to do instead
For every metric comparison, state the definition being used: which conversion actions are primary, whether the window is click or view, whether the unit is click, session, or user. Normalize before comparing (for example cost per conversion using the same primary actions across campaigns) and flag comparisons where definitions differ as invalid.
The candidate segments performance only at the campaign level and never segments by device, network, audience, geography, or time, so the recommendation is a blunt 'pause the campaign' rather than a targeted change.
Campaign-level dashboards are the first thing a candidate sees, and segmentation requires an extra step. The candidate also fears that segmentation will complicate the answer, so they default to the aggregate view.
What to do instead
Before recommending an action, segment by at least device, network (search partners/display), and top geographies or audiences, and check the conversion lag by day of week. Identify the specific segment that underperforms, then recommend a segment-level action (bid adjustment, exclusion, budget shift) rather than a campaign-level pause.
The candidate recommends a bid or budget change based on a single day or a short window, ignoring conversion lag and seasonality, and presents the result as a confident conclusion.
Candidates want to give a decisive answer and treat the most recent data as the most relevant. They do not account for the fact that conversions can arrive days after the click, so recent days look artificially weak, and they do not check for day-of-week or seasonal patterns.
What to do instead
State the conversion lag for the account and exclude the incomplete tail of the date range from evaluation, or compare like-for-like periods. Check week-over-week and year-over-year where available. If the window is shorter than the lag, describe the finding as preliminary and specify the additional data needed before acting.
The candidate identifies a problem (for example high cost per conversion) but the recommended action is not tied to the metric that caused it, such as recommending a budget increase when the issue is a landing page conversion rate.
Candidates pattern-match 'underperforming campaign' to a stock list of optimizations (raise budget, add keywords, improve quality score) without tracing which stage of the funnel is actually broken. The recommendation sounds plausible but does not address the diagnosed cause.
What to do instead
Force a one-to-one link between diagnosis and action: if click-through rate is low, act on creative and targeting; if click-to-conversion rate is low, act on landing page, offer, and audience intent; if cost per click is high, act on quality score, bid strategy, and auction competitiveness. State the metric that justifies the action and the metric you expect to move as a result.
The candidate proposes an optimization but does not define how success will be measured, over what period, or what would count as failure, so the recommendation cannot be evaluated after the fact.
Exam prompts often ask 'what should the advertiser do next', and candidates answer only the action. They do not habitually attach a measurement plan, and they may not know that changing a bid strategy resets the learning period and makes short-term results unreliable.
What to do instead
Close every recommendation with a measurement plan: primary success metric, guardrail metric to ensure no harm elsewhere (for example conversion volume or impression share), evaluation window longer than the conversion lag and any learning period, and the threshold that would trigger a rollback. Note that bid strategy changes trigger a learning period during which performance is volatile and should not be judged.