Short answer
Google Ads conversion tracking setup means defining the right conversion actions, implementing them through Google Tag Manager on real success signals (not page loads), setting the correct count, enabling Enhanced Conversions, tracking calls separately, and importing offline outcomes — then verifying every number against your CRM before trusting the bidding algorithm with it.
Conversion tracking is not a checkbox. It is the training data for every bidding decision Google makes on your behalf, which makes a sloppy google ads conversion tracking implementation more expensive than no implementation at all.
Most accounts I audit have conversion tracking that technically fires but structurally lies — duplicated form fills, page-view-based "conversions" that count refreshes, or call tracking that was never switched on. Here is the full build, in the order I actually do it, including the parts most guides skip: GTM structure, conversion ID and label handling, and the 30-day verification pass that catches drift before it costs you money.
What Google Ads conversion tracking actually measures
A Google Ads conversion action is a signal you tell the platform to treat as valuable, tied to a conversion ID and conversion label pair generated when you create the action in the Goals section of the account. Every tag you install downstream — Google tag or GTM — simply fires that ID/label combination when a condition is met.
The mistake most businesses make is confusing tracking with reporting. GA4 can report a form submission happened; Google Ads conversion tracking has to report it in a form Smart Bidding can use to adjust bids in real time. That means timing, deduplication and value all matter far more here than in a general analytics report.
If you're building measurement across both platforms rather than Google Ads alone, read the companion piece on GA4 and Google Tag Manager conversion tracking — the data layer approach is shared between them.
Plan the conversion actions before you tag anything
List the real outcomes a salesperson would recognise: form submission, qualified phone call, booking confirmed, quote requested, demo booked. Assign each a value based on average deal size multiplied by close rate, even if it's an estimate — an unweighted value of "1" for every action tells Smart Bidding that a newsletter signup and a signed contract are equally desirable.
Decide which are primary and which are secondary conversion actions inside the conversion action settings. Only outcomes that represent genuine sales pipeline should be marked primary, because primary actions are what Target CPA, Target ROAS and Maximise Conversions optimise toward by default.
Primary vs secondary conversion actions
Primary actions feed the bidding algorithm and appear in the default "Conversions" column. Secondary actions still record but don't influence bids unless you deliberately include them in a custom column. Newsletter signups, brochure downloads and video views belong in secondary; qualified leads and purchases belong in primary.
Getting this wrong is the single most common cause of an account that spends well but reports poorly — Smart Bidding chasing a metric no one in the business actually cares about.
Implement through Google Tag Manager
Install the Google tag once at the container level, then add a conversion linker tag (auto-fires on all pages) and one conversion tracking tag per action. Trigger every conversion tag on a real success signal — a custom event pushed to the data layer on form success, not a thank-you page view that can be refreshed, bookmarked or reached directly by URL.
Set the count to "One" for lead-generation actions. "Every" belongs to ecommerce purchases where each transaction is a distinct sale. Leaving count on "Every" for a lead form is the single most common source of inflated conversion numbers I find in audits — a user who double-clicks submit or refreshes a confirmation page gets counted twice, and cost per conversion looks artificially better than it is.
Data layer event for form success
Ask your developer to push a data layer event only after the form's server response confirms success, e.g. `dataLayer.push({event: 'generate_lead', form_id: 'contact'})`. A custom event trigger in GTM listens for `generate_lead` and fires the conversion tag from there — immune to refreshes, direct visits and back-button returns.
Where a developer isn't available, GTM's built-in Form Submission trigger combined with a check on a visible success element is the next best option, though it is more fragile against JavaScript-based forms and multi-step wizards.
Conversion ID, label and value mapping
Paste the conversion ID and label exactly as generated in Google Ads — a mismatched label silently fails to record without any error in GTM preview. Pass value dynamically from the data layer where deal size varies (e.g. quote value), and pass a fixed estimated value where it doesn't.
Turn on enhanced conversions
Enhanced conversions send hashed first-party data — typically email and phone — alongside the standard conversion hit so Google can match conversions it would otherwise lose to Safari's ITP, ad blockers or third-party cookie restrictions. In most accounts I've implemented it in, it recovers somewhere between 5% and 15% of conversions that were previously invisible to the platform.
There are two implementation modes: Enhanced Conversions for Web, which hashes data client-side via GTM's built-in variable, and Enhanced Conversions via Google Tag Manager server container or the Conversions API for a fully server-side path. For most lead-gen sites, capture email or phone at the point of submission, feed it into GTM's Enhanced Conversions configuration on the conversion tag, and accept the data processing terms inside the conversion action settings.
This is one of the few genuinely free performance gains left in the platform. If you're running Meta alongside Google Ads, the equivalent server-side concept is covered in Meta Conversions API setup — the matching logic (hashed identifiers, deduplication) is conceptually identical across both platforms.
Track calls properly
There are three distinct call sources that get conflated in most accounts: calls made directly from the ad's call extension, calls from a number displayed on the website, and calls initiated via a click-to-call button on mobile. Each needs its own tracking method.
Use Google forwarding numbers (via call reporting) for the first two — this swaps the displayed number dynamically per session so Google can attribute the call to the specific click. Set a minimum call duration, typically 60 seconds, so misdials, wrong numbers and immediate hang-ups don't inflate the conversion count.
- Ad call extension conversions: enabled automatically once call reporting is on and a minimum duration set.
- Website call tracking: forwarding number swapped via a tag manager script, feeding a conversion when a call connects and clears the duration threshold.
- Click-to-call button: a GTM click trigger on the `tel:` link firing a separate, lower-value conversion action, since clicking isn't the same as answering.
Import offline conversions
Capture the GCLID (Google Click ID) on every form submission and store it against the lead record in your CRM. When that lead becomes qualified, books a meeting, or closes as a customer, upload the outcome back to Google Ads via the offline conversion import — either a scheduled CSV, Zapier/Make connector, or a direct API integration from the CRM.
Bidding then learns from revenue and qualified-lead status rather than raw form fills, which is the difference between an account optimised for volume and one optimised for outcomes that actually matter to the business. This pairs directly with the reconciliation work covered in attribution and analytics measurement.
Offline conversion import has a lag — Google Ads typically needs the upload within 90 days of the click, and closer to it is always better for bid learning. Build the CRM export as a weekly job at minimum, not a quarterly afterthought.
Verify, then verify again in 30 days
Use GTM's Preview mode to confirm the trigger fires exactly once per real conversion event, Google Tag Assistant to confirm the tag reaches Google's servers, and a genuine test submission to see the conversion land in Google Ads within a few hours (conversions can take up to 24 hours to fully populate in reporting).
Then, roughly 30 days after launch, reconcile a full month of platform-reported conversions against CRM records for the same period. A gap under 10% is normal (some loss to consent declines and cross-device journeys is expected); a gap over 20% means something structural is wrong — duplicate tags, count set to "Every", or a trigger firing on page load rather than success.
- GTM Preview: trigger fires once, on the correct event.
- Tag Assistant / Google Ads diagnostics: tag status shows "Recording conversions", not "No recent conversions" or "Unverified".
- GA4 DebugView (if linked): event arrives with expected parameters.
- CRM reconciliation at 30 days: platform vs CRM within 10%.
- Recheck after every site redesign, CMS migration or consent banner update — these break tags more often than anything else.
Common mistakes worth checking for
The recurring faults I find, roughly in order of frequency: count left on "Every" for lead forms, conversion tags firing on thank-you page load instead of a data layer success event, enhanced conversions never switched on, phone calls not tracked at all, and offline conversion imports set up once and then abandoned when the CRM changed.
Each of these is individually simple to fix and collectively responsible for most of the "our cost per lead looks fine but sales say leads are rubbish" conversations I have with clients. If you'd rather have this built and documented once by someone who does it daily, conversion tracking setup is the service built specifically for this, and a Google Ads account audit will surface tracking issues alongside everything else worth checking.
Get it built properly, once
A correct google ads conversion tracking setup is roughly a day of focused work for someone who's done it dozens of times, and the return shows up in every bidding decision the algorithm makes afterwards. If you want a second pair of eyes on an existing setup, or a full build from scratch, book a 30-minute call or request a paid media account audit and I'll tell you exactly what's broken before you spend another pound or dollar on media.
Frequently asked questions
- What's the difference between the Google tag and Google Tag Manager for conversion tracking?
- The Google tag is a base site-wide tag; Google Tag Manager is a container that manages that tag plus every other conversion, remarketing and analytics tag through triggers and variables. GTM is strongly preferable for anything beyond a single conversion action because it centralises control, versioning and debugging in one place.
- Should conversion count be set to 'one' or 'every'?
- Use "One" for lead-generation actions like form fills and calls, since a single lead shouldn't count twice from a refresh or resubmission. Use "Every" only for ecommerce purchase actions, where each transaction genuinely represents a separate sale.
- How much do Enhanced Conversions actually improve tracking?
- In the accounts I've implemented it in, Enhanced Conversions typically recovers 5% to 15% of conversions that browser restrictions or ad blockers would otherwise hide. The exact gain depends on your traffic mix — more Safari and iOS traffic generally means a bigger recovery.
- Why does Google Ads show more conversions than my CRM?
- Usually one of: count set to "Every" on a lead form, a conversion tag firing on thank-you page load rather than a genuine success event (counting refreshes and direct visits), or duplicate tags firing the same action twice. Reconcile monthly and investigate any gap over 10%.
- Do I need call tracking if I already track form submissions?
- For most service businesses, yes — calls are frequently the majority of qualified leads, not a minority. An account that only counts form fills is optimising against a fraction of its actual outcomes, and Smart Bidding will under-value campaigns that generate calls rather than forms.
- How long should I wait before trusting new conversion data for bidding?
- Give it at least 30 days and roughly 30 conversions per conversion action before making major bidding decisions off the data. Smart Bidding strategies also need a learning period after any change to conversion actions, so avoid switching values or actions during that window.