Skip to content
Ecomwith

Google Ads Setup: Account and Conversion Signal QA

  • Beginner
  • 54 minutes

An ad system learns from the conversion signals you send. Identify the sending route and bidding goal, then examine the order, value, currency, and dedupe evidence. Reported purchases need supporting order records.

Series start

QA the signal before choosing the next move

A Shopify store is preparing a small Search campaign for a leak-proof commute tumbler. The hero version is 20oz, aimed at English-speaking buyers in Canada; classroom order values are recorded in USD. These details establish no merchant, payment, or ad-account eligibility, and no previous lesson is needed. Test order #10,021 is 59 USD in Shopify. A thank-you-page refresh fires Purchase again, both a GA4 import and a Google Ads tag record it, and AddToCart is also primary. Resolve the goal and source problem before using that report to justify scale.

The work here is to read fields, gather evidence, and make a checkable decision. This page does not sign in to a store, install tags, create ads, charge a payment, or issue a refund. An authorized person must choose a controlled test method actually available for the store. Leave checks unverified when they have not been performed.

Note Do these three things today

  1. Open the conversion actions and write each name, source (Shopify, GA4, or manual), and counting (every or unique). 2. Take one order and compare order ID, value, and currency across the Ads conversion, GA4 purchase, and the Shopify order. 3. Mark mismatched fields "to verify" with who will check them and where.

Understand tags, actions, and goals

Purchase records a purchase event, AddToCart an add-to-cart event, and BeginCheckout the start of checkout. A qualified Lead meets the business’s stated qualification criteria. A tag sends the data, a conversion action defines what is recorded, and a goal determines how the campaign uses those actions. These distinctions matter when you read the account fields.

Terms used in this QA

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.If misread Duplicate, missing, or misplaced tags can miss purchases, double count them, or treat page visits as revenue signals.Example: For a 20oz tumbler test order, Purchase should fire once only after a real completed order.
primary conversion

A primary conversion is a business action intended for optimization; its standard goal must also be used by the current campaign. Ecommerce usually checks Purchase, while a lead business may use a qualified Lead.

Where you see it You see primary / secondary status in Google Ads conversion action settings.If misread If page view, session, or test orders become primary, the system learns toward the wrong goal.Example: Purchase is primary; AddToCart can observe interest but should not replace Purchase as the long-term revenue signal.
secondary conversion

A secondary conversion normally supports funnel observation. If it belongs to a custom goal, it is still used for bidding, so check the campaign’s goal as well.

Where you see it Common secondary events include AddToCart, BeginCheckout, page engagement, or supporting leads.If misread If secondary events stay as primary targets, low-quality visits may be treated as success.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.If misread It is not a patch for broken basics. If Purchase, value, currency, or transaction ID are unstable, fix those first.Example: Verify the purchase path and value first. Use the relevant hashed data through supported enhanced-conversion features only when the applicable permissions and data policies allow it.
transaction ID

Transaction ID is the unique order identifier. Ad and analytics systems use it to detect duplicate purchase records.

Where you see it Check it in Shopify orders, GA4 purchase parameters, and actual tag requests. Google Ads does not report transaction IDs as a report column.If misread A missing ID can let the same purchase count again; reusing an ID for different orders can instead undercount. Both distort ROAS and the bidding signal.Example: Test order #1,008 should map to the same business action in Shopify, GA4, and Google Ads.

Enhanced Conversions improve matching. They do not repair a wrong primary action, duplicate Purchase, missing transaction ID, or wrong value/currency. Stabilize the basic order path before interpreting the additional diagnostics.

Separate business actions and system roles

The same business event has different meanings in these systems. Write down the question each column answers before trying to match its number. An action named Purchase is not proof of a valid order; a qualified Lead also needs a business definition.

What each event can support

  • Purchase / qualified Lead

    Business role
    Real business value action
    Bidding role
    Can be primary
    QA boundary
    Must verify value, currency, dedupe, and test-order exclusion.
  • AddToCart / BeginCheckout

    Business role
    High-intent observation signal
    Bidding role
    Usually secondary over the long term
    QA boundary
    Useful for funnel reading, but should not replace revenue for long.
  • Page view / Session

    Business role
    Visit quality observation
    Bidding role
    Should not be primary
    QA boundary
    Can optimize toward cheap visits instead of purchases or qualified leads.
  • Test order

    Business role
    QA evidence
    Bidding role
    Should not pollute reports long term
    QA boundary
    Unmarked test orders inflate early performance.

Do not blend the systems into one revenue table

  • Google Ads

    Question it answers
    The place to review and manage bidding and ad delivery.
    Readback
    Primary conversions, conversion value, bid strategy, and ad attribution.
    What it cannot replace
    Do not use alone as the finance revenue baseline.
  • GA4

    Question it answers
    Site behavior, source path, and funnel analysis system.
    Readback
    Event quality, source/medium, page path, funnel drop-offs.
    What it cannot replace
    Do not import every event into Ads bidding without review.
  • Shopify

    Question it answers
    Order and revenue baseline.
    Readback
    Order ID, net sales, refunds, discounts, tax, and shipping.
    What it cannot replace
    Do not expect it to explain ad attribution windows.

A primary action is used for bidding under that setting when its standard goal is used by the campaign. Secondary actions normally appear in All conversions for observation. A custom goal is an important exception: its actions are used for reporting and bidding whether primary or secondary. Check account-default, campaign, and custom goals rather than relying on the optimization label alone. Official scope.

Find the signal that would mislead learning

  • Cheap actions treated as revenue

    Dirty signal
    AddToCart, BeginCheckout, or page view is set as the primary conversion while Purchase is left as observation-only.
    What the system learns
    The system learns to find people who are easy to bring to a page or cart, not necessarily buyers who complete payment, request fewer refunds, and leave contribution profit.
    First check
    Check Google Ads conversion actions first: Purchase should be primary, funnel events should be secondary.
  • One order learned twice

    Dirty signal
    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.
    First check
    Reconcile transaction ID across Shopify, GA4, and Google Ads. One order should map to one valid Purchase.
  • Wrong value or currency

    Dirty signal
    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.
    First check
    First verify one test order end to end, then sample orders by anomaly type and order quality to reconcile value, currency, discount, tax, shipping, refund, and transaction_id.

Inventory every Purchase sender

Inventory what is installed before adding a tag. An app, GTM, GA4 import, and old scripts can all send the same order. Record the system, account/tag/action IDs, owner, trigger, consent treatment, and keep-or-migrate decision for each route.

Five Shopify source locations to inspect

  • Google & YouTube app

    First readback
    Whether Google Ads, Merchant Center, and GA4 are connected, and whether purchase events are sent automatically.
    Record
    Record app status, account IDs, and whether it duplicates the Ads tag or GA4 import.
  • GTM / Google tag

    First readback
    Tag ID, trigger rule, and whether Purchase fires only after a real completed order.
    Record
    Record tag source, trigger page, transaction_id, value, and currency.
  • Customer events / Pixels

    First readback
    Whether a Shopify pixel sends purchase independently and whether consent status changes availability.
    Record
    Record pixel name, responsible team, consent mode, and test-order proof.
  • checkout / order status page

    First readback
    Whether old thank-you page scripts, order status page scripts, or historical app code still exist.
    Record
    Record the decision for old code: keep, disable, or migrate to the single source.
  • Orders / Timeline / Refunds

    First readback
    Order ID, payment status, refunds, discount, tax, shipping, and currency.
    Record
    Use the Shopify order as the business reference record for explaining Ads / GA4 gaps.

Caution Keep legacy sources distinct from new-install advice

For the Shopify store in this lesson, Google currently recommends migrating Google tags to the Google & YouTube app. Legacy checkout.liquid, Order status page Additional scripts, and Google tags inside custom pixels are not interchangeable new-installation choices. Shopify still documents a technical GTM custom-pixel route with sandbox limits; Google explicitly does not support running Google tags inside that custom-pixel environment. Those statements address different scopes and do not mean that all GTM implementations are invalid.

Google’s Shopify migration guidance and Shopify’s GTM sandbox tutorial describe provider support and technical capability respectively.

Exercise · pick one

Route being inspected

Stores that want the Shopify channel to handle the baseline connection and can state clearly which route sends Purchase.

Readback route
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.

A selected option identifies the route being inspected; it does not prove installation, migration, or provider support. An app connection still needs conversion-action and campaign-goal QA. Google Tag Assistant’s Troubleshoot tag feature is incompatible with Shopify custom pixels. Use the relevant Pixel Helper, event/request readback, and provider support boundaries rather than treating a missing debugger result as proof that no event fired.

Read the actual account fields

Use a consistent sequence: admin location, fields, proof, and the action that stays on hold. Menus vary with account access and product changes. Use the functional names to locate the current control, even when the menu layout differs.

Four evidence paths

  • Account / billing / access path

    Location and fields
    Google Ads -> Admin -> Account settings / Billing / Access and security; also record linked accounts for GA4, Merchant Center, Shopify, or partner access. Customer ID, account name, time zone, currency, billing profile, payment status, admin users, standard users, linked account ID, and who can edit conversion goals.
    Inspectable proof
    Read back account identity, billing status, currency, time zone, and access ownership. A status record does not guarantee a successful charge or merchant eligibility; week-one comparisons still need aligned time and monetary definitions.
    What stays held
    Do not create the live campaign while time zone, currency, or billing is uncertain; do not let multiple people share one admin login.
    Handoff
    Before the first Search campaign, write the account ID, owner, billing status, and access boundary in the handoff record.
  • Google tag / GA4 import / Shopify event path

    Location and fields
    Google Ads -> Goals -> Conversions -> Summary / Diagnostics; GA4 -> Admin -> Key events / Product links; Shopify -> Customer events / Pixels / checkout path. 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.
    Inspectable proof
    It shows whether Google Ads is reading an Ads tag, a GA4 imported conversion, or a Shopify / GTM path, and whether one business action is being used for training twice.
    What stays held
    Do not import every GA4 key event as primary; do not duplicate-install the Google tag for "safety."
    Handoff
    Route into GA4 setup: use key event, source / medium, landing page, and purchase parameters as reconciliation sources.
  • Conversion action / primary-secondary / goal path

    Location and fields
    Google Ads -> Goals -> Conversions -> Summary -> conversion action detail; then check campaign goal, custom goal, Include in Conversions, counting, attribution, and status. 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.
    Inspectable proof
    It shows which action trains bidding and which actions are observation-only; Purchase, Lead, AddToCart, and BeginCheckout are not all competing for the main learning signal.
    What stays held
    Do not make page view, session, AddToCart, and BeginCheckout all primary; do not ignore custom goals that can pull secondary actions back into bidding.
    Handoff
    Route into the first Search campaign: the campaign goal must match the primary conversion approved by this QA.
  • Enhanced conversions / value / transaction ID path

    Location and fields
    Google Ads -> Conversions -> enhanced conversions / Diagnostics; GA4 -> purchase parameters; Shopify -> Orders / Timeline / Refunds; return to GTM or Shopify pixel fields when needed. Hashed email / phone availability, consent status, transaction ID, value, currency, tax, shipping, discount, refund, order status, diagnostics severity, and match quality note.
    Inspectable proof
    It shows that enhanced conversions improve matching rather than define revenue value; value-based bidding should proceed only after value, currency, and dedupe are trusted.
    What stays held
    Do not treat enhanced conversions passing as tROAS release; do not use Maximize conversion value while refunds, tax, and shipping logic are unclear.
    Handoff
    Route into the enhanced conversions and value quality lesson with the test-order path and signal-quality order samples.

Check permissions for the action you are performing. The Analytics–Ads linking instructions require Analytics property administrator/editor access and Google Ads administrative access. Analytics Conversion management instead specifies at least Marketer access, and the feature may not be available for every property. Verify the current entry point, property, Ads account, auto-tagging, and available events; do not apply one flow’s access rule to every import path. Linking access; Analytics conversion management.

Work through the account and order checks in this sequence. Record what you find, where missing evidence must be resolved, and which actions remain on hold. Use only a permitted test method that is available for the store. Paying and then refunding a real order is one inherited example of a possible check, not this lesson’s default instruction.

From account access to order QA

  1. Validate account access and billing first

    Google Ads -> Admin -> Account settings / Billing / Access and security.

    If this fails, return to Basics / Shopify setup and stabilize store entity, payments, billing email, and permissions before conversion tracking.

    Write the account ID, currency, time zone, billing status, and conversion-goal editor into the acceptance sheet.

    Keep as evidence

    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.

    How to confirm

    Do not create a live campaign from an informal personal account, uncertain billing, or unclear currency/time zone.
  2. Validate the Google tag source

    Google Ads conversion tag, Google tag, GTM, Shopify Google & YouTube app, or Customer events / Pixels.

    If this fails, return to Basics / system integration or GA4 setup and make the test-order chain work first.

    Write the Google tag source, trigger page, Purchase trigger condition, and duplicate-firing check into the acceptance sheet.

    Keep as evidence

    Tag ID, implementation source, trigger page, Purchase trigger condition, existing tag status, and duplicate-install check. A tag alone is not enough; the team needs to know which tag sends Purchase to Google Ads.

    How to confirm

    Do not duplicate-install the Google tag for safety; do not release Purchase only because a tag fired.
  3. Validate the GA4 import boundary

    GA4 -> Admin -> Key events / Product links; Google Ads -> Goals -> Conversions -> New conversion action / Import.

    If this fails, return to GA4 setup / GA4 event QA and fix key event, source / medium, purchase parameters, and Ads link.

    Write the GA4 import property, key event, link status, auto-tagging, and primary / secondary roles into the acceptance sheet.

    Keep as evidence

    GA4 property ID, key event name, link status, auto-tagging, gclid / gbraid / wbraid, and paid-only or paid-and-organic credit setting. Decide which event trains bidding and which only observes.

    How to confirm

    Do not import every GA4 key event into Ads and make all of them primary.
  4. Validate the Shopify event and order chain

    Shopify -> Orders / Timeline / Customer events / Pixels / checkout path.

    If this fails, return to Basics / payment gateway / system integration and prove the real order chain works.

    Write the Shopify order ID, order status, pixel / app source, trigger page, and test-order handling into the acceptance sheet.

    Keep as evidence

    Test order ID, payment status, refund or test marker, pixel / app source, trigger page, and Shopify order timeline. Shopify is the order baseline, not the Ads attribution-window explainer.

    How to confirm

    Do not treat "Ads has no conversions" as a keyword or budget problem immediately; check the order and event chain first.
  5. Validate the primary conversion and campaign goal

    Google Ads -> Goals -> Conversions -> conversion action detail; campaign goal / custom goal / Include in Conversions.

    If this fails, return to the earlier conversion-role checks and GA4 event QA; fix conversion goals before building the first Search campaign.

    Write the primary conversion, secondary events, campaign goal, and custom-goal check results into the acceptance sheet.

    Keep as evidence

    Conversion action name, source, primary / secondary, counting, attribution, conversion window, and campaign goal usage. Purchase or qualified Lead trains bidding; AddToCart / BeginCheckout only observe.

    How to confirm

    Do not let page view, session, AddToCart, or BeginCheckout become the first-round learning target.
  6. Finally validate transaction_id, value, and currency

    Google Ads diagnostics, GA4 purchase parameters, Shopify Orders / Refunds; return to GTM or Shopify pixel fields when needed.

    If this fails, return to enhanced conversions and value quality check / GA4 revenue refund lessons and fix value definition and dedupe.

    Write transaction_id, value, currency, the order sample, refund/discount definition, and the value-bidding QA conclusion into the acceptance sheet.

    Keep as evidence

    Transaction_id, value, currency, tax, shipping, discount, refund, order status, and orders sampled by anomaly and business quality. Do not proceed to value-based bidding until these values are trusted.

    How to confirm

    Do not use Maximize conversion value / tROAS while transaction_id is missing, currency mismatches, or refund logic is unclear.
Exercise · pick one

Current setup check

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.

Admin path
Google Ads -> Admin -> Account settings / Billing / Access and security.
Failure route
If this fails, return to Basics / Shopify setup and stabilize store entity, payments, billing email, and permissions before conversion tracking.
Write into the sheet
Write the account ID, currency, time zone, billing status, and conversion-goal editor into the acceptance sheet.

Read value, currency, and dedupe from one order

Order #10,021 is the opening failure case. Order #1,008 is a separate practice example below. Start with Shopify Orders / Timeline / Refunds, then compare GA4 purchase parameters and Google event/tag diagnostics: order ID, transaction_id, value, currency, tax, shipping, discount, refund, and actual order status all need an explanation.

Matching amounts also need matching definitions. Sending 59 as CAD does not match a 59 USD order. Define tax, shipping, discounts, and refunds before comparing Ads, GA4, and net sales. When the confirmation page is reopened or refreshed, check whether repeated requests are deduplicated by transaction ID within the same conversion action. Never hardcode one ID across different orders. Google Ads does not report transaction IDs as a report column; inspect actual tag requests, implementation records, and relevant diagnostics instead of inventing an order-level field in the Ads report.

A test order proves a measurement path, not necessarily an attributable ad interaction. The classroom Ads = 1 traces assume attribution eligibility and an elapsed reporting delay. A real test that does not become an ad conversion, or temporarily differs across systems, has not automatically failed. Separate reporting time, attribution window, delay, refund, discount, test marking, and duplication before changing budgets.

Transaction-ID scope and limits; reporting columns and time basis.

Dynamic values must actually be available where the event fires. A URL-only confirmation-page rule does not establish transaction-specific value or ID collection. Inspect how an existing Google tag is adapted rather than pasting another one. Enhanced-conversion setup in Ads and Analytics depends on the bidding source and usually does not automatically configure both. If both measure the same purchase, prevent both actions from becoming competing primary signals.

Record consent state, data provenance, field availability, and diagnostics. Hashing does not grant permission to use data. Google’s customer-data policy requires disclosure, consent where legally required, and additional sensitive-category restrictions. The responsible team must check the applicable market, data, and implementation. Modelled conversions are not order-level revenue evidence. Use system names, classroom IDs, and redacted summaries in these notes, not customer names, email addresses, phone numbers, or raw user data. Record event availability and differences separately for the regions, browsers, and consent states you check; leave untested combinations unverified.

Keep the example distinct from your own evidence

The worked example starts with account basics recorded and the other five rows pending: 1/6. It remains a manually editable example, not one verified check in your account. Gather your own evidence separately. All four note fields start empty; hints are examples rather than filled answers.

The acceptance work and architecture record save, restore, and clear separately; each group’s buttons affect that group only. Copying or downloading notes does not save a record. Main-board selections and notes can now be saved even though the original page did not save them. Legacy recovery applies only to the architecture fields. The old textareas were unbounded; each long note allows 2,000 characters. Keep the original before condensing longer notes, and compare it after import.

Evidence behind each manual state

  • Account basics

    Meaning of the check
    Billing, time zone, currency, permissions, and the people who can make changes are auditable.
    Evidence
    Account settings path, field records, and permission list.
    Owner and timing
    Ads lead, before launch
  • Tag source

    Meaning of the check
    Google tag, GTM, Shopify integration, or GA4 import source is documented.
    Evidence
    Tag diagnostics, trigger page, and implementation path notes.
    Owner and timing
    Data lead, before launch
  • Primary conversion

    Meaning of the check
    Only Purchase or a qualified Lead should feed bidding.
    Evidence
    Conversion action primary / secondary status record.
    Owner and timing
    Ads lead, before launch
  • Deduplication evidence

    Meaning of the check
    One order counts once, and transaction ID is stable.
    Evidence
    Test order ID plus Ads / GA4 / Shopify reconciliation.
    Owner and timing
    Data lead, before launch
  • Value and currency

    Meaning of the check
    Value, currency, discount, tax, and shipping definitions are explainable.
    Evidence
    Order reconciliation sheet sampled by signal quality.
    Owner and timing
    Finance/data, first week
  • First-week review

    Meaning of the check
    Google Ads, GA4, and Shopify gaps have daily explanations.
    Evidence
    Daily reconciliation notes and mismatch handling.
    Owner and timing
    Growth lead, first 7 days

Main worked-example count

Note1/6 manual states
This reflects the manual states above, not verified account evidence.

The count reflects manual selections. Marking all six rows and choosing the correct current practice action opens the final admin-readback route below. It does not verify billing, tags, orders, consent, or a completed observation week, and it does not launch an ad.

Choose a repair for each dirty signal

The same tumbler can expose different measurement failures. Choose a case, then a repair action. Switching cases does not select the correct answer for you. Every trace is a classroom example. Use the feedback to explain what needs repair and why performance judgment must wait.

Exercise · pick one

Choose the signal case

One test order appears twice in GA4 and Google Ads, inflating ROAS.

Classroom evidence
Shopify #1,008 = 1 order; GA4 purchase = 2; Ads conversions = 2
Correct repair reference
Good: check thank-you page refresh, GTM triggers, Google tag, and transaction ID before more learning.
Risk of another action
Do not launch: duplicate Purchase makes the system think the same spend bought more orders.
Case acceptance line
Dedupe proof: Shopify #1,008 should map to GA4 purchase 1 and Ads conversion 1; thank-you page refresh does not refire.
What stays blocked
Do not judge ROAS, CPA, or tROAS while duplicate firing is unresolved.
Exercise · pick one

Your repair action

Rationale
When thank-you page refresh or multiple tags fire Purchase for one order, fix trigger rules and transaction ID first.

Current signal-decision feedback

Go

Good: check thank-you page refresh, GTM triggers, Google tag, and transaction ID before more learning.

Good: check thank-you page refresh, GTM triggers, Google tag, and transaction ID before more learning. Dedupe proof: Shopify #1,008 should map to GA4 purchase 1 and Ads conversion 1; thank-you page refresh does not refire.

A correct choice is not a completed account repair. Give the selected action and its evidence to the data or engineering owner, then retest the actual tracking gap. Duplication, goal hierarchy, currency mismatch, and importing every event are separate problems; keep those specific diagnoses in the retest record.

Choose the bidding source and dedupe conclusion separately

Bring the installed route, bidding source, and dedupe judgment into one architecture record. These remain independent choices. A historical GTM implementation does not decide today’s Shopify Google measurement route; selecting GA4 import does not automatically make that action safe for bidding.

Exercise · pick one

Bidding source under review

A verified Google Ads website Purchase conversion action through the Google tag or GTM.

Field readback
Goals > Conversions > Summary: inspect action source, primary/secondary, value, counting, and campaign goal. Check transaction_id separately in actual tag requests and test evidence.
Boundary
If the same Purchase is also primary through a GA4 import, stop and resolve double learning first.

The next traces use three other classroom orders: classroom-order-01, classroom-order-02, and classroom-order-03. They separate two sending routes, a same-action/same-ID reload, and GA4 plus native actions both set to primary. Transaction-ID dedupe is also different from Count=One: dedupe avoids counting the same purchase again; One limits conversions after an ad interaction and can omit later, distinct purchases.

Exercise · pick one

Choose the dedupe trace

One practice test order has two Purchase routes. Even with matching value and currency, do not assume only one will bid.

Event trace
Shopify test order: classroom-order-01; Google & YouTube app Purchase: recorded; GTM Google Ads Purchase: recorded; Google Ads Goals: both routes visible
Correct disposition reference
Keep this case on hold. First list the conversion action, primary/secondary status, and campaign goal for both routes, then retain one explicit bidding Purchase.
Risk if ignored
Launching directly can make reporting treat one order as two learning signals.
Exercise · pick one

Your dedupe verdict

Reason for this verdict
When one order has two routes, two primary actions, or an unclear goal scope, stop at conversion architecture and do not change budget.

Current dedupe feedback

Note

Correct for this trace; verify the hold or retest against evidence

Keep this case on hold. First list the conversion action, primary/secondary status, and campaign goal for both routes, then retain one explicit bidding Purchase.
Checklist0 / 6 items
Architecture evidence checks
  • Write which of Google & YouTube app, GTM / Google tag, GA4 import, and custom pixel exist, and which do not send Purchase.
  • In Google Ads Goals, record the conversion action, account-default or campaign-specific goal, and whether a custom goal brings a secondary action into bidding.
  • Record the consent mechanism, Google tag behavior, and whether user choices are passed appropriately; do not treat modeled conversions as Shopify orders.
  • Define the treatment of discounts, tax, shipping, and refunds, then see value, currency, and transaction_id in one explainable Purchase payload.
  • From Shopify Orders/Timeline to the tag or GA4, then to Google Ads Goals/diagnostics, record timing and attribution differences.
  • Confirm whether there is one valid Purchase, one ignored duplicate, or two actions that can both bid. If no verdict exists, keep the hold.

A route-inventory example might read: “The Google & YouTube app sends Purchase; GA4 import observes; the old GTM/custom pixel awaits verified retirement and retest.” Treat it as fact only after checking it. The test trace records order status and reopening; payload readback records ID, value, currency, and consent availability; the release note names the reviewer, level, and actions still held.

The architecture record is complete only with six checks, four nonblank evidence notes, the correct verdict for the selected duplicate case, and a primary choice other than hold-for-evidence. For some cases, hold-and-map is the correct answer. That can make the record complete while the actual launch remains on hold. “Record complete” means ready to take to an admin readback, not approved to advertise.

The record holds your own inputs and changes no external account. After restoring, check the original choices and note line breaks; a wrong answer stays wrong until you change it. The original save timestamp remains in the old record. A time shown for a new native save belongs to that save and does not impersonate the original timestamp.

Record completeness, not release authority

Use week-one reconciliation to choose the next check

Validate the signal before judging traffic and bids in the first week. Name the reviewer, the time basis for daily comparisons, and the discrepancy that stops interpretation. The inherited 10–20 order example is a troubleshooting sample covering anomalies, refunds, and currencies. It is not a Google launch or value-bidding threshold, and one clean order cannot establish that later orders are correct.

Week-one observation order

  • Day 1

    Check
    Test path reproduces, primary/secondary settings are correct.
    Action
    Fix tracking first, before judging CPC/CTR.
  • Days 2-3

    Check
    Shopify orders, GA4 purchases, and Google Ads conversions are explainable.
    Action
    Record time lag, attribution windows, test orders, and refunds.
  • Days 4-5

    Check
    Value gap, currency, and transaction ID are stable.
    Action
    Sample across anomalies, refunds, currency, and value definitions so averages do not hide duplicates or missing values.
  • Days 6-7

    Check
    Only after signal trust should keyword, budget, and bidding reviews start.
    Action
    Write the acceptance result into the next ad action.

A first-day shortfall can be a reporting delay. An unexplained gap that persists for days still prevents a performance conclusion. Mark test orders, exclude them where appropriate, or explain them separately in the review. If a tumbler order was paid and later refunded, Purchase, attributed Ads value, and Shopify net sales can legitimately differ. Record the refund treatment and timing rather than forcing the totals to agree.

When a gap appears, start with the responsible evidence source. Each route below identifies the first check, the evidence to retrieve, the repair, and the action that stays blocked. Choosing an audit route does not rewrite the saved architecture answers.

Exercise · pick one

Choose the current discrepancy

The account shows purchase, but the store order list has no matching order.

Possible cause
A thank-you page view, test event, or duplicate trigger may be counted as purchase.
First evidence source
Check the Google Ads conversion action and tag trigger point first.
Evidence to retrieve
Conversion action settings, Tag Assistant / GTM firing record, and Shopify order list.
Repair before spend
Return to tag trigger conditions; Purchase must fire only after real order completion and include transaction ID.
What stays blocked
Do not let smart bidding keep learning from this conversion.

State a release level with its evidence

These three levels are handoff terms used in this lesson, not automatic Google eligibility certificates. Tracking-only supports further investigation; campaign-ready supports preparing a controlled first Search validation; value-bidding-ready additionally requires a trusted value definition and quality sample. None guarantees a return.

Three handoff levels

  • tracking-only

    What may continue
    This only shows that the tag, GA4, and Shopify order path works end to end, so the team can keep collecting evidence.
    What remains blocked
    Do not create the live campaign and do not let the signal train bidding.
  • campaign-ready

    What may continue
    Purchase or qualified Lead is primary, and the test order, transaction_id, value, and currency are explainable. The first Search campaign can be built.
    What remains blocked
    Do not move straight into Maximize conversion value / tROAS or large-budget scaling.
  • value-bidding-ready

    What may continue
    The test-order path and samples drawn by anomaly and order quality are explainable, and refunds, discounts, tax, shipping, currency, and dedupe are trusted. Only then should value-based bidding be discussed.
    What remains blocked
    If enhanced conversions only pass diagnostics while value definitions are unstable, tROAS is still blocked.

Name the hold and its evidence

Stop hereGo
Page view / session is primary
Primary keeps only real purchases or qualified leads
Evidence
Conversion action status record
One order is learned by two primary conversions
One bids, the other observes only
Evidence
Test order ID and dedupe notes
No value / currency / transaction ID evidence
Value, currency, and order ID reconcile across systems
Evidence
Ads / GA4 / Shopify sample match
Test orders pollute reports long term
Test orders are marked, excluded, or explained
Evidence
First-week daily reconciliation notes

Use a 30-minute review: 5 minutes on the account, 10 on sources and roles, 10 on the controlled-order evidence pack, and 5 on first-week ownership and hold conditions. Adjust the schedule to the work. Ask three counter-questions: does delay explain the difference, is a test order being mistaken for ad performance, and does a refund explain the revenue gap? An unanswered question becomes a named gap with an owner.

Next route from the main checks

HoldClose the QA gaps before using the signal for spend
The main rows are not all recorded, or the current signal action is incorrect. Retest through the selected audit route.
What you finished

No checkpoint finished in this lesson yet. Start with “Go to the exercise”.

Copy a conclusion the next owner can use

Common questions

What do I actually need to install for Google Ads conversion tracking

Do not start by asking for one tag name. Inventory the Google & YouTube app, GTM / Google tag, Customer events / Pixels, checkout / order status page, GA4 import, and old scripts, then decide which source is allowed to send the primary Purchase signal.

What is the difference between primary and secondary conversions in Google Ads

A primary action normally appears in Conversions and is used for bidding when its standard goal is used by the campaign. Secondary actions normally observe in All conversions. Actions inside a custom goal are used for reporting and bidding regardless of that label. Validate Purchase or qualified Lead and the actual campaign goal rather than the label alone.

Can AddToCart and BeginCheckout be primary conversions

Usually not for the long term. They can help read funnel quality, product page issues, or checkout friction, but if they train bidding for too long the system can learn cheap interaction instead of real buyers.

What does the conversion signal practice help me decide

It uses one 20oz tumbler test order to help you identify dirty signals: duplicate Purchase, thank-you page refresh firing twice, AddToCart as primary, wrong currency, missing transaction_id, or test orders polluting reports. The practice is about fixing the signal before judging ad performance.

Does Enhanced Conversions mean I no longer need order QA

No. Enhanced Conversions improve match quality; they do not prove that Purchase, value, currency, transaction_id, refunds, and dedupe are correct. Passing diagnostics cannot replace order-level QA in Shopify Orders / Timeline / Refunds.

Is it normal for Google Ads, GA4, and Shopify conversion numbers to differ

Yes, but the differences must be explainable. Google Ads handles bidding and attribution, GA4 explains site behavior and source paths, and Shopify is the order and revenue source of truth. The acceptance sheet should explain whether the gap comes from attribution window, delay, refund, discount, test order, or duplicate firing.

What consent or privacy boundary should I check in this lesson

Record consent status, data source, field availability, Customer events / Pixels, checkout scripts, and Enhanced Conversions diagnostics. Do not send first-party data that lacks consent or should not be sent, and do not treat modeled conversions as order-level revenue truth.

How should I use tracking-only, campaign-ready, and value-bidding-ready

Tracking-only keeps the work in QA. Campaign-ready supports controlled first-Search preparation after the actual fields and order proof are trusted. Value-bidding-ready additionally needs a trusted value definition and order quality. The inherited 10–20 orders are a troubleshooting sample, not a universal Google launch threshold. Explain refunds, discounts, tax, shipping, currency, and dedupe; a complete record does not automatically authorize scale.

What to take to the next check

Give one unexplained discrepancy to a named owner, with the current route, order fields, and retest condition. Once the signal is trustworthy, continue to the first Search ad and keyword draft. Keep the launch on hold when its evidence is missing. In the next draft, test the keyword cluster, ad group, Final URL, and RSA promise against one validation question; take Feed gaps back to Merchant Center and value-quality gaps back to Enhanced Conversions and value QA.

Revisit Search, Shopping, and PMax roles if the campaign question has changed. Use the Google Ads course index to locate the next reconciliation topic.

Edition notes

  • Author Ranfeng Wei
  • Published
  • Updated
  • Reviewed
  • Next review

This update: Reorders account, conversion-role and order-evidence checks; clarifies current Shopify Google-tag migration, permissions and dedupe scope.