Text version of this lessonExpand
Google Ads is not one placement. It is an ad system shaped by search intent, product data, creative assets, conversion goals, and budget rules. The first beginner lesson is not to turn on Search, Shopping, Performance Max, Display, and Video at once. It is to choose one traffic path you can explain.
Boundary: choose by job, not by button popularity
Last reviewed: June 14, 2026. This lesson is for ecommerce beginners deciding how Search, Shopping, Performance Max, Display, and Video should be used before the first launch. Google Ads surfaces and labels can change, but the beginner rule stays stable: start with the traffic source that answers the first business question clearly.
This is not a dashboard walkthrough
- What: Google Ads has several campaign types, and each answers a different question.
- Why: If the first launch tests too many variables, you cannot tell whether keywords, page fit, feed quality, assets, tracking, or budget caused the result.
- How: Write the business question first, choose the campaign type that produces the clearest proof, and record what will wait.
First understand Google Ads: it is not one traffic pool
When someone says "run Google Ads," they may mean five different jobs: buy active search demand, show product cards, let automation find conversions across channels, run remarketing, or educate the market with video. These jobs can all live in Google Ads, but they are not the same traffic.
If you sell a 20oz leak-proof commute tumbler, a person searching "buy leak proof travel mug" is high-intent demand. A person seeing a YouTube lifestyle video is education or reach. A person comparing Shopping cards is testing product data and price fit. These need different evidence.
Define SKU, CVR, ROAS, and Merchant Center before choosing a type
These terms appear throughout the lesson. Do not only memorize the acronym. Know where each term appears, which system reads it, and how a mistake can distort campaign judgment.
| Term | Plain meaning | What breaks |
|---|---|---|
| SKU | SKU is the store-owned identifier for a product or variant. You see it in Shopify, inventory sheets, order exports, feeds, and Merchant Center product reports. | Messy SKUs make Shopping and PMax performance hard to match with real inventory, margin, refunds, and replenishment decisions. |
| CVR | CVR means conversion rate: how many clicks or visits become key actions such as Purchase, Lead, or AddToCart. | Low CVR does not automatically mean the campaign type is wrong. The issue may be query quality, page fit, price, shipping, or tracking quality. |
| ROAS | ROAS is return on ad spend: revenue attributed to ads divided by ad spend. It measures revenue efficiency, not profit. | Comparing Search, Shopping, PMax, and Display ROAS in one table can hide that each campaign type has a different job. |
| Merchant Center | Merchant Center is where Google reads product data. Shopping and feed-centered PMax depend on title, image, price, availability, GTIN, and product-page consistency. | Bad product data can cause disapprovals, limited serving, wrong prices, or spend moving toward products you did not intend to promote. |
The 5 common campaign types and the job each one answers
| Type | Best first question | Do not use it for | First evidence |
|---|---|---|---|
| Search | Do people actively search for this product, use case, or problem? | Demand education, remarketing, or feed acceptance | Search terms, CTR, CVR, Purchase/Lead, first-screen match |
| Shopping | Can Google read your product data, price, image, and stock correctly? | Scaling before the feed is reviewed | Merchant Center diagnostics, title, image, price, stock, GTIN/MPN, page match |
| Performance Max | Can stable goals, feed, assets, and conversion signals support broader reach? | A shortcut while tracking is still unverified | Conversion quality, product grouping, asset coverage, brand and remarketing boundaries |
| Display | Reach, remarketing, and education | Proving that a product can sell from impressions or cheap clicks | Audience source, frequency, visit quality, remarketing pool size |
| Video | Product demos, use cases, and awareness | A tiny first launch that expects stable purchases immediately | Completion, engagement, search lift, downstream page quality |
Search / Shopping / PMax evidence paths: prove the role before launching 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. The question is not "which button is stronger." The question is "which clean proof can this account produce first."
| Evidence path | Backend path | Fields to record | What it proves | Hold rule and next route |
|---|---|---|---|---|
| Search / search terms / landing-page intent | Google Ads Search campaign, Keywords, Search terms, Ads, and Landing pages; then sample GA4 landing pages and Shopify orders. | Query, match type, keyword, ad promise, landing page URL, CTR, CVR, conversion action, order or lead sample, and negative keyword candidates. | Whether real queries, ad promise, first-screen page fit, and Purchase / Lead can sit in one evidence chain. | If terms are noisy, the page promise does not match, or Purchase is unverified, do not use PMax / Shopping as the scaling answer yet. Next route: Google Ads Pro search terms / negative keyword system, with reuse for SEO keyword mapping. |
| Shopping / Merchant Center / feed readiness | Merchant Center Products, Needs attention, and Diagnostics; then return to the feed, Shopify product / variant, and product page. | Item ID, SKU, GTIN, title, image_link, price, availability, shipping, approval status, diagnostics issue, and product page URL. | Whether product data can support Shopping or feed-centered Performance Max. | If the feed has disapprovals, price or stock mismatch, unclear variants, or GTIN problems, fix the feed first. Next route: Product Data Feed Operations, GTIN / feed tools, and the Merchant Center diagnostics checklist. |
| Performance Max / input quality / conversion value | Google Ads Performance Max, Asset groups, Listing groups, Goals, and Insights; also inspect conversion goals, brand exclusions, search themes, and final URL expansion. | Conversion action, value, currency, transaction ID, asset coverage, final URL expansion, product group, audience signal, brand exclusion, budget window, and learning status. | Whether automation has clean goals, enough assets, clear product scope, and a reviewable budget window. | If conversion value, feed, assets, or brand / remarketing boundaries are unclear, do not let PMax carry the main budget yet. Next route: account setup and conversion tracking, plus Google Ads Pro PMax control. |
| Budget / review window / hold list | Google Ads Budget, Bidding, and Change history; then review GA4, Shopify orders, and the team task sheet. | Daily budget, bid strategy, target CPA / ROAS if used, review window, change history, hold list, pause condition, and owner. | Whether the team is reviewing by window, pause condition, and next task instead of changing ads by feel. | If budget is fragmented, changed multiple times a day, or change history is not recorded, narrow terms, product scope, or geography first. Next route: budget and bidding basics, ROAS / profit judgment, and the copyable lesson notes. |
How this connects: align the ad entry point with the data entry point
After choosing the first campaign type, do not build ads immediately. First make sure the account, conversion goal, and product feed are ready, otherwise Search, Shopping, and PMax numbers will blur together later.
- Next lesson: account setup and conversion tracking to verify primary conversion, value, currency, and transaction ID.
- Product-ad prerequisite: Merchant Center and product feed to confirm price, stock, GTIN, and item status are readable by Google.
Main artifact: campaign type selection map
The map is not about memorizing every campaign type. It makes the first account move readable. Ask: what proof is missing now? Do people actively search? Is the feed stable? Is conversion tracking trusted? Are assets ready? Can budget support a review window?
| Current situation | Suggested start | Can add later | Hold this round |
|---|---|---|---|
| People actively search for the product or problem | Search | Shopping / Performance Max | Display / Video as first purchase validation |
| Product data is stable | Shopping or feed-centered PMax | Search for high-intent capture, PMax for wider reach | Scaling before feed review |
| Conversions, assets, and feed are mature | Performance Max | Search for high-intent control, Shopping for product grouping checks | Unverified tracking, thin assets, short budget window |
| The job is education or remarketing | Display / Video | Search captures new demand, Shopping/PMax captures product clicks | Treating impressions, views, or cheap clicks as product proof |
20oz first-campaign lab: do not memorize types, practice the starting choice
The same 20oz tumbler does not always need the same first campaign. The question is not whether you personally prefer Search, Shopping, or Performance Max. The question is where the cleanest account evidence already exists. If queries are clear, validate Search first. If the feed sample has passed, Shopping may be the cleaner first test. If conversions, feed, assets, and budget window are mature, then PMax can expand coverage. If people do not understand the use case yet, Display / Video can educate and build remarketing, but it should not be written as product validation.
| 20oz scenario | Safer start | Why | Hold this round |
|---|---|---|---|
| You can list 24 high-intent queries, Purchase has passed QA, and the first screen shows leak proofing, size, price, and shipping proof | Search | Queries, ad promise, page fit, and Purchase can sit in one evidence chain | PMax, Display, Video; add Shopping after feed sampling |
| Merchant Center sample passes, title, image_link, price, availability, GTIN, and product page match, but query research is still rough | Shopping | The first question is whether product card, price, image, and inventory can be understood by Google | Broad Search and PMax expansion |
| Search already found stable purchase queries, the feed is sampled, Purchase value / currency / transaction ID are trusted, and assets are mature | Performance Max | PMax now expands from accepted inputs instead of acting as a shortcut | Blending brand, remarketing, high-margin, and low-margin products without boundaries |
| Search volume is low, but the team has commute, leak-proof, and car-cup-holder comparison videos and use-case assets | Display / Video | Educate the use case, build remarketing, and inspect downstream visit quality | Treating views, impressions, or cheap clicks as product validation |
Do not choose "launch everything together" during the exercise. That is not active testing. It blends search intent, feed, assets, tracking, and audience into one unreadable pool. The first campaign is not better because it uses more buttons. It is better when one week later you can explain which proof supports continuing and which proof requires a pause.
Why beginners usually start with Search
Search is not always better. It is easier to read. You can see what people searched, which terms wasted spend, whether the ad promise matches the first screen, and whether Purchase / Lead tracking is trusted. For a small budget, readability matters more than broad inventory access.
Search also works as a minimum viable test. You do not need a large video library, many image formats, audience signals, or a mature feed just to learn from 10-30 high-intent queries.
Search still has launch gates
- You can write real high-intent queries, not broad interest words.
- The landing page first screen matches the ad promise, price, shipping, and proof.
- Purchase / Lead has passed conversion tracking QA.
- The budget can support a review window instead of splitting samples too thin.
Performance Max is powerful, but not a beginner shortcut
Google describes Performance Max as a goal-based campaign type that can access Google Ads inventory from one campaign. For beginners, the main lesson is not "it reaches more places." The lesson is that PMax depends on the goals, assets, audience signals, product data, and conversion signals you give it.
If Purchase value, currency, trigger timing, or deduplication has not passed QA, PMax may learn toward a bad goal. If feed title, price, stock, or GTIN/MPN is wrong, PMax may learn from weak product signals.
Before PMax, write four checks
- Conversion goal and value are trustworthy.
- Feed is no longer an unknown risk.
- Assets can support multi-surface serving.
- Brand terms, remarketing, high-margin products, and low-margin products have boundaries.
Launch risk router: First decide whether you are validating or blending variables
If the first campaign feels confusing, the problem is often not "not enough optimization." The problem is that the risk was not routed before launch. Put these four situations into the campaign type map.
| Risk scenario | Surface symptom | First action | Do not do |
|---|---|---|---|
| All types at once | Week one has data, but nobody can explain which traffic caused it | Pause the blended readout and choose one validation path | Do not compare PMax, Search, and Display ROAS as the same job |
| PMax before tracking QA | Purchase / Lead count, value, currency, or dedupe does not match | Return to conversion tracking QA first | Do not replace acceptance with "let it run a few more days" |
| Shopping with weak feed | Disapprovals, price or stock mismatch, or titles that look like internal SKU names | Sample title, image, price, stock, variants, and page match | Do not blame bidding while the feed is weak |
| Video/Display used as product validation | Impressions, views, or click cost look good, but orders and profit do not improve | Define it as education, remarketing, or asset learning | Do not write impressions or cheap clicks as product validation |
Stop / Go rules for the first campaign
| Stop | Go | Proof |
|---|---|---|
| Conversion tracking has not passed QA | Purchase/Lead, value, currency, trigger timing, and dedupe have proof | Field records and order samples from Google Ads, GA4, and Shopify |
| Search, Shopping, PMax, and Display launch together | The first campaign answers one question | The selection map states which types wait this round |
| Shopping / PMax launches before feed review | Merchant Center diagnostics, price, stock, and variants are explainable | Feed checklist and product-page samples |
| Impressions, views, or cheap clicks are used as product proof | Purchase validation stays with Search, Shopping, or a trusted conversion path | Review sheet separates visit quality, purchase quality, and profit quality |
Copyable lesson notes: turn the first campaign into an acceptance sheet
Copy this into your account plan
- This round's question: what business question should the first campaign answer?
- This round's start: which campaign type starts first, and why?
- This round's hold list: which campaign types wait, and why?
- Review rule: how long do you observe, and what signal triggers pause, review, or continue?
| Note field | What to write | How the next lesson accepts it |
|---|---|---|
| Business question | State whether this round tests active search demand, readable product cards, automation reach, remarketing, or market education. | Build the account structure around one question instead of blending Search, Shopping, PMax, and Display into one week-one judgment. |
| Starting campaign type | Write Search, Shopping, Performance Max, Display, or Video, plus one sentence explaining why it can produce the cleanest proof. | Before building the campaign in Google Ads, confirm that objective, budget, location, language, and landing page all serve the same choice. |
| Backend evidence | List the fields this round must inspect: search term, keyword, item ID, SKU, GTIN, conversion action, value, currency, transaction ID, and budget window. | When the next lesson verifies conversion tracking, at least one Google Ads, GA4, and Shopify order or event sample should reconcile. |
| Hold list | Write which types wait and why: feed not accepted, Purchase not QA'd, thin assets, short budget window, or unclear brand boundary. | Anyone who wants to open a held type early must first add the missing evidence instead of replacing judgment with let it run a few days. |
| Week-one review line | Name the owner, review days, pause condition, continue condition, and next tutorial route. | Review CTR, CVR, CPA, ROAS, order samples, refund reason, and change history before deciding to continue, pause, or return to feed, tracking, or page repair. |
The value of this acceptance sheet is that campaign type choice stops being "we will run Google Ads" and becomes a week-one boundary the team can review. The next lesson should not reopen the whole advertising debate; it should check whether account setup, conversion goals, budget, and product data can support this map.
How to use this output: treat the notes as a launch boundary, not as a slogan. If the chosen first campaign is Search, the next lesson should verify account structure, conversion goals, and budget guardrails around that Search test. If the chosen first campaign is Shopping, the next lesson should treat Merchant Center evidence and feed QA as the starting point. The note keeps the team from changing the goal halfway through the first week.
The next lesson covers account setup and conversion tracking. Do not enter it with only "we will run Google Ads." Bring the campaign type selection map. Then account structure, conversion goals, and budget guardrails will serve the same validation question.