Google Ads Conversion Tracking Checklist: Verify Measurement Before You Spend

Define the conversion hierarchy and business value

List the actions available on the journey and classify them as primary business outcomes, supporting signals or diagnostics. Set the primary status only for actions that should influence campaign optimisation.

If leads differ materially in value, plan how qualified, won or revenue outcomes will return from the CRM. A form submission alone may be too early to distinguish useful demand from spam.

Example hierarchy

Choose the data source and implementation path

Google Ads can use Google Analytics, the Google tag or both for different actions. The Google tag supports Ads-specific measurement, while Analytics may be efficient when a business already has a reliable event model.

Document which platform owns each conversion and avoid importing the same action twice under different names. Use Google Tag Manager only if the team can govern containers, triggers, versions and consent correctly.

Implementation record

Fire on confirmed success, not intent

A click on “Submit” is not a completed lead if validation fails or the integration rejects the record. Trigger the conversion after confirmed form success or on a dedicated thank-you state that cannot be reached accidentally.

For purchases, pass a unique transaction ID to prevent duplicate counting. For single-page forms, ensure retries, back-button actions and repeated event listeners do not fire multiple times.

Common false positives

• Button click before form validation
• Thank-you page accessible without submission
• Event fires on page refresh
• Tag installed both directly and through a manager
• Every calendar view counted as a booking
• Test and staff traffic included in reporting

Configure values, counting and primary status intentionally

Use “one” counting for lead-generation actions when repeated conversions from one ad click should not all carry equal value; use transaction-level logic for purchases where appropriate.

Assign values from real economics where possible. If an early lead is assigned a proxy value, document how it was calculated and update it when qualification data improves.

Configuration questions

• Should repeated actions from one ad click count once or every time?
• Does the value represent revenue, margin or a proxy?
• Which actions are included in the account default goals?
• Could the same outcome be imported twice?
• Does automated bidding use the intended primary set?

Implement consent and enhanced measurement appropriately

Measurement must respect the consent and privacy requirements that apply to the business, audience and market. Coordinate the consent banner, tag behaviour, privacy notice and retention settings rather than adding tags in isolation.

Enhanced conversions can use first-party customer data in a privacy-safe hashed form to improve measurement, but it still requires correct implementation, user disclosure and applicable consent.

Governance checklist

Google Ads conversion measurement ↗

Test the journey in browser and platform diagnostics

Use a clean browser session and a uniquely identifiable test. Confirm the ad or landing URL, consent state, form success, network event, tag assistant result, CRM record and Google Ads diagnostics.

Allow for processing delay before deciding the implementation failed. Keep timestamps, IDs and screenshots so developers and marketers can compare the same event.

End-to-end test

Preserve campaign context into the CRM

Store landing page, UTM values and click identifiers when available and permitted. Ensure hidden fields survive validation and integration so the business can connect spend to qualified outcomes.

Pair this checklist with the website form–CRM integration guide when lead delivery and routing are part of the measurement path.

Minimum lead context

• Timestamp and form name
• Landing page and referrer
• Campaign, source, medium and content values
• Google click identifier when applicable
• Consent record
• CRM lifecycle stage
• Revenue or qualification outcome

Launch with monitoring and a change log

Compare platform conversions with CRM or commerce records daily during launch. Small differences can be expected because attribution windows and processing differ, but unexplained discontinuities require investigation.

Record changes to forms, tags, consent tools, landing pages and CRM mappings. If campaign strategy also needs review, see the paid advertising strategy guide or explore paid advertising support.

First-week monitor