Conversion tracking should record the actions that represent real business value. A click, attempted form submission and confirmed enquiry are different events.
Define what counts as a conversion
For sales, use confirmed orders with an appropriate transaction identifier. For lead generation, distinguish submitted enquiries, completed bookings and qualified leads. Decide what should be used for campaign optimisation.
Prevent duplicate and false events
Do not count every button click as a lead. Avoid sending the same confirmed event again on a refresh or repeated callback. Test success, failure and validation paths.
Configure primary and secondary actions
Google Ads distinguishes actions used in optimisation from those used mainly for observation, with additional behaviour for custom goals. Check both the action setting and the campaign goal. Read Google’s primary and secondary action guidance.
Reconcile with business records
Compare tracking with order or CRM records over the same period and allow for attribution and processing differences. Document which paths are measured and which remain unverified.
Define the conversion before installing tags
List the actions the business genuinely values—purchase, qualified form submission, booked call or another outcome—and decide which should be primary optimization goals versus secondary observations.
Choose one source of truth for each event
A conversion can be imported from GA4, recorded with a Google Ads tag or passed from another system. Avoid duplicate counting by documenting the source, trigger and attribution role of every conversion action.
Test the full journey
Complete real test actions and verify that the right event fires once, carries the expected value where relevant and appears in the reporting after normal processing delay. Check consent and privacy configuration for your jurisdiction and implementation.
Reconcile platform conversions with business records
Google Ads attribution will not always match CRM, ecommerce or financial totals. Understand the attribution window and model before deciding that one system is “wrong.”
For measurement and campaign support, see Google Ads management.
Create a conversion-action inventory
List every action in the account with name, source, category, counting method, value logic, attribution setting and whether it is primary or secondary. Remove or relabel outdated actions so optimization is not influenced by legacy goals.
Test after website or form changes
Tracking can break when checkout, forms, consent tools or tag containers change. Add conversion validation to launch checklists for major website releases.
Define counting rules intentionally
Purchases usually need different counting logic from lead submissions or page-level actions. Review whether each conversion action should count every occurrence or only one per ad interaction based on the business event.
Assign values consistently
For ecommerce, pass transaction value accurately. For lead generation, use estimated or imported values only when the methodology is documented and useful for optimization.
Separate diagnostic events from bidding goals
Calls, page views or micro-conversions can be useful to observe without making them primary optimization targets. Too many primary actions can teach the system to pursue the easiest event rather than the most valuable outcome.
Keep a change history
Record when goals, values or attribution settings change so performance before and after the change is interpreted correctly.