Google Ads Conversion Tracking Setup

A Google Ads account without working conversion tracking is an account bidding blind. Smart Bidding can only chase what it can see, and if what it sees is a thank-you page that fires on form spam, double-clicks, and bounce traffic, your reported cost-per-acquisition is noise dressed up as a number. The job of conversion tracking setup is to make sure every rupee of ad spend is optimised toward an action that actually moves revenue — a purchase, a qualified lead, a booked call, a closed deal — and that the value of that action is recorded with the right attribution.

This is a measurement-engineering task, not a reporting task. It lives in your GTM container, your Google Ads conversion actions, your consent layer, and your CRM. Here is what we actually build.

Most accounts we inherit have either one conversion action (a generic “Lead” on the thank-you page) or a dozen overlapping ones, half of which haven’t fired in months. We rebuild the set deliberately:

• Purchase / transaction with a dynamic revenue value and currency pulled from your cart or backend — Shopify, WooCommerce, Magento, or a custom checkout.
• Form lead counting once per session, so refreshes and accidental resubmits don’t inflate the number.
• Phone call from a Google forwarding number, with a minimum call-duration threshold so eight-second misdials don’t register as conversions.
• Qualified lead and closed-won, imported from your CRM rather than fired from the site, because those are the actions that pay your bills.

Each action gets a name, a value, a count rule (“one” or “every”), and a decision about whether it belongs in Smart Bidding’s “Conversions” set. That last checkbox matters more than people realise.

Apple’s Intelligent Tracking Prevention, browser privacy changes, and the iOS consent screen quietly drop a meaningful slice of your attributable conversions — the visitor clicked your ad and bought, but the cookie that would have credited the click was blocked. Enhanced conversions is Google’s fix: instead of leaning on the cookie alone, you pass a SHA-256-hashed email or phone number at the point of conversion, and Google matches it on its side to recover that attribution.

This only works cleanly when consent mode v2 is in place — specifically the ad_user_data and ad_personalization signals set according to the visitor’s choice. We configure consent mode so that even visitors who decline analytics still send a cookieless, modelled signal, which keeps your campaign data populated without overriding their decision. If your tracking currently runs on a bare gtag.js tag with no consent layer, this is usually where the biggest measurement lift comes from.

For service businesses — clinics, real estate, education, B2B services — the phone call is often the real conversion, and it’s also the one Google Ads counts worst by default. We set up call tracking using whatever fits the account:

• Google forwarding numbers on call-only campaigns and call extensions, with duration-based conversion thresholds.
• Website call clicks for mobile tap-to-call buttons tracked through GTM.
• Third-party call tracking wired into Google Ads as an import source when you already use a provider.

When a human qualifies or closes that call later, we capture the gclid from the original click and send the qualified outcome back as an offline conversion — so the keyword that earned a booked appointment gets credit for the appointment, not just the ring.

Lead-gen accounts carry a measurement gap that retail accounts don’t: the form fill lands on the site today, but the sale closes in your CRM three weeks from now. Without offline conversion import, Smart Bidding optimises toward form fills — junk ones included — because it never sees which leads turned into revenue.

We capture the gclid into a hidden field on your form, store it against the lead record in HubSpot, Salesforce, Zoho, or your in-house CRM, and upload qualified-lead and closed-won stages back to Google Ads as offline conversions via the Google Ads API or the bulk-upload CSV schema. Each stage becomes its own conversion action with its own value and conversion delay, so bidding can target the milestones that matter to finance.

You can count a conversion two ways: import it from GA4, where your event logic already lives, or tag it directly in Google Ads with the Google tag and enhanced conversions. The trade-off is latency, deduplication, and Smart Bidding signal quality. We make the choice per action — usually native tags with enhanced conversions for the primary event that drives bidding, GA4 imports for secondary reporting events — and we deduplicate carefully so the same thank-you page isn’t counted twice. Getting this wrong silently halves your reported CPA without changing a single rupee of spend.

Before the account goes back to automated bidding, we prove the setup in the tools Google actually provides: GTM Preview to confirm each tag fires on the right event, GA4 DebugView to watch parameters and consent states land in real time, and the Google Ads diagnostics tab to confirm each action shows “Recording recent conversions.” We run real test purchases, real form submissions, and real test calls, then hand over a one-page measurement doc that records what each action means, its value, and how to recheck it the next time something looks off.

If your account is bidding on conversions that haven’t been verified in six months, send us the account for an audit — and when the basics are clean, move into server-side tracking for the attribution gaps client-side tags still can’t close.