
Paid search teams make bidding decisions based on conversion data, and that data is only as good as the tracking code developers ship. If you support a marketing team that handles Google Ads management, these are the implementation details that most often break, and how to check them.
Fire on the confirmed event, not the button click
A conversion tag attached to a submit button records attempts, including failed validations and duplicate clicks. Fire the event after the server confirms the lead or order. For single-page apps, that usually means pushing the event in the success callback of the API request, not on route change.
Pass transaction IDs
Include a unique order or lead ID with each conversion. Google Ads uses it to deduplicate, so a customer who refreshes the thank-you page is not counted twice. Without it, conversion numbers inflate and automated bidding overpays.
Send real values
For ecommerce, pass the order value after discounts and in the correct currency. For lead generation, agree on a value per lead type with the marketing team. Value-based bidding cannot work if every conversion is worth 1.
Respect consent mode
In regions with consent requirements, configure consent mode so tags adjust their behavior when users decline cookies. Hard-blocking all tags until consent loses modeled conversions. Firing them regardless creates legal risk.
Keep the gclid through redirects
Redirects, payment gateways and cross-domain checkouts often drop the click identifier from the URL. Test the full path from an ad click to the confirmation page and make sure the identifier survives, or store it in a first-party cookie at landing.
Test before every release
- Use Tag Assistant to confirm the event fires once per conversion.
- Compare Google Ads conversions with backend records for the same week.
- Add a regression test for the data layer push on the confirmation step.
A small discrepancy between ad platform numbers and your database is normal. A gap above ten to fifteen percent usually means something in this list is broken.
Top comments (0)