Google Ads Auto-Tagging Checklist

Use this Google Ads auto-tagging checklist in order: define the measurement purpose, verify the destination can preserve the click identifier, test consent and redirects, connect analytics or CRM data, and reconcile one conversion with the source system. Auto-tagging is ready only when the identifier survives the journey and the resulting event has a meaningful conversion definition.

Google’s auto-tagging documentation explains the feature. This checklist adds the operational evidence needed for a website, analytics, and offline-import release. Mark each item with a test record, screenshot with sensitive values masked, or system comparison; do not mark a box because the account toggle is enabled.

Pass 1: Define the measurement contract

[ ] The team has written why it needs the click identifier: analytics, conversion tracking, CRM, offline imports, or a stated combination.
[ ] The destination domain, redirect service, form or checkout domain, and analytics property are listed.
[ ] The conversion action, primary or secondary role, counting method, value, currency, and conversion window are documented.
[ ] The CRM or order record has a stable ID and a field for the click identifier when the business and privacy design allow it.
[ ] Manual UTM parameters, tracking templates, and auto-tagging have clear ownership for each report field.

Auto-tagging links an ad interaction to the journey. It does not decide whether a page view, lead, or order is the result the campaign should optimize toward. Use the conversion tracking settings article for that separate decision.

Pass 2: Prepare the destination and redirects

[ ] A controlled ad URL reaches the intended landing page with the click identifier present.
[ ] HTTP-to-HTTPS, hostname, locale, device, and campaign redirects preserve the required query parameters.
[ ] Shorteners, link builders, and canonical URL logic do not silently remove the identifier.
[ ] Mobile, app, booking, payment, and third-party form handoffs have been tested separately where they exist.
[ ] A page reload, browser back action, and normal conversion path do not assign one visitor’s identifier to another record.

Test the final response as well as the first redirect. A framework that rebuilds the URL from only the path can lose the parameter after a successful initial request. If a handoff intentionally removes it, record the exception and use an alternative measurement design rather than storing a guessed value.

Pass 3: Configure the account and analytics

[ ] The correct Google Ads account and current auto-tagging setting have been confirmed.
[ ] The editor, date, and implementation ticket are recorded.
[ ] Analytics receives the expected Google Ads source and campaign context.
[ ] Manual UTMs have a documented relationship to the click identifier.
[ ] The tracking template or final URL suffix is tested separately from the auto-tagging parameter.
[ ] The connected analytics property is the one used by the report owner.

Do not change the UTM policy at the same time as enabling auto-tagging unless the release plan explicitly tests both. Check the actual analytics event, not only the address bar. If the identifier is present but the session is unassigned, inspect the analytics tag, consent state, property, and cross-domain setup.

Pass 4: Test consent and storage

[ ] Consent granted: the permitted identifier and analytics event are present.
[ ] Consent denied: the site does not send or retain data that the privacy design prohibits.
[ ] Consent unanswered: behavior is tested separately from explicit denial.
[ ] A visitor changing consent and reloading the page behaves as designed.
[ ] Retention, access, masking, and deletion rules are recorded for stored identifiers and test records.

The click ID is not a permission bypass. Do not place it together with raw email, phone, or other personal data in a public URL, console output, screenshot, or shared ticket. Use disposable or masked test values and clean them after the test.

Pass 5: Connect forms, orders, and offline conversions

[ ] A lead or order record preserves the click identifier with its stable source-system ID and timestamp.
[ ] Cross-domain forms and checkouts retain the relationship when the conversion happens on another host.
[ ] The CRM stage used as a conversion is documented and meaningful.
[ ] Offline upload rows retain the correct action, value, currency, event time, and timezone.
[ ] The import is idempotent: retrying a row does not create a second event.
[ ] Rejected records and queue age can be reviewed without exposing raw data.

An identifier can be complete while the lead is unqualified. Validate click coverage and business quality separately. The conversion tracking setup guide covers the event-definition side of the release.

Pass 6: Reconcile and approve

Run one controlled form submission or order and record:

The click path and final URL.
The identifier’s presence after each redirect.
The analytics source and campaign result.
The CRM or order ID and any offline queue record.
The Google Ads conversion action, value, and timestamp.

Compare the systems using the same date definition and timezone. Check a refresh, payment retry, or duplicate form submission where relevant. Do not call a one-day difference a tracking failure without considering attribution and conversion lag, but investigate an unexplained identifier gap.

After launch, review direct or unassigned traffic, missing identifiers, offline rejections, and conversion reconciliation after the first full cycle. Annotate redirect, consent, analytics, and checkout releases. If a problem appears, use the auto-tagging troubleshooting guide and repair the first point of loss rather than adding another tag.

adz.so can inspect supported Google Ads settings through its audit workflow, but it does not modify your website, analytics, consent platform, or CRM. For the account-level setting, use Google’s current auto-tagging documentation.

Research note: reviewed against Google Ads Help auto-tagging and conversion tracking guidance on 2026-08-03. Verify current account navigation and privacy requirements before sign-off.