Validate conversion signals before letting the ad system learn
Many accounts do not fail because ads cannot work. They start learning dirty signals: page visits, duplicate Purchase events, test orders, or the wrong primary conversion. More early budget only speeds up bad learning.
Lesson artifact: Google Ads conversion launch acceptance sheet
Use order ID, value, currency, transaction ID, primary conversion, and first-week reconciliation to block dirty signals.
Pre-launch status
1/6
Without order ID, value, currency, and dedupe proof, scaling and smart bidding discussions should wait.
Google Ads Basics 02
Bring the previous article's choice map here: campaign role is not launch permission
Google Ads Basics: Choose Search, Shopping, or PMax decides which traffic path is worth reading first; it does not prove that the account is ready to scale. This lesson keeps the 20oz leak-proof travel mug case and proves that account setup, tag source, primary conversion, order dedupe, value, and currency can carry a real business action into Google Ads. Until that proof exists, even Search is only a narrow preparation path, and Shopping or PMax cannot replace QA with “let it run for a few days.”
Bring from the previous article
The business question, starting campaign, hold list, check window, and first evidence fields.
This lesson verifies
Account and billing, signal source, primary / secondary status, transaction ID, value, currency, and the Ads / GA4 / Shopify comparison.
Next route
Enter Google Search Campaigns: Keywords, Ad Groups, and Landing Pages after the sheet passes; route feed or value-quality gaps to Merchant Center or the later enhanced-conversions lesson.
Make one order explainable first
Conversion tracking is not finished when a tag is installed; prove which real business action the system learned
The previous article, Google Ads Basics: Choose Search, Shopping, or PMax, introduced the 20oz leak-proof travel mug. The owner is preparing a small Search launch. Test order #10021 is 59 USD in Shopify, but a thank-you-page refresh fires Purchase again, while both the GA4 import and Google Ads tag record a purchase. AddToCart is also set as a primary conversion. The report looks busy and may even show two purchases, but it does not answer the key question: which signal should steer bidding, and which one only helps us understand the funnel?
The model to use is account → signal source → conversion role → dedupe → value definition → cross-system reconciliation. A primary conversion is the action Google Ads uses for optimization; a secondary conversion is for observation. Do not put every event in one bucket. Purchase or a qualified Lead may be eligible as primary only after amount, currency, order ID, test-order exclusion, and business definition are checked. Page view, AddToCart, and BeginCheckout explain funnel progress, but do not automatically represent deliverable revenue. Enhanced Conversions address matching quality; they do not repair duplicate or wrong Purchases.
Turn #10021 into executable QA: record source and primary/secondary status in the Google Ads conversion action; use tag debugging or a test order to confirm one valid Purchase, then match the transaction ID across Shopify, GA4, and Ads; finally sample real orders across anomalies, refunds, currency, and value definitions to reconcile value, currency, discounts, tax, shipping, and refund treatment. The sample size is a troubleshooting scope, not a Google launch threshold. If one system undercounts or overcounts, write it as a tracking gap and assign data or engineering ownership instead of changing budget or bids first.
Passing does not require every platform number to be identical. It requires differences to have an explainable timing, attribution, or definition boundary, and the primary signal to represent the business goal for this round. Only then take the choice map into Google Search Campaigns: Keywords, Ad Groups, and Landing Pages. If Purchase dedupe, value, or currency is still untrusted, hold scale. The current evidence can show that the system is more likely to read the action correctly; it does not guarantee immediate profit or decide page, feed, or margin quality.
Prove that one real business action is recorded once and has a clear primary/secondary role before letting the system learn from it.
Understand the risk first
Without trusted conversions, the ad system spends blind
Google Ads does not learn from your verbal goal. It learns from the primary conversion, value, currency, and transaction ID you send. If the signal is wrong, the system does not become smarter; it spends faster in the wrong direction.
Cheap actions treated as revenue
What the dirty signal looks like
AddToCart, BeginCheckout, or page view is set as the primary conversion while Purchase only observes.
What the system learns
The system learns to find easier carts or visits, not necessarily people who pay, refund less, and leave profit.
Check this first
Check Google Ads conversion actions first: Purchase should be primary, funnel events should be secondary.
One order learned twice
What the dirty signal looks like
Thank-you page refreshes, old tags, GA4 imports, and Ads tags can make one order appear as two Purchases.
What the system learns
ROAS looks better, smart bidding thinks traffic quality is higher, and later budget decisions get inflated.
Check this first
Reconcile transaction ID across Shopify, GA4, and Google Ads. One order should map to one valid Purchase.
Wrong value or currency
What the dirty signal looks like
Shopify shows 59 USD, but GA4 / Ads receives 59 CAD, or tax, shipping, and refund rules are mixed together.
What the system learns
Value-based bidding learns the wrong customer value, especially hurting tROAS and Maximize conversion value.
Check this first
First make one test-order path explainable, then sample by signal quality to reconcile value, currency, discount, tax, shipping, refund, and transaction_id.
Plain terms first
These are not backend fields; they are training data
Beginners often treat tracking as technical cleanup. In practice, primary conversion, value, currency, and transaction ID directly shape what the system learns.
Google tag
The Google tag is Google’s measurement tag on your site. It sends visits, events, and conversion signals to systems such as Google Ads or GA4.
- Where you see it
- You see it in Google Ads conversion setup, GA4 data streams, Google Tag Manager, or Shopify integrations.
- What breaks
- Duplicate, missing, or misplaced tags can miss purchases, double count them, or treat page visits as revenue signals.
- Ecommerce example
- For a 20oz tumbler test order, Purchase should fire once only after a real completed order.
primary conversion
A primary conversion is the core action Google Ads uses for bidding and optimization. Ecommerce usually uses Purchase; lead businesses may use qualified Lead.
- Where you see it
- You see primary / secondary status in Google Ads conversion action settings.
- What breaks
- If page view, session, or test orders become primary, the system learns toward the wrong goal.
- Ecommerce example
- Purchase is primary; AddToCart can observe interest but should not replace Purchase as the long-term revenue signal.
secondary conversion
A secondary conversion is for observation, not bidding. It helps read the funnel without competing with the real business goal.
- Where you see it
- Common secondary events include AddToCart, BeginCheckout, page engagement, or supporting leads.
- What breaks
- If secondary events stay as primary targets, low-quality visits may be treated as success.
- Ecommerce example
- A tumbler campaign can monitor add-to-cart, but budget decisions should return to Purchase, order quality, and contribution profit.
enhanced conversions
Enhanced conversions use hashed first-party customer data to help Google match conversions more reliably.
- Where you see it
- You see it in Google Ads conversion settings, tag diagnostics, and purchase or form-path setup.
- What breaks
- It is not a patch for broken basics. If Purchase, value, currency, or transaction ID are unstable, fix those first.
- Ecommerce example
- After the purchase path passes order value and email data correctly, enhanced conversions can improve match quality.
transaction ID
Transaction ID is the unique order identifier. Ad and analytics systems use it to detect duplicate purchase records.
- Where you see it
- You see it in Shopify orders, GA4 purchase events, Google Ads conversion details, or tag debugging.
- What breaks
- Missing or repeated transaction IDs can double count one order, inflating ROAS and bidding signals.
- Ecommerce example
- Test order #1008 should map to the same business action in Shopify, GA4, and Google Ads.
Main artifact
Google Ads conversion launch acceptance sheet
This sheet merges account access, tags, primary conversion, dedupe, value, and first-week review into one launch gate. Do not move to budget and bidding before it passes.
Toggle only layers with evidence. If there is no path record, order ID, or reconciliation note, leave it off; unchecked layers are pre-launch work.
Primary / secondary decision
Decide what bids and what only observes
Multiple sources are not the problem. The problem is one order being learned by multiple primary conversions. Ecommerce accounts should separate purchase signals from observation events.
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.
Source roles
Google Ads, GA4, and Shopify are not the same report
The numbers do not have to match perfectly, but the differences must be explainable. Otherwise keyword, budget, and bidding decisions inherit bad definitions.
Google Ads
Bidding and delivery learning system.
Primary conversions, conversion value, bid strategy, and 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-offs.
Do not import every event into Ads bidding without review.
Shopify
Order and revenue baseline.
Order ID, net sales, refunds, discounts, tax, and shipping.
Do not expect it to explain ad attribution windows.
Shopify measurement source inventory
Know who is sending Purchase
One Shopify store can have an app, GTM, Customer events / Pixels, checkout / order status page code, or old scripts sending signals. Inventory the sources before launch so one order is not trained by multiple primary conversions.
Google & YouTube app
Whether Google Ads, Merchant Center, and GA4 are connected, and whether purchase events are sent automatically.
Record app status, account IDs, and whether it duplicates the Ads tag or GA4 import.
GTM / Google tag
Tag ID, trigger rule, and whether Purchase fires only after a real completed order.
Record tag source, trigger page, transaction_id, value, and currency.
Customer events / Pixels
Whether a Shopify pixel sends purchase independently and whether consent status changes availability.
Record pixel name, responsible team, consent mode, and test-order proof.
checkout / order status page
Whether old thank-you page scripts, order status page scripts, or historical app code still exist.
Record the decision for old code: keep, disable, or migrate to the single source.
Orders / Timeline / Refunds
Order ID, payment status, refunds, discount, tax, shipping, and currency.
Use the Shopify order as the business reference record for explaining Ads / GA4 gaps.
Account / conversion / enhanced conversion paths
Do not only say setup is done; record the admin path and acceptance fields
These four paths turn account setup, conversion setup, and enhanced conversions into reviewable evidence. Admin path, fields, blocked moves, and next route must be clear before the next Search campaign learns from the signal.
Acceptance path
Account / billing / access path
- Where to look
- Google Ads -> Admin -> Account settings / Billing / Access and security; also record linked accounts for GA4, Merchant Center, Shopify, or partner access.
- Fields to record
- Customer ID, account name, time zone, currency, billing profile, payment status, admin users, standard users, linked account ID, and who can edit conversion goals.
- Acceptance proof
- It proves this is not an informal personal account: billing can charge, currency and time zone will not distort week-one reads, and access changes are accountable.
- Do not click
- Do not create the live campaign while time zone, currency, or billing is uncertain; do not let multiple people share one admin login.
- Next route
- Before the first Search campaign, write account ID, responsible team, billing status, and access boundary into the copyable lesson notes.
Acceptance path
Google tag / GA4 import / Shopify event path
- Where to look
- Google Ads -> Goals -> Conversions -> Summary / Diagnostics; GA4 -> Admin -> Key events / Product links; Shopify -> Customer events / Pixels / checkout path.
- Fields to record
- Tag ID, conversion action source, GA4 property ID, key event name, link status, auto-tagging, gclid / gbraid / wbraid status, Shopify pixel / app source, and trigger page.
- Acceptance proof
- It proves whether Google Ads is reading an Ads tag, a GA4 imported conversion, or a Shopify / GTM path, and that one business action is not trained twice.
- Do not click
- Do not import every GA4 key event as primary; do not duplicate-install the Google tag for "safety."
- Next route
- Route into GA4 setup: use key event, source / medium, landing page, and purchase parameters as reconciliation sources.
Acceptance path
Conversion action / primary-secondary / goal path
- Where to look
- Google Ads -> Goals -> Conversions -> Summary -> conversion action detail; then check campaign goal, custom goal, Include in Conversions, counting, attribution, and status.
- Fields to record
- Conversion action name, source, primary / secondary, category, counting method, conversion window, attribution model, Include in Conversions, campaign goal usage, conversion goals status record, and diagnostics.
- Acceptance proof
- It proves which action trains bidding and which actions only observe; Purchase, Lead, AddToCart, and BeginCheckout are not all competing for the main learning signal.
- Do not click
- Do not make page view, session, AddToCart, and BeginCheckout all primary; do not ignore custom goals that can pull secondary actions back into bidding.
- Next route
- Route into the first Search campaign: campaign goal must match the primary conversion accepted in this lesson.
Acceptance path
Enhanced conversions / value / transaction ID path
- Where to look
- Google Ads -> Conversions -> enhanced conversions / Diagnostics; GA4 -> purchase parameters; Shopify -> Orders / Timeline / Refunds; return to GTM or Shopify pixel fields when needed.
- Fields to record
- Hashed email / phone availability, consent status, transaction ID, value, currency, tax, shipping, discount, refund, order status, diagnostics severity, and match quality note.
- Acceptance proof
- It proves enhanced conversions improve matching rather than defining revenue value; value-based bidding is only released after value, currency, and dedupe are trusted.
- Do not click
- Do not treat enhanced conversions passing as tROAS release; do not use Maximize conversion value while refunds, tax, and shipping logic are unclear.
- Next route
- Route into the enhanced conversions and value quality lesson with the test-order path and signal-quality order samples.
Beginner acceptance sequence
Accept these 6 steps in order; failed steps route back before ads
This section is for first-time Google Ads setup. Start from step 1 and click the point that is currently blocked. The current checkpoint shows proof to collect, the lesson to return to, what not to do, and the line to write into copyable lesson notes.
Current checkpoint
1. Accept account access and billing first
- Admin surface
- Google Ads -> Admin -> Account settings / Billing / Access and security.
- Proof to collect
- Customer ID, time zone, currency, billing profile / payment status, admin list, and who can edit conversion goals. Without these, the account is not operationally accountable.
- If this fails, route back
- If this fails, return to Basics / Shopify setup and stabilize store entity, payments, billing email, and permissions before conversion tracking.
- Do not do now
- Do not create a live campaign from an informal personal account, uncertain billing, or unclear currency/time zone.
- Write into copyable lesson notes
- Account ID, currency, time zone, billing status, and conversion-goal editor are written into the acceptance sheet.
Test-order evidence pack
Without an evidence pack, tracking is not done
Run at least one real-path QA. Record order ID, value, currency, transaction ID, and how the three systems line up.
Current copyable note
After adding evidence, copy this into the launch acceptance sheet, team task, or the next Search campaign build notes.
Copyable lesson notes: Google Ads conversion launch acceptance sheet Accepted layers: Account basics Test-order evidence: Add order ID, value, currency, and transaction ID Three-system reconciliation: Add whether Ads / GA4 / Shopify map to the same business action Current acceptance step: 1. Accept account access and billing first - Account ID, currency, time zone, billing status, and conversion-goal editor are written into the acceptance sheet. Dirty signal: 20oz test order double-counted Purchase Repair action: Fix duplicate firing first Write back to acceptance sheet: Dedupe proof: Shopify #1008 should map to GA4 purchase 1 and Ads conversion 1; thank-you page refresh does not refire. First-week responsibility: Add responsible person, daily checks, and the signal that pauses budget actions Next route: Fix tracking and acceptance gaps before budget, keyword, or bidding decisions
20oz conversion signal practice
Choose the dirty signal, then choose the repair
The same 20oz tumbler test order can reveal duplicate Purchase, wrong primary settings, currency mismatch, or every GA4 event imported. Practice the decision before sending dirty signals into spend and smart bidding.
Step 1: choose the dirty signal
Step 2: choose the repair action
Instant feedback
Good action20oz test order double-counted Purchase
Your selected action
Fix duplicate firing first
When thank-you page refresh or multiple tags fire Purchase for one order, fix trigger rules and transaction ID first.
Good action
Good: check thank-you page refresh, GTM triggers, Google tag, and transaction ID before more learning.
Write back to the acceptance sheet
Dedupe proof: Shopify #1008 should map to GA4 purchase 1 and Ads conversion 1; thank-you page refresh does not refire.
Do not do this
Do not judge ROAS, CPA, or tROAS while duplicate firing is unresolved.
Conversion architecture selector and launch gate
Choose one explainable Purchase route before deciding whether it can bid
This is a classroom workbench: it puts Google & YouTube app, GTM / Google tag, GA4 import, and custom pixel on one architecture map, then uses one test order to check duplicates. It saves only in this browser and does not write to Google Ads, GA4, Shopify, or any account.
Read the admin state first, then check the classroom gate
Buttons and fields only organize acceptance notes. They do not install tags, change goals, enable consent mode, or launch ads. A wrong choice explains why the gate cannot release.
Current installation route
Google & YouTube app
- Read back first
- First verify the connected Google Ads account and the app-provided purchase measurement route in Shopify’s Google & YouTube channel, then read the conversion action in Google Ads Goals.
- Primary boundary
- A connected app does not make every event biddable. Still confirm which Purchase action is primary in Google Ads and which goal the campaign uses.
- Duplicate risk
- A common risk is adding a manual Ads tag or GTM Purchase route beside the app route, producing two purchase signals for one order.
Which signal may train bidding
This is not an automatic result of the installation route. Choose the bidding Purchase you will read back item by item in Google Ads Goals, or explicitly hold when evidence is missing.
Current readback
Goals > Conversions > Summary: action source, primary/secondary, value, counting, transaction_id, and the campaign goal.
If the same Purchase is also primary through a GA4 import, stop and resolve double learning first.
Duplicate-conversion experiment
Use one classroom test order to test the path, not order volume to hide a problem
Google & YouTube app and GTM both send Purchase
Experiment verdict is sound
This case should not release. First list the conversion action, primary/secondary status, and campaign goal for both routes, then retain one explicit bidding Purchase.
Launch gate
Judge by signal quality, not a fixed order count
The older 10 to 20 order sample is a classroom QA prompt, not a Google launch threshold. No fixed order count, event count, or number of days replaces readback of one order path, goal scope, dedupe, consent, value, and currency.
Current classroom conclusion
Keep the hold: complete the readbacks and evidence fields below before deciding whether to enter campaign setup.
Classroom gate: 0/6 readbacks, 0/4 records
Save and export handle only this browser’s classroom record. The export is marked classroomOnly: true.
First-week reconciliation
In week one, confirm the system is learning the right action
The first-week goal is not scaling. It is proving that Shopify orders, GA4 purchases, and Google Ads conversions have explainable differences.
Day 1
Test path reproduces, primary/secondary settings are correct.
Fix tracking first, before judging CPC/CTR.
Days 2-3
Shopify orders, GA4 purchases, and Google Ads conversions are explainable.
Record time lag, attribution windows, test orders, and refunds.
Days 4-5
Value gap, currency, and transaction ID are stable.
Sample across anomalies, refunds, currency, and value definitions so averages do not hide duplicates or missing values.
Days 6-7
Only after signal trust should keyword, budget, and bidding reviews start.
Write the acceptance result into the next ad action.
Signal source responsibility router
First decide whether Ads, GA4, or Shopify owns the next check
A test order is only the entry point. Before launch, know which system should explain each mismatch first, or week-one data will distort later keyword and budget decisions.
Click the symptom that matches the current mismatch. The current result panel shows which system owns the first explanation, what evidence to pull, and what must be fixed before spend.
Current route
Ads shows conversions, Shopify has no order
- Likely cause
- A thank-you page view, test event, or duplicate trigger may be counted as purchase.
- Responsible source
- Check the Google Ads conversion action and tag trigger point first.
- Evidence to pull
- Conversion action settings, Tag Assistant / GTM firing record, and Shopify order list.
- Do not do
- Do not let smart bidding keep learning from this conversion.
Fix before spend
Return to tag trigger conditions; Purchase must fire only after real order completion and include transaction ID.
Stop / Go
Stop and go rules for conversion launch
Mistakes, full QA, and counter-evidence reminders become an executable boundary.
Page view / session is primary
Primary keeps only real purchases or qualified leads
Conversion action status record
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
Three release levels
Do not treat a visible Purchase as tROAS release
Split acceptance into tracking-only, campaign-ready, and value-bidding-ready so unstable value and dedupe do not enter automated bidding too early.
tracking-only
Only proves that the tag, GA4, and Shopify order path can run, so the team can keep collecting proof.
Do not create the live campaign and do not let the signal train bidding.
campaign-ready
Purchase or qualified Lead is primary, and the test order, transaction_id, value, and currency are explainable. The first Search campaign can be built.
Do not move straight into Maximize conversion value / tROAS or large-budget scaling.
value-bidding-ready
The test-order path and signal-quality order samples are explainable, and refunds, discounts, tax, shipping, currency, and dedupe are trusted. Value-based bidding can be discussed.
If enhanced conversions only pass diagnostics while value definitions are unstable, tROAS is still blocked.
Official setup boundaries
Official docs prove setup conditions, not business signal quality
This lesson is not about memorizing admin paths. It is about knowing what each official setting can prove, how to use it in the acceptance sheet, and what it cannot prove for the business.
Consent / privacy boundary
Enhanced Conversions use hashed first-party customer data; the acceptance sheet must record consent status, data source, field availability, and diagnostics results. Consent mode, Customer events / Pixels, and checkout scripts affect event availability, but modeled conversions do not replace Shopify order truth.
Primary / secondary conversion actions
- Can prove
- Primary actions generally appear in the Conversions column and are used for bidding; secondary actions are usually observation-only. But a secondary action inside a custom goal can still be used for bidding.
- Acceptance-sheet use
- The acceptance sheet should check more than the primary/secondary label; it must also check which goal the campaign uses and whether a custom goal exists.
- Cannot prove
- It does not prove that Purchase is always a high-quality order or that every secondary action can never affect bidding.
Google tag and website conversion setup
- Can prove
- The Google tag should be configured correctly on the site; when an existing Google tag is already present, the job is usually to adapt it for the Ads account, not duplicate-install another tag.
- Acceptance-sheet use
- During acceptance, document the tag source: Google tag, GTM, Shopify integration, or GA4 import, and check for duplicate firing.
- Cannot prove
- It does not prove that Purchase fires only once or that value, currency, and transaction ID are correct.
Dynamic value requirements
- Can prove
- Before dynamic values are set, you need the conversion page URL, the trigger, and available conversion value, transaction ID, and currency where the tag fires.
- Acceptance-sheet use
- Turn value / currency / transaction ID from a setting claim into test-order proof: values exist on the page, the tag reads them, and Ads/GA4/Shopify reconcile.
- Cannot prove
- It does not prove the value definition is right for profit review; tax, shipping, discounts, and refunds still need a business definition.
GA4 key events imported into Google Ads
- Can prove
- GA4 events / key events can be created as Google Ads conversions, but this requires an Analytics-Ads link, auto-tagging, and the right permissions.
- Acceptance-sheet use
- Before importing, write which event trains bidding and which events only observe; also check whether credit is paid-only or paid-and-organic.
- Cannot prove
- It does not prove every GA4 key event should be imported, and it definitely does not prove every imported event should become a primary conversion.
Enhanced conversions in Ads vs Analytics
- Can prove
- Enhanced conversions serve a similar purpose in Google Ads and GA4, but whether you configure Ads, GA4, or both depends on which platform provides the bidding signal.
- Acceptance-sheet use
- The acceptance sheet should state the bidding signal source: Ads conversion tracking for bidding or GA4 imported conversions for bidding.
- Cannot prove
- It does not repair broken baseline tracking, and it does not automatically solve double-learning when the same purchase is primary in both Ads and GA4.
Conversions column and modeled conversions
- Can prove
- The Conversions column shows conversions from primary conversion actions and may include modeled conversions when conversions cannot be directly observed; All conversions includes more secondary / view-through signals.
- Acceptance-sheet use
- In week-one reconciliation, read Conversions, All conversions, GA4 purchase, and Shopify orders separately instead of blending them into one revenue table.
- Cannot prove
- It does not prove Ads numbers equal Shopify net sales, and it cannot prove ad profit by itself.
Closeout
Tracking is not technical cleanup. It is ad-system training data. The next Search campaign build only makes sense after this acceptance sheet passes.