How to Set Up Google Ads Conversion Tracking Correctly
Set up Google Ads conversion tracking by defining the business action first, creating the matching conversion action, installing one dependable measurement path, and testing a real journey before using the data for bidding. The tag is only one part of the job. A correctly installed tag attached to the wrong event still produces bad optimization data.
The safest setup is deliberately boring: one owner, one written event specification, one trigger that fires after the action succeeds, and one test record that can be followed from the website to Google Ads and the source CRM. Use Google’s current interface labels as they appear in the account, because conversion menus and setup screens change over time.
1. Define the conversion before opening Google Ads
Write a short event specification before opening the setup wizard. Name the business outcome, where it happens, who confirms it, and which fields must be sent. A purchase may need an order ID, value, and currency; a lead may need a validated form event, call outcome, or later CRM stage. A download may be useful for reporting without being the right bidding signal.
Decide primary or secondary status, counting, value source, and whether an existing Analytics, tag-manager, or offline import already measures the action. Adding a second route without a deduplication plan is how accounts overcount. For a sales-led business, define how the first online lead connects to the qualified or closed outcome instead of treating every form fill as equal.
2. Create the matching conversion action
In Google Ads, open Goals or Conversions, create a website conversion action, and choose the category that matches the event. If the account detects an existing Google tag or Analytics property, understand that source before adding another one. Google’s web conversions setup guide describes the current data-source flow.
Use the event specification to set the name, goal, primary or secondary role, counting, value source, attribution, and conversion window. A purchase should receive transaction value and currency; a lead should not be labeled as a sale.
Use a URL-based action only when a unique confirmation page represents the event and no custom parameters are needed. Use manual code or tag-manager setup for button events, dynamic values, transaction IDs, enhanced conversions, or journeys without a unique confirmation URL.
3. Install the sitewide tag and event trigger
The sitewide tag establishes the foundation; the event identifies the action. Install the Google tag where required, then add the event snippet or tag-manager event using the conversion ID and label. Google’s website tracking guide explains how ad-interaction information reaches the conversion event.
With Tag Manager, publish one tested container version and configure the conversion linker and trigger for the same site. With direct code, do not also install a tag-manager copy: two working implementations can report one action twice.
Trigger on completion, not intent. A thank-you page must be unique and not reload the event repeatedly; an asynchronous form may need a data-layer event or server confirmation. Use a stable transaction ID for purchases and define whether a lead event means validated form, connected call, or CRM status.
Coordinate the tag with the approved consent setup. Tracking configuration does not itself establish legal permission to collect or use customer data.
4. Configure values, transaction IDs, and later-stage outcomes
Use a fixed value only when the business can defend it; pass actual transaction value and currency when orders differ. Do not confuse a suggested value with money collected.
For purchases, generate a stable transaction ID from the order or CRM system and send it wherever the event is reconciled. It helps identify refreshes, retries, duplicate webhooks, and later imports instead of counting each as a new sale.
For a lead, decide whether the form remains a reporting signal while a later qualified or closed stage is imported. Sending every funnel stage as an equal primary conversion makes the bidding objective unclear. See Google’s manual conversion setup guide for the fields available to the event implementation.
5. Test the complete journey with Tag Assistant
Do not decide that tracking works because the tag appears in source code. Start on the landing page, complete the journey, and watch for the event when the action succeeds. Google’s Tag Assistant guide explains how to launch this test from conversion status.
Check the event name, ID and label, trigger, transaction ID, value, currency, and consent signal. Repeat a realistic refresh or retry and submit an invalid form to ensure neither creates a conversion. For calls, distinguish a number click from the defined connection or duration threshold.
Review the action status after the test and allow for processing time. Compare the result with Analytics and the CRM only after accounting for reporting delay and different attribution dates; Google Ads can assign a conversion to the ad click date rather than the date another system records it.
For a second account-health review, see the adz.so product overview, and confirm the live workflow and permissions before promising a specific capability.