Conversion tracking done right, so the numbers can be trusted.
Every optimisation decision, every bid strategy and every report rests on your measurement, and most of it is quietly broken. Duplicate conversions, consent gaps and browser restrictions leave the platforms optimising to bad data. We set up GA4, Google Ads conversion tracking, Consent Mode v2 and server-side tagging so what you count is what actually happened.
Conversion tracking is the measurement layer that records what people do after they click an ad, so the platforms can optimise and you can report honestly. Done right it spans GA4 and Google Ads conversion actions, Consent Mode v2 for lawful consent handling, and server-side tagging to recover data lost to browser and privacy restrictions. Rogue Logic sets this up deduplicated, consent-aware and validated, so smart bidding optimises to real outcomes rather than noise. Get the measurement wrong and every decision above it inherits the error.
Conversion tracking, in full.
Conversion tracking is the least glamorous part of paid media and the most consequential. Every automated bid strategy, every budget shift and every line in every report is only as good as the measurement feeding it. If your tracking double-counts purchases, fires on the wrong events, or silently drops a chunk of conversions to privacy restrictions, then Google's algorithms are optimising to a distorted picture and your reports are confidently wrong. This is where a surprising number of accounts are broken without anyone realising, because the dashboards still show numbers and the numbers still look plausible.
The modern measurement stack has three moving parts that have to work together. GA4 is now the analytics backbone, event-based and quite different from the Universal Analytics most setups were built around, and it is easy to configure so that events and conversions do not line up with what Google Ads records. Google Ads conversion tracking has its own actions, attribution settings and values that need to agree with GA4 rather than contradict it. And Consent Mode v2, now required for Google to use data from EEA and UK users, changes how and whether tags fire at all based on the choices people make in your consent banner.
On top of that sits the erosion of client-side tracking. Browsers cap cookie lifetimes, privacy features block third-party tags, and ad blockers remove a slice of measurement entirely. Server-side tagging answers this by moving data collection to a server-side container you control, which recovers conversions that would otherwise vanish, improves the quality of the signal sent to the platforms, and gives you far more control over what data goes where. It is more work to set up and it is not always warranted, but for accounts of any scale it is increasingly the difference between measuring most of the truth and measuring a shrinking fraction of it.
We treat all of this as one connected job, done once and done properly, then validated. This is measurement engineering, not reporting: the reporting sits downstream and only tells the truth if the tracking underneath it does. Four senior practitioners run these builds, with no junior layer, and we would rather spend the first weeks getting your measurement right than start spending against numbers we cannot trust.
Conversion tracking, broken down.
GA4 configuration and event mapping
A GA4 setup where events, key events and conversions actually reflect your business: the right actions tracked, values assigned properly, and the data lined up with Google Ads rather than quietly contradicting it. Most GA4 accounts we inherit were migrated in a hurry and never reconciled.
Explore →Google Ads conversion tracking
Conversion actions defined deliberately, with primary and secondary conversions set so smart bidding optimises to the outcomes that matter, correct attribution and values, and the deduplication that stops one sale being counted several times across tags and imports.
Consent Mode v2 implementation
Consent Mode v2 wired into your consent banner so tags respect user choices for EEA and UK visitors, with conversion modelling recovering data lawfully where consent is declined. Done so you meet the requirement and keep usable measurement, not one at the expense of the other.
Server-side tagging
A server-side tagging container where scale justifies it, moving collection to infrastructure you control to recover conversions lost to browser restrictions and ad blockers, improve signal quality to the platforms, and take back control of the data you share.
Enhanced conversions and offline import
Enhanced conversions and, where relevant, offline conversion import so first-party data and sales that close off-site are fed back into the platforms, sharpening bidding on the outcomes that genuinely make you money rather than just the on-site clicks.
Validation and ongoing QA
Debugging with real events, tag and trigger checks, and cross-checks between GA4, Google Ads and your back-end, so the numbers agree before spend rides on them, plus periodic QA to catch the breakages that creep in when sites change.
Explore →The way we run Conversion tracking.
Audit the current measurement
We start by finding out what your tracking is actually recording: duplicated conversions, misfiring events, consent gaps, GA4 and Google Ads figures that do not reconcile, and data lost to browser restrictions. Most accounts have at least one of these, and usually more.
Map what should be measured
We agree the actions that matter and what each is worth, then set primary and secondary conversions deliberately, so the platforms optimise to real business outcomes rather than every micro-event that happens to be trackable.
Rebuild the tracking
GA4 events and conversions configured cleanly, Google Ads conversion actions defined and deduplicated, and the two lined up so they tell the same story rather than two different ones.
Add consent and server-side where needed
Consent Mode v2 implemented against your banner so measurement is lawful, and server-side tagging deployed where scale and data loss justify it, to recover conversions and improve signal quality.
Validate before trusting it
We test with real events, check tags and triggers fire correctly, and reconcile GA4, Google Ads and your back-end figures, so no bid strategy or report rides on numbers we have not verified.
Monitor and re-check
Sites change, tags break, and consent tools update. One senior lead keeps the measurement under review and re-checks it periodically, so the tracking that was right at launch stays right.
How we approach Conversion tracking.
Measurement is the foundation, not a bolt-on
Smart bidding, budget decisions and reporting all inherit whatever your tracking feeds them. If conversions are duplicated, missing or firing on the wrong events, the algorithm optimises to fiction and the reports agree with it. We fix the measurement first, because everything above it is only as good as the data underneath.
Count real actions, deduplicated
One purchase should count as one conversion, valued correctly, once. We map the actions that actually matter, set primary and secondary conversions deliberately, and remove the double-counting and phantom events that make accounts look like they are performing better than they are.
Consent Mode v2, done lawfully
Consent Mode v2 is required for Google to use EEA and UK data, and it changes how tags fire based on user choices. We implement it correctly so you respect consent and still recover modelled conversions, rather than either breaking measurement or quietly ignoring the rules.
Server-side tagging where it earns its place
Browser restrictions, ad blockers and short cookie lifetimes erode client-side tracking. Server-side tagging moves collection to a server you control, recovering data and improving signal quality. We deploy it where the gain justifies it, not as a box-ticking exercise.
What Conversion tracking puts on your desk.
Who sets up your measurement, and how
Rogue Logic is the trading name of Bryley Ltd, a senior-led team of four practitioners with roughly forty years of combined experience. Your conversion tracking is built and validated by an experienced operator who understands GA4, Google Ads, Consent Mode v2 and server-side tagging as one connected system, not handed to a junior with a tag-manager template. We treat measurement as the foundation the whole account rests on, validate before we trust it, and will tell you plainly when your tracking is misleading you.
Senior people do the work
The person who audits your tracking is the person who rebuilds and validates it. No measurement build is parked with a junior copying a template, because a small error here quietly corrupts every decision above it.
Validated, not assumed
We test with real events and reconcile GA4, Google Ads and your back-end before spend rides on the data. If the numbers do not agree, we find out why rather than pick the flattering one.
Honest about what is trackable
Privacy rules and browser restrictions mean not everything can be measured perfectly, and anyone claiming otherwise is guessing. We recover what can be recovered lawfully, model the rest properly, and are clear about the limits.
Conversion tracking: common questions.
What is conversion tracking?
Conversion tracking is the measurement layer that records what people do after they click an ad: purchases, leads, sign-ups and the other actions that matter. It feeds the platforms so they can optimise bidding, and it feeds your reports so you can judge performance. Done properly it spans GA4, Google Ads conversion actions, Consent Mode v2 and, at scale, server-side tagging, all reconciled so they tell the same story.
What is server-side tracking and do I need it?
Server-side tracking moves data collection from the browser to a server-side container you control. It recovers conversions lost to browser restrictions, short cookie lifetimes and ad blockers, improves the quality of the signal sent to the platforms, and gives you more control over what data goes where. It is more work to set up and is not always warranted, but for accounts of any scale it is increasingly worth it. We advise honestly on whether it earns its place for you.
What is Consent Mode v2 and is it required?
Consent Mode v2 is Google's framework for adjusting how tags fire based on the consent choices your EEA and UK visitors make. Google requires it to use data from those users for measurement and audiences. Implemented properly it lets you respect consent and still recover modelled conversions where consent is declined, so you meet the requirement without losing all measurement. We wire it into your consent banner and validate that it behaves correctly.
Why do my GA4 and Google Ads numbers not match?
They rarely match exactly, because they attribute and count differently, but large gaps usually mean something is broken: duplicated conversions, events firing on the wrong actions, consent handling dropping data, or attribution windows that do not line up. We reconcile the two so the difference is explainable and small, rather than a mystery that undermines every decision made from the data.
How is this different from your reporting work?
Conversion tracking is the measurement engineering underneath; reporting is what sits on top. The reporting only tells the truth if the tracking is right, so we fix the measurement first. If you want the ongoing dashboards and honest monthly reporting built on that foundation, that is covered in our wider reporting and Paid & AI ads work.
Can you fix tracking that is already broken?
Yes, and it is often the first thing we do. We audit what your current setup is actually recording, find the duplicated conversions, misfiring events and consent gaps, rebuild GA4 and Google Ads tracking cleanly, and validate it with real events before any bidding relies on it. One-off tracking fixes are scoped at £119 an hour where you do not need an ongoing retainer.