Before you start
- Admin access to the Google Ads account, and edit access to the site's tag container (GTMTag management system.) or to the page templates if the tag will be placed directly.
- A list of the actions the business cares about, in priority order, with where each happens on the site (a thank-you page, a form submission event, a purchase confirmation) and what each is worth. The measurement hub explains the difference between a primary action and the diagnostic ones.
- A staging or preview way to test without polluting live data: Tag Manager preview mode, or a test order path that can be excluded afterwards.
- Consent requirements for the markets you advertise in, agreed with whoever owns the consent bannerSoftware that collects, stores and passes on visitors' consent choices for cookies and tracking..
- Auto-tagging switched on in account settings, so the click identifier reaches the site. Manual UTMURL tags identifying traffic source. parameters are for analytics, not for Google Ads conversion matching.
Define the conversion actions
Write down each action before touching the interface: its name, category (purchase, lead, sign-up, contact and so on), where it happens on the site, whether it has a value and whether that value is fixed or varies per transaction. Decide which one or two represent a real business outcome; everything else will be secondary. Resist tracking every click. An account with a purchase, a lead form and a phone call is easier to bid on than one with a dozen page views dressed up as goals. Agree the names with whoever reads the reports, because renaming later causes confusion in change history.
Choose the tag method
There are three documented routes for website conversions. The Google tag with an event snippet placed in the page is the most direct and the least flexible. Tag Manager wraps the same event in a tag with triggers and variables and is the default for most sites. Importing GA4Google's event-based analytics platform. key events through the Google Ads link reuses the analytics tagging but adopts GA4's attribution and session rules. Pick one route per action, not several; mixing them is how double counting starts. This tutorial follows the Tag Manager route and notes where the others differ.
Create the action in Google Ads and collect its identifiers
In the conversions section, create a new website conversion action. Google asks for the goal category, name, value, count and window settings in the same flow; set them provisionally now and revisit them in the later steps. Once saved, the action exposes a conversion ID and a conversion label. The ID is shared across the account; the label is specific to this action. Record both, because Tag Manager asks for them and a mistyped label is the most common reason an action never records anything.
Install the base tag
The Google tag must load on every page of the site before any event can be sent, and it is also what reads the click identifier from the landing URL and stores it. That identifier is the one Auto-TaggingA Google Ads setting that adds a click identifier (GCLID) to every ad click's landing URL. appends to every ad click. In Tag Manager, confirm a Google tag or conversion linker tag is already present and fires on all pages; if not, add the conversion linker, which Google documents as the tag that handles the click identifier for Google Ads conversion tracking. Publish the container and check in the browser that the tag loads on the homepage, a landing page and the conversion page itself.
Build the event trigger
Create a Google Ads conversion tracking tag in Tag Manager with the conversion ID and label from the earlier step. Then define when it fires. For a thank-you page, a page-view trigger on that URL is enough, provided the page cannot be reached without completing the action. For a form that submits without a page change, use a form-submission or custom-event trigger that fires only on success, not on the click of the submit button. For a purchase, fire on the confirmation page or on the purchase event pushed to the data layer. A trigger that fires too broadly is far worse than one that occasionally misses.
Set counting, value and window
Return to the action settings. Counting is "one" for leads and sign-ups, because a person who submits twice is still one lead, and "every" for purchases, because each order matters. Value is a fixed amount for leads where you know roughly what one is worth, or a transaction-specific value for purchases, passed from the data layer into the tag's value and currency fields. Set the click-through conversion window to match the sales cycle: a short cycle can use a short window; a long cycle needs the longest available. The AttributionAssigning conversion credit to touchpoints. model is also set here; data-driven is the default where the account has enough data, last click otherwise. Each of these choices changes the denominator of cost per conversion, which the glossary's CPA in Google Ads entry traces column by column.
Handle consent
If the site shows a consent banner in any market, the conversion tag has to respect it. Google documents consent mode as the mechanism: the tag adjusts its behaviour according to the consent state the banner communicates, and with the advanced implementation Google can model conversions it could not observe. Check that the consent management platform updates the consent state before the Google tag fires, and that denied states actually prevent cookies from being set. A tag that fires regardless of consent will record more conversions and expose the business to complaints; a tag blocked for everyone will record almost nothing. Neither is a measurement problem that bidding can fix.
Test with Tag Assistant and preview mode
Open Tag Manager preview mode and walk through the conversion path as a visitor who arrived from an ad, using a test URL with a click identifier parameter if a real ad click is not practical. Confirm the conversion linker fires on the landing page, the conversion tag fires exactly once on the conversion step, and the value and currency fields carry the right data. Tag Assistant shows the same sequence from Google's side. Test the failure cases too: reload the thank-you page and confirm the count does not double where counting is set to "one"; submit an invalid form and confirm nothing fires.
Verify in the conversions report
After publishing, the action's status in Google Ads moves from "Unverified" to "Recording conversions" once real conversions arrive. Check the diagnostics view on the action for tag health and any warnings. Compare the first week of conversions against the back office: orders, leads in the CRM, calls logged. The numbers will not match exactly, for reasons the comparison of Google Ads and GA4 figures covers, but they should be the same order of magnitude and move together. A conversion rate (CVRShare of visits or clicks that convert.) wildly out of line with the site's analytics is a trigger problem, not a bidding one. The conversion rate calculator gives a quick sanity check.
Set primary and secondary actions
Mark the one or two actions that represent business outcomes as primary and everything else as secondary. Check which conversion goals each campaign uses: the account default is usually right, but a campaign created for a different purpose can be given a custom goal. If a GA4 import duplicates a native action, make the import secondary so it stays visible for comparison without counting twice. Record the decision in change history notes so the next person understands why the Conversions column looks the way it does. In an inherited account with many existing actions, the conversion action clean-up tutorial applies the same decisions to the whole set and stages them so bidding relearns only once.
Hand over to bidding
Nothing in the previous steps changes how campaigns bid until the strategy is pointed at the new action. Give the account a period of clean recording before switching a campaign to a target-based Smart Bidding strategy, and when switching, expect a learning period in which performance is noisy. The Smart Bidding strategies guide explains which strategy fits which goal and what data each needs. Then plan the next layer: enhanced conversions recover matches that browser restrictions and consent lose, and offline import closes the loop for lead-generation businesses.
Verify the result
A finished setup has: a written list of actions with their category, counting, value and window; one tag route per action; a conversion linker or Google tag on every page; a trigger that fires once per real conversion and never otherwise; consent handled before the tag fires; a passed preview test including the failure cases; a "Recording conversions" status with a back-office comparison; one or two primary actions; and a dated note in change history. Someone auditing the account a year later should be able to reconstruct every decision from the names and the notes.
A furniture retailer's first clean week
A furniture retailer had tracked "Add to basket" as its only conversion for two years, and its target ROAS campaigns had learned to buy basket additions. The new setup creates a purchase action with dynamic transaction values, sets counting to "every" and a 60-day click window, and demotes the basket action to secondary. Preview testing catches that the confirmation page could be reloaded and fired the tag twice, which a data-layer transaction ID fixes. In the first full week the account records 212 purchases against 219 orders in the shop's admin, a gap explained by consent refusals and returns. Reported conversion value falls from the inflated basket figure to real revenue, and the ROAS target is reset against it before the campaigns are switched back to automated bidding.
Troubleshooting
| Problem | Usual cause | Fix |
|---|---|---|
| Status stays "Unverified" for days | Tag never fires on the live site, or fires without the linker | Re-check the trigger in preview; confirm the conversion linker is published |
| Status says "Tag inactive" after working before | Site redesign removed the container or the thank-you URL changed | Compare the current path with the trigger; re-publish |
| Counts are far above the back office | Counting set to "every" on a lead, or a trigger on the submit click instead of success | Change counting; move the trigger to a success event |
| Counts are far below the back office | Consent blocking for most visitors, or the conversion happens off-site (payment provider, CRM) | Review consent mode; add offline import or a return-URL confirmation page |
| Values are missing or wrong | Value variable not mapped, or currency not passed | Inspect the data layer in preview; map value and currency explicitly |
| Conversions appear in GA4 but not Google Ads | Auto-tagging off, or the click identifier stripped by a redirect | Enable auto-tagging; fix redirects to keep query parameters |
| The same conversion appears twice | Native tag and GA4 import both primary | Make one secondary or remove it |
If conversions suddenly stop recording, the tracking outage response SOP shows how to protect automated bidding, find the cause and document the affected period for later reporting.
If a working setup later stops recording, the conversions not tracking diagnosis walks the chain from tag to conversion action in the order that finds the break fastest.
Common mistakes
- Tracking the button, not the outcome. A click on "Submit" is not a submitted form.
- Leaving every action primary. Bidding then optimises towards whichever action is cheapest to buy.
- Counting "every" on leads. Double submissions become double conversions.
- Forgetting the linker. The event fires but cannot be joined to a click, so nothing records.
- Testing on the live site without a plan to exclude the tests. The first week's data is then unreliable for bidding.
- Treating the GA4 import as identical to a native tag. The attribution and session rules differ, and so will the counts.
- Setting a short window for a long sales cycle. The account looks worse than it is, and bidding learns from the wrong subset.
The author's conversion tracking expertise page describes how this sequence is applied on client accounts, including the hand-off to developers.
