Loading interactive version
Text version of this lessonExpand
Many accounts do not fail because ads cannot work. They fail because the system starts learning from dirty signals on day one. You think Google Ads is learning from purchases, but it may be learning from page visits, duplicate Purchase events, test orders, the wrong primary conversion, or a conversion with no order ID and value.
Lesson output: a Google Ads conversion launch acceptance sheet. It proves that account setup, tags, primary conversion, dedupe, value, currency, transaction ID, and first-week reconciliation are explainable.
Boundary: tracking is training data, not technical cleanup
Last reviewed: June 6, 2026. This lesson is for ecommerce beginners before the first Search campaign. It covers Google Ads account readiness, Google tag, GA4 / Shopify comparison, primary / secondary conversion, enhanced conversions, and transaction ID. Admin paths can change, but the rule stays stable: prove that the system is learning from a real business action before spend starts.
This lesson answers three questions
- What: setup includes access, billing, tags, conversion actions, value, dedupe, and first-week review.
- Why: if the primary conversion is wrong, keywords, budget, bidding, and PMax learning move in the wrong direction.
- How: use one real test order or real lead to reconcile Google Ads, GA4, and Shopify.
Plain terms first
| Term | Plain meaning | Where you see it | What breaks |
|---|---|---|---|
| Google tag | Google's measurement tag on your site; it sends events and conversions to Google Ads or GA4 | Google Ads conversion setup, GA4 data streams, GTM, Shopify integrations | Duplicate, missing, or misplaced tags can miss or double-count Purchase |
| primary conversion | The main action Google Ads uses for bidding and optimization | Google Ads conversion action settings | If page view or test order is primary, the system learns the wrong goal |
| secondary conversion | An observation-only action, not the main bidding signal | AddToCart, BeginCheckout, supporting lead, or page engagement settings | If used as the main target for too long, low-quality visits may look successful |
| enhanced conversions | Hashed first-party customer data that improves conversion matching | Google Ads conversion settings, tag diagnostics, purchase or form path | It cannot fix broken baseline tracking; Purchase, value, currency, and transaction ID must work first |
| transaction ID | The unique order identifier used to detect duplicate purchases | Shopify orders, GA4 purchase, Google Ads conversion details, tag debugging | Missing or repeated IDs can inflate or distort ROAS and smart bidding |
Main artifact: Google Ads conversion launch acceptance sheet
This sheet is not paperwork. It blocks bad learning. Before every row has evidence, do not move into budget, bidding, scaling, or PMax decisions.
| Layer | Pass standard | Evidence | Responsible role / timing |
|---|---|---|---|
| Account basics | Billing, time zone, currency, permissions, and operators are auditable | Google Ads account setting screenshots and permission list | Ads lead, before launch |
| Tag source | Google tag, GTM, Shopify integration, or GA4 import source is documented | Tag diagnostics, trigger page, and implementation path notes | Data lead, before launch |
| Primary conversion | Only Purchase or qualified Lead participates in bidding | Primary / secondary setting screenshots | Ads lead, before launch |
| Deduplication evidence | One order counts once, and transaction ID is stable | Test order ID plus Ads / GA4 / Shopify reconciliation | Data lead, before launch |
| Value and currency | Value, currency, discount, tax, and shipping definitions are explainable | Sample sheet for the latest 10-20 orders | Finance / data, first week |
| First-week review | Google Ads, GA4, and Shopify gaps have daily explanations | Daily reconciliation notes and issue handling | Growth lead, first 7 days |
Decide what bids and what only observes
Google defines primary conversion actions as actions used in the `Conversions` column and for bidding optimization. Secondary conversion actions are mainly for observation. A common beginner mistake is importing every GA4 event into Google Ads and then not knowing what is training the system.
| Event | Role | Primary? | Risk |
|---|---|---|---|
| Purchase / qualified Lead | Real business value action | Can be primary | Must verify value, currency, dedupe, and test-order exclusion |
| AddToCart / BeginCheckout | High-intent observation signal | Usually not long-term primary | Useful for funnel reading, but should not replace revenue for long |
| Page view / Session | Visit quality observation | Should not be primary | Can optimize toward cheap visits instead of purchases or qualified leads |
| Test order | QA evidence | Should not pollute reports long term | Unmarked test orders inflate early performance |
Google Ads, GA4, and Shopify are not the same report
These systems will not always show the same number because they do different jobs. The goal is not perfect equality. The goal is explainable difference.
| System | Job | Read first | Do not use it for |
|---|---|---|---|
| Google Ads | Bidding and delivery learning system | Primary conversions, conversion value, bid strategy, ad attribution | Do not use alone as the finance revenue baseline |
| GA4 | Site behavior, source path, and funnel analysis system | Event quality, source / medium, page path, funnel drop-off | Do not import every event into Ads bidding without review |
| Shopify | Order and revenue baseline | Order ID, net sales, refunds, discounts, tax, shipping | Do not expect it to explain ad attribution windows |
Test-order evidence pack: tracking is not done without proof
Run at least one real-path QA. Do not stop at a success message. Write down order ID, value, currency, transaction ID, and how the three systems match.
The pack needs four lines
- Test order ID / lead ID: for example, Shopify #1008, paid and then refunded or marked as test.
- value / currency / transaction ID: for example, 59.00 USD, transaction_id = 1008.
- Ads / GA4 / Shopify match: Shopify 1 order; GA4 purchase 1; Ads conversion pending or recorded 1.
- Deduplication and test-order handling: thank-you page refresh does not refire; test order is marked in first-week reconciliation.
Signal source responsibility router: decide whether Ads, GA4, or Shopify owns the next check
Tracking QA cannot stop at one successful test order. When these mismatches appear, assign the first explanation to the right system before you keep spending.
| Symptom | Likely cause | Responsible source | Do not do |
|---|---|---|---|
| Ads shows conversions, Shopify has no order | Thank-you page view, test event, or duplicate trigger counted as purchase | Google Ads conversion action and tag trigger point | Do not let smart bidding keep learning from this conversion |
| Shopify has orders, Ads has no conversions | Google tag missing, conversion action unfinished, consent limited, or attribution window misunderstood | Google tag / GA4 event chain and Ads conversion status | Do not raise budget or swap keywords immediately |
| Order count is close, but value / currency is unclear | Tax-included revenue, amount paid, merchandise subtotal, or discounted value mixed together | Shopify revenue definition, GA4 purchase parameters, Ads conversion value | Do not use value-based bidding while value is unclear |
| All GA4 events are imported, bidding responsibility unclear | Primary / secondary was not decided; GA4 import and native Ads conversion are blended | Google Ads conversion goals and each conversion action status | Do not set every GA4 event as primary |
First-week reconciliation: confirm the system is learning the right action
1
Day 1: reproduce the test path and confirm primary / secondary settings; fix tracking before judging CPC / CTR.
2
Days 2-3: explain differences across Shopify orders, GA4 purchase, and Google Ads conversions; record time lag, attribution windows, test orders, and refunds.
3
Days 4-5: check whether value gap, currency, and transaction ID are stable; sample 10-20 orders.
4
Days 6-7: only after the signal is trusted, move into keyword, budget, and bidding review.
Stop / Go rules
| Stop | Go | Proof |
|---|---|---|
| Page view / session is primary | Primary keeps only real purchases or qualified leads | Conversion action setting screenshot |
| One order is learned by two primary conversions | One bids, the other observes only | Test order ID and dedupe notes |
| No value / currency / transaction ID evidence | Value, currency, and order ID reconcile across systems | Ads / GA4 / Shopify sample match |
| Test orders pollute reports long term | Test orders are marked, excluded, or explained | First-week daily reconciliation notes |
Handoff: bring the acceptance sheet into the next lesson
Before building the Search campaign, write four lines
- Primary conversion: which action is primary, and why it represents real business value.
- Observation events: which AddToCart / BeginCheckout / page engagement events are observation only.
- Test-order evidence: order ID, value, currency, transaction ID, and three-system match.
- First-week responsibility: responsible person, daily difference checks, and the signal that pauses budget actions.
Tracking is not technical cleanup. It is ad-system training data. The next Search campaign build only makes sense after this acceptance sheet passes.