Google Ads Shopping common mistakes
Google Ads Shopping · Understand the traps and how to avoid them.
Treating a Product Shopping campaign and a Smart Shopping campaign as interchangeable when choosing a campaign type for a new feed-driven advertiser, and answering campaign-type questions without checking which inventory or bidding controls the scenario implies.
The campaign-type names overlap in casual use, and candidates who have only seen one interface assume all Shopping campaign types share the same bidding and placement controls. The exam tests the distinction between standard Shopping (manual bidding, Search/Shopping inventory) and automated campaign types with different control surfaces.
What to do instead
Build a one-page comparison table of Shopping campaign types covering bid strategy options, inventory/placement reach, and which levers the advertiser can still control. Before answering, identify the scenario's stated goal (control vs. automation) and match the campaign type to it.
Answering feed-attribute questions by guessing which attribute controls a given eligibility rule instead of reasoning from the attribute's defined role (for example confusing product_type with google_product_category, or brand with mpn).
Several feed attributes look similar in purpose but drive different matching, reporting, and eligibility behaviour. Candidates memorize attribute names without learning what each one actually feeds into, so near-synonyms become traps.
What to do instead
For each core attribute, write down three things: what it matches against, whether it is required or recommended, and what breaks if it is missing or malformed. Drill by predicting the outcome of a broken attribute, not by reciting definitions.
Assuming a disapproved or missing product will still serve in some form, or that fixing the feed guarantees immediate eligibility, and answering timing/eligibility questions as if changes were instantaneous.
Candidates conflate 'submitted' with 'approved' and forget that feed reprocessing and policy review take time and can fail on re-review. The exam probes understanding of the product lifecycle rather than the happy path.
What to do instead
Learn the product status states and what each one means for serving, plus the typical reprocessing cadence after a feed update. On any eligibility question, first ask 'what state is this product in right now?' before choosing an answer.
Choosing a bid strategy for a Shopping scenario based only on the stated goal (e.g., 'maximize revenue') without checking whether the account has the conversion data or feed quality the strategy requires.
Automated bid strategies have data and eligibility prerequisites, and candidates pick the strategy whose name best matches the goal rather than the one the account can actually support. The exam deliberately includes scenarios where the obvious goal-named strategy is not viable.
What to do instead
For each bid strategy, note its prerequisites (conversion volume, conversion tracking, value data) and what happens when those are absent. Practice rejecting a goal-matched strategy when the scenario shows insufficient data, and pick the feasible alternative.
Ignoring the interaction between Merchant Center account structure and Google Ads linking, and answering linking or multi-account questions as if one feed maps to one campaign by default.
Candidates who work in single-account setups assume linking is trivial and overlook multi-client, multi-country, or sub-account feed structures. Exam items test whether you know how feeds, Merchant Center accounts, and Ads accounts connect and what breaks when they do not.
What to do instead
Map out the possible feed-to-account topologies (one feed to many campaigns, multiple feeds, sub-account structures) and the linking prerequisites for each. When a scenario mentions multiple countries or brands, check the feed structure before answering.
Treating product groups as a reporting-only construct and failing to recognize that subdivision and exclusion decisions change which products are eligible to serve and at what bid.
Product groups look like a reporting tree in the UI, so candidates underestimate their bidding function. The exam tests whether you can predict what happens to a product when it falls into a subdivided or excluded group.
What to do instead
Practice tracing a single product through a product-group tree: which group it lands in, whether it is excluded, and which bid applies. Learn the default catch-all group behaviour and how exclusions cascade.
Answering performance-diagnosis questions by picking the most plausible-sounding cause instead of following a structured triage order (feed disapproval, then budget/bid, then competition, then landing page).
Shopping diagnosis involves several independent layers, and candidates jump to the layer they know best. Without an ordered checklist, they select answers that describe a real problem but not the one the scenario data points to.
What to do instead
Memorize a fixed triage sequence and apply it to every diagnostic scenario: eligibility and disapproval first, then impression share and budget, then bid and competition, then page and price competitiveness. Eliminate answer choices that address a later layer before an earlier one has been ruled out.
Confusing feed-based remarketing or dynamic remarketing eligibility with standard Shopping campaign eligibility, and answering audience questions with the wrong requirement set.
Both rely on the Merchant Center feed, so candidates assume the same requirements apply. In practice the tagging, audience, and campaign requirements differ, and the exam tests whether you know which requirements belong to which feature.
What to do instead
Create a requirements checklist per feature (feed attributes needed, tagging needed, audience list needed, campaign type needed) and compare features side by side. When an audience question appears, identify the feature first, then recall its specific checklist.
Assuming local inventory or store-related Shopping features work from the online feed alone, and answering local-availability questions without the separate local data source requirement.
Candidates who have not set up local inventory assume store availability is inferred from the product feed. The exam tests knowledge of the additional data and setup steps local features require.
What to do instead
List the separate inputs local Shopping features need (local product data, store linkage, business profile linkage) and what happens when they are missing. Treat 'local' as a distinct setup track, not an extension of the standard feed.
Managing time poorly by over-investing in feed-attribute minutiae early and then rushing scenario-based bidding and diagnosis items, or the reverse, leaving no time to re-check the high-weight conceptual items.
The exam mixes recall-heavy feed questions with reasoning-heavy scenario questions, and candidates allocate effort by comfort rather than by item difficulty or weight. Fatigue on long scenario stems leads to selecting a plausible but wrong option.
What to do instead
Do a timed practice pass to find your personal pacing. Flag long scenario items, complete all short recall items first, then return with remaining time. Reserve the final minutes to re-read flagged scenario stems and confirm the chosen answer addresses the stated goal.