Google Ads Conversion Tracking
Bidding algorithms are only as good as the signal you feed them. Most accounts I look into are optimizing hard toward conversions that are duplicated, mistimed, misattributed, or simply not the conversions that matter to the business. The algorithm isn't broken — it's doing exactly what it was told, and what it was told is wrong.
Fixing that isn't a settings toggle. It's an architecture problem, and it's the one I spend most of my time on.
What accurate conversion tracking actually means
- Primary vs. secondary conversion actions defined correctly, so your bidding strategy optimizes toward revenue-driving actions — qualified leads, purchases, bookings — instead of diluting the signal with newsletter signups and button clicks.
- Deduplication across platforms, so a conversion counted in GA4 isn't also double-counted through a separate Ads tag, inflating numbers that then feed straight into your bid strategy.
- Enhanced Conversions configured properly, matching hashed customer data to recover conversions lost to browser restrictions and ad blockers — without compromising user privacy or violating Google's data policies.
- Server-side tagging, where it's warranted, routing conversion data through a server container instead of relying entirely on the browser. This improves match rates, survives ad blockers and ITP/ETP restrictions, and gives you control over exactly what data leaves your systems and when.
- Offline and CRM conversion imports, so a lead that closes three weeks after the click still gets attributed back to the campaign, keyword, and ad that actually generated it — instead of vanishing into "direct" or "unassigned."
- Attribution windows and models set to match your actual sales cycle, not left on default settings that quietly undercount anything with a longer consideration period.
Why it matters
A campaign that "looks like it's underperforming" is sometimes just a tracking problem wearing a performance problem's clothes. I've seen budget pulled from channels that were actually working, and budget poured into channels that were only winning on paper because the tracking made them look better than they were.
Once the conversion signal is clean, the algorithm does what it's supposed to do: find more of what's actually working, faster. That's the entire value proposition of automated bidding, and it only holds if the data going in is correct.
How I approach it
- Audit the current conversion setup — what's firing, what's duplicated, what's missing, and where the reported numbers diverge from what the CRM or finance actually sees.
- Define the conversion hierarchy — which actions are primary, which are secondary, and how each should influence (or not influence) bidding.
- Architect the tracking, choosing browser-side, server-side, or a hybrid based on your traffic, tech stack, and privacy requirements — not defaulting to whatever's easiest to install.
- Wire in Enhanced Conversions and offline imports where they add real match-rate or attribution value, not just because they exist.
- Validate against real transactions, checking that what Google Ads reports actually reconciles with what the business closed.
- Document and hand off, so the setup stays intact as new campaigns, landing pages, and team members get added later.
This work depends on solid foundations in GA4 and Consent Mode v2 — conversion tracking is only as trustworthy as the tracking layer and consent signals it's built on top of.
If your bidding algorithm is optimizing toward the wrong thing, it doesn't matter how much budget you throw at it. Let's give it the right signal.