Start by mapping the conversion journey
Write down every step between the visitor clicking an ad and the business receiving a usable enquiry. This may include a landing page, form validation, backend submission, CRM creation, thank-you page, GA4 event and ad-platform conversion.
When teams only test the visible page, they can miss failures between systems. A confirmation message is not proof that the lead reached the sales team.
Submit at least one real test lead and follow it all the way to the destination where sales will see it.
1. Name events around real actions
Use clear event names that describe what happened. GA4 supports automatically collected, recommended and custom events; choose the closest recommended event where it fits and use custom events when your business action needs a different definition.
Keep a tracking dictionary that lists the event name, trigger, parameters, destination platforms and whether the action should be used for optimisation.
2. Validate GTM triggers before publishing
Preview the container and reproduce the exact action a visitor will take. Check that the intended tag fires once, at the correct moment, and that unrelated page interactions do not trigger it.
For form tracking, understand whether the site uses a normal page load, AJAX submission, embedded third-party form or server-side process. The correct trigger depends on how the form actually behaves.
3. Check for duplicate conversions
Duplicate conversions can happen when the same action is tracked through multiple tags, when a thank-you page reload fires again or when both browser and platform integrations record the same event without deduplication.
Test refresh, back-button behaviour and repeat submissions. Decide which event should be primary for optimisation and which signals should remain secondary or diagnostic.
4. Confirm lead delivery separately from tracking
A perfect analytics event does not guarantee a successful lead. Check the destination inbox, CRM, webhook or database. Confirm the submitted values are complete and readable.
If the business has spam filters or routing rules, test those too. Tracking should never become a substitute for validating the actual operational workflow.
5. Collect only what you need
Form and tracking implementations can involve personal data. Limit collection to what is necessary for the stated purpose, use appropriate consent and privacy controls and follow the requirements that apply to the business and location.
Do not pass sensitive user information into analytics parameters simply because it is technically possible.
6. Create a launch verification sheet
- Landing page loads correctly on desktop and mobile.
- Form validation works.
- Lead reaches the intended CRM or inbox.
- Thank-you state appears only after success.
- GA4 event appears once with the expected parameters.
- Google Ads or other conversion tag fires as intended.
- Refresh does not create an unwanted duplicate.
- Campaign URLs preserve the tracking parameters you need.
Re-run the same checks after major form, CMS, consent-banner or tag-container changes.
Questions business owners ask
Is a thank-you page enough for conversion tracking?
It can be useful, but only when it appears after a successful submission and cannot easily be triggered without the real action. Test the full implementation.
Should every GA4 event be a Google Ads conversion?
No. Many events are useful for analysis but should not guide bidding. Optimisation goals should represent meaningful business actions.
Why do GA4 and Google Ads show different numbers?
Different attribution, processing and configuration choices can produce differences. First confirm that both platforms are receiving the intended event correctly.
How often should tracking be tested?
Before launch and after any meaningful change to forms, tags, consent, CMS templates or conversion settings.