Shopify Google Ads first campaign: Search, Shopping, or PMax
The first Google Ads move is not trying Search, Shopping, Performance Max, Display, and Video all at once. First decide whether the buyer is searching, comparing product cards, or being found by automation; if the feed or conversion tracking is not accepted, hold Shopping and PMax.
Lesson artifact
campaign type map
Primary rule
explain first, automate later
Next lesson
account and conversion tracking
First-screen status board
Intent
active search demand
Feed
feed accepted before Shopping/PMax
Assets
multi-surface assets
Tracking
Purchase/Lead QA
Guardrail
budget and stop rules
Series entry
Bring a choice map before moving into account setup
This is lesson 1 of Google Ads Basics, so it assumes you do not yet have trusted account setup, conversion tracking, or feed evidence. You do not need to build ads yet. For the 20oz leak-proof travel mug, write one question for this round, one path to start with, and one line that keeps another path on hold.
This lesson covers
Decide whether the first proof comes from active search, product cards, automated reach, or education / remarketing.
The next lesson uses
Bring the choice map to verify the primary conversion, value, currency, and transaction ID.
Later routes
Go to Merchant Center when the feed is unclear and to budget and bidding when the sample is fragmented; do not open every type at once.
Read the buying path before choosing a campaign
The first Google Ads campaign should not prove three things at once; decide whose evidence you need first
Keep the series case: a 20oz leak-proof travel mug on a Shopify store. The owner has a $30 daily budget, knows some buyers may search “leak proof travel mug,” and knows others compare price, availability, and delivery in product cards. But conversion tracking is not accepted and Merchant Center has not shown that feed fields match the page. The easiest mistake is to launch Search, Shopping, and PMax together and use total clicks or blended ROAS from week one to decide which campaign is best. That creates a mixed result, not a learning path.
This lesson treats the three campaign types as three ways to find people, not as levels of sophistication. Search reads active queries and the ad promise. Shopping depends on product data so people comparing cards can read price, image, and availability facts. PMax gives more inputs and automation to the system, which requires trusted conversion actions, value, feed, assets, page, and budget window. Before choosing a campaign, write the question for this round: do you need to learn what people actively search, verify product recognition, or expand after the signal is trusted?
Turn the tumbler case into an executable order: confirm the page can carry the promise about leak protection, capacity, and commuting use; verify the Purchase/Lead primary conversion, value, currency, and transaction ID; if the feed is not accepted, mark Shopping/PMax as held instead of collecting bad evidence for “a few days.” If Search starts first, keep one main intent, one ad group, the same final URL, and a small term set. Record search terms, ad promise, first-screen proof, and order evidence. Each choice must say where to check, what passes, and which lesson receives the failure.
The first campaign succeeds when, after an observation window, the reader can say which people the spend bought, whether ad and page answered the same question, whether tracking carried real orders into Google Ads, which path should continue, and which should stay held. Relevant Search clicks do not automatically qualify Shopping or PMax for scale. The current conclusion supports the next choice and release boundary; it does not merge three channel jobs into one answer.
Write who you need to read, what you need to learn, and what stays held before creating a campaign; automation does not replace feed or tracking evidence.
Do not memorize campaign types first
First read Google Ads as three ways to find buyers
Search, Shopping, and Performance Max are not three buttons with different levels of sophistication. They are three traffic paths: people already searching, people comparing product cards, and people the system tries to find from your signals. Understand the buyer state before choosing the first campaign.
Path 1
People already searching
They already typed the need into Google, such as "leak proof travel mug." They are closer to purchase, but you must read the actual query.
Campaign fit
Usually start with Search. The first round is not about reaching everyone; it is about reading query, ad promise, and landing-page fit.
First proof
Search term, keyword, ad headline, Final URL, Purchase / Lead, and first-screen page proof.
Common trap
Do not make keywords broad just because Search is readable. Broad terms can buy clicks that look like users but are not customers.
Path 2
People comparing product cards
They compare price, image, stock, shipping, reviews, and size. Google mainly understands the product through product data.
Campaign fit
This usually points to Shopping, or feed-centered PMax. Merchant Center and product-page fields must match first.
First proof
Item ID, SKU, title, image_link, price, availability, GTIN, and Merchant Center Diagnostics.
Common trap
Do not blame bidding before the feed is accepted. If product data is wrong, the system may not even learn which product should show.
Path 3
People the system tries to find
They may come from Search, YouTube, Gmail, Discover, Display, or remarketing. You are no longer controlling one entry point; you are giving the system goals and inputs.
Campaign fit
This is where Performance Max fits better: expanding after tracking, feed, assets, and budget window are already stable.
First proof
Conversion action, value, currency, transaction ID, asset coverage, product group, brand boundary, and learning status.
Common trap
Do not treat PMax as a beginner shortcut. If the inputs are wrong, automation learns around the wrong goal faster.
Plain terms first
These terms are not decorative; every later step uses them
If campaign, feed, and conversion tracking are unclear, campaign type selection becomes a recommendation click. First ground the terms in an ecommerce workflow.
Google Ads
Google Ads is Google’s advertising system, not one ad slot. It can serve ads across Search, Shopping surfaces, YouTube, Display, Discover, Gmail, Maps, and more.
- Where you see it
- You see it in the Google Ads account where campaigns, goals, budgets, bids, assets, and conversions are configured.
- What breaks
- If every placement is treated as the same traffic, week-one data may look busy while the real source of results stays unclear.
- Ecommerce example
- For a 20oz tumbler, a person searching "leak proof travel mug" and a person seeing a YouTube video answer very different validation questions.
campaign
A campaign is the layer that carries the business goal, budget, campaign type, and major settings. It answers what this spend is supposed to learn first.
- Where you see it
- You choose a campaign type when creating a campaign, then set conversions, budget, bidding, and assets.
- What breaks
- If the first campaign handles acquisition, remarketing, product testing, and creative testing at once, the readout becomes blended.
- Ecommerce example
- A tumbler launch can start by validating high-intent Search terms instead of adding Display remarketing and PMax scaling at the same time.
Search
Search ads are triggered by search queries, so they are useful for seeing what people are actively trying to find.
- Where you see it
- You see it in Search campaigns, keywords, search terms, and ad groups.
- What breaks
- If keywords are too broad or the page mismatch is large, clicks may rise while purchase intent stays weak.
- Ecommerce example
- "buy leak proof travel mug" is a cleaner first purchase test than "coffee lifestyle ideas."
Merchant Center / Feed
Merchant Center manages product data for Google. A feed is the product data table with fields such as title, image, price, inventory, brand, and GTIN.
- Where you see it
- Shopping and feed-based Performance Max read these fields, and Google uses them for product review and matching.
- What breaks
- Wrong price, inventory, title, or GTIN can make Shopping/PMax learn from weak product signals.
- Ecommerce example
- If one tumbler has 12oz and 20oz variants, the feed must clearly carry size, price, inventory, and images for stable Shopping surfaces.
SKU
SKU is the store-owned identifier for a product or variant. It is not a Google-generated ID; it is the unit your team uses to connect inventory, price, margin, and ad readouts.
- Where you see it
- You see it in Shopify products, order exports, product feeds, Merchant Center sample sheets, and margin reports.
- What breaks
- When SKUs are messy, Shopping and PMax product performance is hard to match with real inventory, margin, and refunds.
- Ecommerce example
- A black 20oz tumbler and a white 12oz tumbler should use different SKUs, or ad spend, inventory, and profit get blended.
CVR
CVR means conversion rate: how many clicks or visits become key actions such as Purchase, Lead, or AddToCart.
- Where you see it
- You see it in Google Ads, GA4, Shopify analytics, and page review sheets.
- What breaks
- When CVR is low, the first problem may be keywords, page fit, price, shipping, or tracking quality rather than campaign type.
- Ecommerce example
- If Search brings 200 clicks and 0 orders, do not only blame budget; inspect queries and first-screen page fit.
ROAS
ROAS is return on ad spend: revenue attributed to ads divided by ad spend. It is revenue efficiency, not profit.
- Where you see it
- You see it in Google Ads, GA4, and business review sheets, but attribution can differ by platform.
- What breaks
- Comparing Search, PMax, and Display ROAS in one table can hide that each type has a different job.
- Ecommerce example
- Display can have low ROAS while building a useful remarketing pool; high Search ROAS also does not mean unlimited scaling.
conversion tracking / key event
Conversion tracking records important user actions. Ecommerce usually cares about Purchase, but Lead, AddToCart, or InitiateCheckout may also matter.
- Where you see it
- You verify it in Google Ads conversion settings, GA4, Shopify orders, and ad reports.
- What breaks
- If value, currency, trigger timing, or deduplication is wrong, automated campaigns can learn toward the wrong goal.
- Ecommerce example
- Purchase should fire after a real order with value and currency, not repeatedly just because a thank-you page is visited.
Main artifact
Campaign type selection map
Do not treat campaign types as a feature list. Treat them as a diagnostic order: pick the type that best validates the first variable your account needs to understand.
Click the problem that best matches the account first, then read the suggested start, hold items, and evidence requirements. Do not validate every type at once.
Search
Can add later
Shopping / Performance Max
Hold this round
Display / Video as first purchase validation
Evidence required
- You can list 10-30 high-intent queries, not generic interest terms.
- The product page first screen matches the ad promise, price, shipping, and proof.
- Purchase or Lead tracking has passed QA.
First action
Launch one small-budget Search campaign to answer whether active searchers click and convert.
20oz first-campaign practice
Do not memorize types; practice the first launch choice
The same 20oz tumbler can need a different first campaign depending on queries, feed, conversion signals, and asset maturity. Pick a scenario, choose the start, then read the feedback.
Step 1: choose the account scenario
Step 2: choose the first campaign
Instant feedback
Good starting point20oz tumbler: clean search demand
You can list 24 high-intent queries such as leak proof travel mug and 20oz insulated tumbler with lid. The first screen shows leak proofing, size, price, shipping, and reviews; Purchase has passed QA.
Your choice
Start with Search
Safer start
Start with Search
Why
Search connects queries, ad promise, page fit, and Purchase in one evidence chain, which fits a small first test.
Hold this round
Hold PMax, Display, and Video; add Shopping after feed sampling is complete.
Proof to write into the map
Before launch, write 10-30 queries, matching ad promise, first-screen proof, and stop conditions.
First-campaign decision record
Turn a service, single product, multi-SKU catalog, or new product into a reviewable start record
The 20oz practice above shows four typical starts. Here, put your own business shape, readiness, current UI readback, and hold list into one saveable record.
Do not begin with “which campaign is more advanced.” A service, a single product, a multi-SKU catalog, and a new product need different first evidence. The readiness score here only counts inputs you can explain; it is not a Google Ads eligibility or performance score.
Choose the business shape, then write one question for this round. Mark an input as “explained with saved evidence” only when it can be reviewed. When something is still unclear, keep it on the hold record instead of hiding it behind a new campaign.
Fill readiness first
Classroom readiness
1/7
This only counts how many inputs you can explain. A higher score does not replace a same-day official-page check, account eligibility, or real conversion acceptance.
Then select one starting path
This does not submit an ad or change an account. It makes you write what is being validated now and what is not being validated this round.
Current judgment
Write this round’s question in one sentence first
Why
Before choosing a type, state whether this round reads active search, product cards, post-education visit quality, or trusted automated expansion. Without a question, a readiness score is only a string of checks.
Boundary this round
Hold campaign creation until the question, evidence location, and responsible lead can all be written down.
Read this result before moving to the launch-risk router below. It does not prove that an account can run ads; it helps make the object, evidence, and pause line for the next review more specific.
Current UI readback steps
Google UI, goals, and available types can change. These are same-day readback actions, not a claim that one old screen is a fixed operating path.
Step 1
Read the goals and types shown in the current account
Open the Google Ads campaign-creation flow and record the goals and types actually shown that day. Accounts, regions, and product eligibility can differ, so do not treat an old screen reference as the current path.
Step 2
Read Merchant Center product status before a retail path
If you choose Shopping or feed-based PMax, first check that product data, website verification or claim, shipping settings, and the Google Ads link all have a clear owner and current status.
Step 3
Carry conversion and page evidence into the next lesson
Confirm the current evidence in Google Ads conversion settings and the test order or lead path. Record only status and evidence location here, not login details, customer data, real order IDs, or advertising account identifiers.
Wrong-choice explanation
Choose the action closest to what you might have done, then read why it can distort the first readout.
Why not start this way
Not right. It blends search intent, product data, assets, and automation into one readout, so the first round cannot tell you which layer needs repair.
Save your first-campaign decision record
The record stays in this browser, and the export is marked for classroom use.
Launch risk router
First decide whether you are validating or blending variables
This step separates four common beginner launch mistakes. It is not another campaign-type list; it tells you whether the risk comes from the goal, tracking, feed, or traffic job mismatch.
Click the risk that looks closest to the current account. The response separates symptom, likely cause, first action, and forbidden action so you can write it into the copyable notes.
Current risk
All types at once
Surface symptom
Week one has clicks, impressions, and a few events, but the team cannot tell whether Search, Shopping, PMax, or Display caused the readout.
Likely cause
The first launch skipped the business question and tested intent, product data, assets, and audience at the same time.
First action
Pause the blended readout, choose one validation path, and move the other types into the hold list.
Do not do
Do not compare PMax, Search, and Display ROAS in one table as if they had the same job.
Role boundaries
No type is inherently more advanced; each answers a different question
Understand the five campaign types by job boundary first. Beginners should read what each type should and should not answer before clicking buttons.
Search
Validate active search intent first
- Good for
- People actively search for the product, problem, or use case; small budgets need readable queries, ad promise, and page fit.
- Not for
- Demand has no clear query yet, or keywords are so broad that click quality cannot be explained.
- First evidence
- Search terms, CTR, CVR, Purchase/Lead events, first-screen message match.
Shopping
Validate product data and price competitiveness
- Good for
- The feed is approved, and title, image, price, inventory, shipping, and GTIN-like fields are stable.
- Not for
- The feed is new and unaudited, product page price/inventory changes often, or variant data is messy.
- First evidence
- Merchant Center diagnostics, product approval, title quality, price/inventory consistency, product-page quality.
Performance Max
Expand across inventory after signals are stable
- Good for
- Conversion goals are clear, and feed, assets, audience signals, and budget window can support automated learning.
- Not for
- Using it as a beginner shortcut, or giving it most budget while tracking, feed, and assets are unstable.
- First evidence
- Conversion quality, asset coverage, product grouping, Search overlap, brand exclusions/negative boundaries.
Display
Support reach, remarketing, and demand education
- Good for
- There is a clear audience, remarketing pool, or education task, and the first round is not meant to prove purchase demand.
- Not for
- Using impressions or cheap clicks as proof that a product is validated, especially before purchase tracking passes QA.
- First evidence
- Audience source, frequency, visit quality, remarketing pool size, downstream purchases/leads.
Video
Explain use cases, grow awareness, and learn from creative
- Good for
- The product needs demo, comparison, or story, and the team has enough assets plus downstream page support.
- Not for
- A tiny-budget first launch that expects stable purchases while asset inventory is thin.
- First evidence
- Video completion/engagement, search lift, landing-page visit quality, downstream Search/Shopping capture.
Search / Shopping / PMax evidence paths
Prove the role before deciding whether to launch the type
Do not choose campaign type by instinct. Each type needs a backend evidence path: where to look, which fields to record, what those fields prove, and which gaps mean hold.
Evidence path
Search / search terms / landing-page intent path
Validate active demand first: people are already searching for the product, use case, or problem, and the ad plus page can answer it.
Where to look
Google Ads -> Search campaign -> Keywords / Search terms / Ads / Landing pages; then sample GA4 landing pages and Shopify orders.
Fields to record
Query, match type, keyword, ad promise, landing page URL, CTR, CVR, conversion action, order or lead sample, and negative keyword candidates.
What it proves
It proves whether real queries, ad promise, first-screen page fit, and Purchase / Lead can sit in one evidence chain.
Hold rule
If terms are noisy, the page promise does not match, or Purchase is unverified, do not treat PMax or Shopping as the scaling answer yet.
Next route
Route into the Google Ads Pro search terms / negative keyword system, and reuse the insight for SEO keyword mapping.
Evidence path
Shopping / Merchant Center / feed readiness path
Validate whether Google can understand the product card correctly: title, image, price, stock, GTIN, and product page consistency.
Where to look
Merchant Center -> Products / Needs attention / Diagnostics; then return to the feed, Shopify product / variant, and product page.
Fields to record
Item ID, SKU, GTIN, title, image_link, price, availability, shipping, approval status, diagnostics status, and product page URL.
What it proves
It proves whether product data can support Shopping or feed-centered Performance Max.
Hold rule
If the feed has disapprovals, price or stock mismatch, unclear variants, or GTIN problems, fix the feed before blaming bids.
Next route
Route into Product Data Feed Operations, the GTIN / feed tools, and the Merchant Center diagnostics checklist.
Evidence path
Performance Max / input quality / conversion value path
Expand coverage after goals, feed, assets, and conversion signals are trusted, instead of using automation to hide basic gaps.
Where to look
Google Ads -> Performance Max -> Asset groups / Listing groups / Goals / Insights; also inspect channel performance / inventory mix, conversion goals, brand exclusions, search themes, and final URL expansion.
Fields to record
Conversion action, value, currency, transaction ID, asset coverage, channel performance, inventory mix, final URL expansion, product group, audience signal, brand exclusion, budget window, and learning status.
What it proves
It proves automation has clean goals, enough assets, clear product scope, explainable inventory mix, and a reviewable budget window.
Hold rule
If conversion value, feed, assets, inventory mix, or brand / remarketing boundaries are unclear, do not let PMax carry the main budget yet.
Next route
Route into account setup and conversion tracking, plus Google Ads Pro PMax control, brand exclusions, and negative boundaries.
Evidence path
Budget / check window / hold-list path
Make sure the first campaign has enough sample to answer one question, instead of splitting budget across unreadable variables.
Where to look
Google Ads -> Budget / Bidding / Change history; then review GA4, Shopify orders, and the team task sheet.
Fields to record
Daily budget, bid strategy, target CPA / ROAS if used, check window, change history, hold list, pause condition, and check lead.
What it proves
It proves the team is not changing ads by feel, but reviewing by window, pause condition, and next task.
Hold rule
If budget is fragmented, changed multiple times a day, or change history is not recorded, narrow terms, product scope, or geography first.
Next route
Route into budget and bidding basics, ROAS / profit judgment, and the next task in the copyable lesson notes.
First-campaign launch blocker check
Choose the missing proof first: hold the matching campaign types
This is not another concept list. Choose the gap closest to your account, then use the response to decide which campaign types to hold, which lesson comes next, and what to write in the copyable notes.
Click the gap you are least confident about. The selected row changes the selected hold rule; if you have more than one gap, fix the most upstream problem first.
Current blocker
Conversion tracking not accepted
Surface symptom
Purchase / Lead count, value, currency, transaction_id, or deduplication still does not match Shopify / GA4 order samples.
Hold this round
Hold PMax, tROAS, Maximize conversion value, and any scaling that learns from Purchase value. Search can only run as a small query-reading test.
Fix this route first
Go to the next account and conversion tracking lesson first. Verify primary conversion, value, currency, dedupe, and test orders before returning to budget decisions.
Copyable note line
Write in the notes: fix tracking first; keep only readable query samples this round; hold PMax / value bidding.
Official campaign type boundaries
Official docs explain type roles; they do not choose your first campaign
This section translates official docs into decision boundaries. The point is not memorizing types; it is knowing what each signal can and cannot prove.
Google Ads Help: choose the right campaign type
Campaign type choice
Official fact
Google Ads begins with a goal and campaign, and campaign type is selected based on marketing goals, brand strategy, and available time.
How this lesson uses it
This lesson treats campaign type as diagnostic order: write the business question first, then choose the first campaign that produces the clearest proof.
What it cannot prove
The official campaign type list does not prove you should launch every type at once, or that one type is inherently more advanced.
Google Ads Help: Search campaigns
Search campaign
Official fact
Search campaigns use keywords and text ads to reach people actively searching for products or services, and setup does not require special files or assets.
How this lesson uses it
Beginners often start with Search to validate active demand because search terms, page fit, and conversion tracking are easier to read.
What it cannot prove
Search is readable, but not always first; without high-intent terms, page fit, and conversion goals, it can still buy noise.
Google Ads Help + Merchant Center product data specification
Shopping and product data
Official fact
Shopping ads use Merchant Center product data, not keywords, to decide how and where ads show; inaccurate or missing product data can affect serving or create product problems.
How this lesson uses it
If feed, price, inventory, image, GTIN, and landing-page consistency are not verified, hold Shopping or feed-based PMax.
What it cannot prove
Having products does not prove the feed is ready; Shopping also does not prove the page, margin, or inventory path is ready.
Google Ads Help: Performance Max
Performance Max inputs
Official fact
Performance Max is a goal-based campaign type that can access multiple Google inventory sources from one campaign, using inputs such as conversion goals, assets, audience signals, and optional data feeds.
How this lesson uses it
PMax is better used after goals, conversion signals, assets, and feed inputs are clear, not as a replacement for the first explainable validation path.
What it cannot prove
Broader inventory does not mean PMax can fix weak feeds, weak pages, bad conversion goals, or confused budget logic.
Google Ads Help: choose the right campaign type
Display / Video reach
Official fact
Display and Video can reach people beyond search results; Video can support YouTube reach, views, engagements, or conversion-focused goals.
How this lesson uses it
This lesson routes them to education, reach, remarketing, or asset validation jobs, not mixed into the first purchase-validation campaign.
What it cannot prove
Cheap clicks or high views do not prove product demand by themselves, and they do not replace Search, feed, page, or conversion tracking checks.
Google Ads Help: Demand Gen campaigns
Demand Gen visual path
Official fact
Google documents Demand Gen separately from PMax: Demand Gen serves visual browsing environments such as YouTube, Discover, and Gmail, while PMax can access broader Google Ads inventory from one campaign.
How this lesson uses it
When a new product or use case needs education, this lesson treats Demand Gen or Video as an asset and use-case judgment and requires a written later path for purchase validation.
What it cannot prove
Visual impressions, views, or low click cost do not prove a product can sell, and they do not make Demand Gen a synonym for PMax.
Search-first gate
Most beginners start with Search, not because Search is always best
Search is useful because it is readable: you can see what people searched, what wasted money, and whether the page matched high intent. If these gates fail, do not rush launch.
Toggle only the gates you can prove. If you do not have evidence, leave it unchecked; unchecked items are the pre-launch work.
Current readiness
2/4
Close gaps before launch
This is not meant to block advertising. It prevents the first campaign from testing too many variables. Early gaps make the next account and tracking lesson easier to verify.
PMax boundary
Performance Max is powerful, but it is not a beginner shortcut
Google describes PMax as a goal-based campaign that can access multiple inventory sources. For beginners, the point is not just broader reach; it depends on your goals, feed, assets, and conversion signals.
Conversion goals and value are trustworthy
PMax learns toward your stated goals. Wrong goals mean wrong optimization.
QA Purchase/Lead, value, currency, and deduplication first.
Feed is no longer an unknown risk
Product title, price, inventory, and GTIN affect Google matching and product serving.
Resolve Merchant Center diagnostics, variant relationships, and product-page consistency.
Assets can support multi-surface serving
Multi-surface serving is not only product cards; headlines, images, descriptions, and video gaps affect delivery.
Prepare core images, short copy, and needed video, or at least document gaps.
Blending boundaries are known
Mixing brand, remarketing, high-margin, and low-margin products can look good while hiding scale risk.
Document brand exclusions, product grouping, page scope, and stop conditions.
Stop / Go
Launch acceptance for the first campaign
Mistakes, budget guardrails, and counter-evidence reminders become stop/go rules that must work before launch.
Next lesson route
Use the first-campaign choice to pick the next route
The entry lesson should not teach all ten later lessons, but it should send the reader to the right next step. Bring the choice, route, and fields forward together.
Search first
Account setup and conversion tracking -> first Search campaign -> search terms / negative keywords
Fields to bring forward: conversion action, search terms, Final URL, budget window, pause line
Shopping first
Merchant Center and product feed -> Search / Shopping / PMax traffic role split
Fields to bring forward: SKU, GTIN, item ID, price, availability, diagnostics status
PMax later
Account setup and conversion tracking -> enhanced conversions and value quality -> scale readiness
Fields to bring forward: transaction_id, value, currency, product group, brand boundary, channel performance
Display / Video education
Improve assets, page fit, and remarketing pool first, then return to Search / Shopping / PMax purchase validation
Fields to bring forward: asset role, landing page, audience source, visit quality, next validation path
Copyable lesson notes
Turn the choice into an account task the next lesson can use
These four lines are the copyable lesson notes. Do not just say "run Google Ads"; document why, what is excluded, how long to observe, and where to stop.
Current copyable note
Copy this into the account plan, team task, or the conversion tracking check in the next lesson.
Copyable lesson notes: Google Ads campaign type map This round question: First proof: whether active searchers will click and purchase. This round start: Start with Search Hold this round: Hold PMax, Display, and Video; add Shopping after feed sampling is complete. Launch blocker: Conversion tracking not accepted - Write in the notes: fix tracking first; keep only readable query samples this round; hold PMax / value bidding. Check rule: Before launch, write 10-30 queries, matching ad promise, first-screen proof, and stop conditions. Current risk: All types at once - Pause the blended readout, choose one validation path, and move the other types into the hold list. Bring into next lesson: Account setup, conversion goals, budget guardrails, and feed checks should all serve the same first validation question.
Closing sentence
Understand the first traffic path before automation and scaling. When the next lesson moves into account setup and conversion tracking, these four lines become your launch boundary.
Go deeper
The same "run Google Ads" request can mean very different first questions
Beginners often treat campaign types as a feature list. A better approach is to write the business question first, then choose the type that produces the clearest proof.
The product has active demand, such as people searching for "leak proof travel mug" or "portable coffee cup."
Common mistake: Launch Performance Max immediately because it reaches more placements and looks easier.
Better read: The first proof is search intent and page fit; Search makes the bought queries easier to inspect.
Next action: Write 10-30 high-intent terms, ad promise, and landing page before launching Search.
The catalog is complete, with stable price, inventory, images, and variants.
Common mistake: Assume Shopping or PMax is ready just because products exist, without inspecting the feed.
Better read: Shopping readiness is not "products exist"; Merchant Center must understand the product facts.
Next action: Sample 20 SKUs for title, image, price, inventory, GTIN, and product-page consistency.
The brand is early, with little branded search and no stable remarketing audience.
Common mistake: Treat cheap Display or Video clicks as the first sales validation.
Better read: Cheap clicks may answer a reach question, not a purchase-intent question.
Next action: Define Display / Video as education or remarketing, separate from Search purchase validation.
Next lesson
Account setup and conversion tracking: make the system read the right goal first