Inside this resource.
5 sectionsA map of the published document. Choose a section to start reading.
- 01Put this guide to work
- 02How Tracking Layers Work
- 03The 10 Foundation Checks
- 04Your Score and Priorities
- 05The Full Picture
| Result | Evidence to retain |
|---|---|
| Pass | Observed behavior, date, setup and test scope |
| Fail | Reproducible issue, affected events and proposed fix |
| Not checked | Missing access or evidence and next owner |
| N/A | Why this connection or feature is irrelevant |
Source: View the complete rubric · Source-defined bands. Your account has not been scored.
Trace the event before changing the campaign.
Locate the evidence in the implemented tracking path. An untested link stays Not checked; the diagram does not assert that your account passes.
- Observe
Inspect the intended event and actual tag/network behavior.
- Check identity
Review click data, consent choices and cross-domain continuity.
- Reconcile
Match purchase IDs and values; inspect duplicate reporting.
- Record
Keep the observed issue, owner and next verification check.
Read the full source: How Tracking Layers Work · The 10 Foundation Checks
Jump to a section
Put this guide to work
Review accounts, tagging prerequisites and click identifiers before investigating higher-level attribution.
Your task: Check tracking foundations. Record the source, date range and reviewer beside the result. Leave anything you have not checked marked Not checked.
Related work: 15-Point Critical Tracking Checklist · Measurement Maturity Assessment
How Tracking Layers Work
Use this five-layer review map to locate a problem. Dependencies differ by the measurement implementation.
Layer 5: Optimization signals (bidding data, audience signals) Layer 4: Attribution (cross-platform alignment, windows) Layer 3: Conversion actions (what you're tracking, values) Layer 2: Tag implementation (GTM, pixels, event firing) Layer 1: Foundation (account linking, consent, base setup)
A foundation defect can affect the flows that depend on it; it does not establish that every tag, conversion or report is corrupted. Trace the actual affected path before estimating its scope.
That's why we always audit bottom-up. And that's why this diagnostic starts here.
The 10 Foundation Checks
Check 1: Google Ads Linked to GA4
Open GA4 > Admin > Product Links > Google Ads Links.
Pass: Your Google Ads account ID appears and shows "Linked." Fail: No link, or wrong account linked.
Impact if broken: Features that depend on the GA4–Google Ads link may be unavailable or mis-scoped. Independently implemented tags and reports can still work; verify the specific audience, reporting or conversion path rather than declaring all tracking broken.
Check 2: Correct GA4 Property
While in GA4 > Admin, verify the property ID matches the one on your website.
Pass: The linked GA4 property is the correct, active property for your site. Fail: The linked GA4 property is a test, obsolete or wrong property for the intended site. A legacy Universal Analytics identifier is not a valid GA4 property.
Impact if broken: The affected link or tag may send or associate data with an unintended property. Inspect actual tag destinations and reported events; a wrong link alone does not show that every event went to the wrong destination.
Check 3: Google Merchant Center Linked
Open Google Ads > Tools & Settings > Linked Accounts > Google Merchant Center.
Pass: The intended Merchant Center account is linked for the selected retail setup. Record feed/item eligibility separately. Fail: The required link is missing or points to the wrong account. Record individual product disapprovals as separate eligibility findings.
Impact if broken: A missing required link can prevent the intended retail product advertising. Item errors can limit eligible products; inspect the actual affected inventory and diagnostics instead of assuming all products or campaigns are unavailable.
Note: Skip this check if you're not running e-commerce or Shopping campaigns.
Check 4: GTM Admin Access
Open Google Tag Manager > Admin > User Management.
Pass: The responsible human/service identity has the necessary GTM role, with a documented publisher and review path. The Google Ads account itself is not a GTM user. Fail: No accountable authorized path to inspect or implement needed changes; read-only access may be sufficient for an audit.
Impact if broken: Missing authorized access can delay inspection or implementation. An intentional review/publisher handoff is not itself a defect; keep least-privilege access and a named change owner.
Check 5: Auto-Tagging Enabled
Open Google Ads > Admin > Account Settings.
Pass: Auto-tagging is turned on. Fail: Auto-tagging is disabled.
Impact if broken: The intended automatic click-identification/reporting path can lose coverage. Verify the actual identifiers, tags, consent and conversion implementation; this is not proof that all purchase measurement disappears.
Checks 6–8: Consent Implementation and Choices
Review the selected basic or advanced implementation against Google's consent-mode documentation and the accountable privacy review for your actual markets.
- Check 6: Verify defaults and updates for
ad_storage,analytics_storage,ad_user_dataandad_personalizationwhere applicable. - Check 7: Test accept, reject and withdrawal paths against the selected design. Basic mode can block Google tags before consent; advanced mode can send limited cookieless pings under denied consent. No ping after rejection is not automatically a defect.
- Check 8: Verify ordering, storage and actual network behavior, not merely whether a tag appears to fire. Consent mode is a technical mechanism and does not by itself establish legal compliance or model eligibility.
Mark each applicable check Pass/Fail from observed evidence; unknowns stay Not checked.
Check 9: Click-Identifier Capture
Inspect landing-page redirects and permitted tag/storage behavior. Google's sitewide-tagging guidance describes capturing click information into first-party storage. GCLID need not remain visibly appended to every subsequent page URL.
Pass: Identifier capture survives initial redirects and is available to the intended conversion implementation under the applicable consent state. Fail: A verified redirect or implementation issue prevents required capture.
A synthetic gclid=test123 can check URL handling only; it is not a valid ad click or proof of attribution. Do not click a live ad merely to test this checklist.
Check 10: Cross-Domain Tracking
Check whether the actual purchase journey crosses domains and whether its supported analytics integration requires cross-domain configuration. Do not assume a generic checkout domain applies to your store.
Open GA4 > Admin > Data Streams > Select your stream > Configure Tag Settings > Configure Your Domains.
Pass: Required domains/integration settings and observed session/identifier continuity are verified in an authorized test, under the applicable consent state. Fail: A reproducible domain-transition issue disrupts the intended measurement path; a missing generic domain entry alone does not establish a reset.
Impact if broken: A verified domain-transition issue can disrupt session attribution. Inspect actual domains, implementation and observed events before estimating its scope.
Shopify-specific: Inspect the actual checkout domains and supported integration first; do not add a generic domain from this example blindly. Use an authorized test to verify continuity.
Skip this check if your entire purchase flow stays on a single domain.
Your Score and Priorities
Count checked applicable passes and failures; exclude Not checked and N/A from earned and possible points and show coverage. A checklist score does not certify tracking accuracy. Prioritize verified missing/wrong destinations, identifier capture, purchase events, cross-domain behavior and consent-state defects by their actual effect.
| Result | Evidence to retain |
|---|---|
| Pass | Observed behavior, date, setup and test scope |
| Fail | Reproducible issue, affected events and proposed fix |
| Not checked | Missing access or evidence and next owner |
| N/A | Why this connection or feature is irrelevant |
The Full Picture
For the complete team-operated workflow, review the Google Ads AI Agentic System. The product page lists the current deliverables, price, license terms and setup responsibilities.
- Layer 1: Foundation (10 items) - what you just checked
- Layer 2: Tag Implementation - inspect the selected tag/event setup
- Layer 3: Conversion Actions - inspect goals, values and counting
- Layer 4: Attribution - reconcile definitions, windows and models
- Layer 5: Optimization Signals - review the data actually used for bidding and audiences
Use the current product page to verify licensed deliverables. Choose platform-specific checks from the actual implementation; this review map does not establish a frequency ranking of failures.
Use verified foundational findings to scope the next tag and conversion-event checks; a pass here does not validate the upper layers.
Choose who handles the next step.
Use the reference yourself, book a focused paid working session, or have Tegra handle the ongoing channel work.
Search, Shopping, Performance Max and Demand Gen campaigns, plus the research, product feeds, static and video creative, and landing, offer and pre-sale pages behind them.
Explore managed Google Ads → · See paid working sessions →