Skip to content

If you can't measure it, you're bidding blind.

Conversion Tracking Setup

The most expensive move you can make in an ad account is starting optimization before measurement is set up correctly. If Google does not know which click turned into a real lead or sale, the smart-bidding algorithm learns from the wrong signal — and you pay for it every day. That is why conversion tracking is the first thing I check in any Google Ads engagement, before changing bids, budgets, keywords, audiences, or creative.

Good tracking goes beyond “seeing conversions” in a dashboard. The real purpose is to give Google Ads a clean, reliable signal that reflects business value. A form submission from a serious buyer is not the same as a casual page visit. A paid order is not the same as a product-page view. A duplicate conversion is not a success; it is a measurement error that can push the account in the wrong direction.

My developer background applies directly here. Conversion tracking is really a data-flow problem: the event fires, the tag triggers, the browser sends data, Google receives it, and the conversion is attributed to the correct ad click. The question is simple: does the data reach the right place, at the right time, in the right shape? I set it up, test it, and verify it before using it for decisions.

Why conversion tracking is broken so often

Conversion tracking is invisible infrastructure. When it fails, it usually does not show a clear warning. There is no big red error saying, “Your account is optimizing against bad data.” The numbers simply look wrong, incomplete, inflated, or suspiciously clean. Sometimes the account shows zero conversions even though leads are coming in. Sometimes it shows many conversions, but the business does not see matching enquiries or sales.

Typical problems include:

  • The tag was never installed, or it was placed on the wrong page.
  • The same conversion is counted twice because duplicate tags are firing.
  • GA4 and Google Ads conversions are mixed up or imported without a clear reason.
  • Forms with no thank-you page, such as single-page or AJAX forms, are not tracked.
  • Phone clicks, WhatsApp clicks, or other contact actions are tracked as if they were final leads.
  • Conversion actions exist in the account, but the wrong ones are marked as primary.
  • Data is lost because of cookie restrictions, consent settings, browser limitations, or ad blockers.
  • A conversion fires on page load instead of after a real action.
  • Test submissions, internal traffic, or admin actions are included in the data.
  • E-commerce purchases are tracked, but revenue value is missing or incorrect.

These are not small technical details. They change how the account behaves. If a duplicated form tag makes one lead look like two, smart bidding may think a campaign is performing better than it really is. If a WhatsApp click is treated as a primary conversion, Google may chase people who click a button but never become customers. If a purchase conversion has no revenue value, the account cannot properly distinguish a low-value order from a high-value order.

The result is the same: optimization becomes guesswork. You may raise budgets on the wrong campaigns, pause useful keywords, trust misleading CPA or ROAS figures, or judge the account by numbers that do not match the business.

Correct setup: layer by layer

Reliable conversion tracking is built in layers. Each layer has a specific role. If one layer is unclear, the rest of the account becomes harder to manage.

GA4 + Google Tag Manager

I manage tags through Google Tag Manager from a single container. This keeps tracking organised, versioned, and testable. Instead of adding scripts directly to different pages and hoping they work, tags, triggers, and variables can be reviewed in one place.

This is especially useful when a site changes. A developer may update a form, replace a checkout plugin, redesign a landing page, or move a thank-you page. If tracking is scattered through the site code, those changes can silently break measurement. With Tag Manager, the setup is easier to audit and adjust.

GA4 events and Google Ads conversions are also kept cleanly separated. GA4 is useful for broader behaviour analysis: page views, engagement, traffic sources, and user journeys. Google Ads conversions are used to guide bidding and campaign decisions. These two systems can share information, but they should not be treated as the same thing.

For example, a GA4 event may be useful for understanding behaviour on the website, while a Google Ads conversion action should represent something that matters commercially. Blending every GA4 event into Google Ads can make the account noisy. The goal is not to track everything as a conversion. The goal is to track the right things with a clear purpose.

Conversion actions and values

Each meaningful action should be defined separately. A phone click is different from a WhatsApp click. A contact form submission is different from a quote request. A purchase is different from adding a product to cart. When these actions are separated, the account becomes easier to read and easier to optimize.

For lead generation, common actions include form submissions, phone clicks, email clicks, WhatsApp clicks, booking requests, and quote requests. For e-commerce, the most important action is usually the purchase, with the real order value passed into Google Ads whenever possible.

Where possible, a value should be assigned. This can be a real sale amount in an e-commerce store, or an estimated average lead value in a lead-generation business. The point is to help Google understand that not all conversions are equal.

For example, if one campaign generates many low-intent contact clicks and another generates fewer but higher-quality quote requests, a simple conversion count may favour the wrong campaign. Value helps create a more realistic picture. It also makes value-based bidding, such as tROAS, possible when the account has enough reliable data to support it.

Value does not need to be perfect on day one to be useful. It needs to be logical, consistent, and based on how the business actually makes money. A structured estimate is better than treating every action as identical.

Primary vs secondary goals

Not all conversion actions should guide bidding. This is one of the most common issues I see in accounts.

A sale or qualified lead is usually a primary conversion. This means Google Ads can optimize toward it. It is the action that represents the main business objective.

Phone clicks, WhatsApp clicks, email clicks, or other softer interactions are often better as secondary conversions or observation signals. They are still useful. They help explain user behaviour and show whether people are engaging. But they should not always control bidding.

This distinction matters because smart bidding follows the goal you give it. If every micro-action is marked as primary, Google may optimize toward the easiest action, not the most valuable one. A click on a phone number may be easier to generate than a serious enquiry. A button click may be easier than a completed sale. If those actions are treated equally, the Google Ads budget can drift toward lower-value traffic.

A clean primary/secondary structure keeps the account focused. You still see the supporting actions, but the algorithm is not pushed to chase them at the expense of real outcomes.

Enhanced conversions

Enhanced conversions help recover some signal that may otherwise be lost because of cookie restrictions, browser changes, or consent limitations. The basic idea is straightforward: when a user submits contact details, such as an email address or phone number, that data can be sent to Google in a privacy-safe, hashed form. Google can then use it to improve conversion matching.

This does not mean exposing raw personal data in reports. The data is transformed before it is sent. The purpose is to help Google connect the conversion to the ad interaction more accurately.

Enhanced conversions are especially useful when normal browser-based tracking is less reliable. If a user clicks an ad, browses the site, and converts later, some of the original tracking information may be missing. Better matching gives the bidding system a more complete signal. A more complete signal means the account has a better chance of learning from real outcomes instead of partial data.

It is not a magic fix for poor tracking. It should sit on top of a correct setup, not replace it. The conversion event still needs to fire at the right moment, with the right action, and with the right value where relevant.

Server-side tracking when needed

Server-side tagging can make tracking more resilient by moving part of the data flow away from the browser and through a server-side environment. This can reduce data loss caused by ad blockers, browser restrictions, and some client-side limitations.

It is not needed for every account. A small lead-generation site with simple forms may not need the extra complexity. A larger account, a store with meaningful revenue volume, or a business relying heavily on accurate ROAS measurement may benefit from it more.

I recommend server-side tracking by scale and need. The setup should justify the complexity. The goal is not to build the most advanced tracking system possible. The goal is to build the right tracking system for the account, the traffic level, and the decisions being made.

Verification — the most skipped step

Setting up tracking is not enough. You have to prove it works.

This is the step many accounts skip. A tag is added, a conversion action is created, and everyone assumes the data is correct. But until a real test is completed, the setup is only theoretical.

Verification usually includes:

  • Checking tags in Google Tag Manager preview mode.
  • Triggering the action exactly as a real user would.
  • Confirming that the correct tag fires once, not zero times and not twice.
  • Checking that the event appears in GA4 where relevant.
  • Confirming the conversion action appears in Google Ads.
  • Looking for the correct status, such as recording.
  • Comparing reported conversions with the real lead or order count.
  • Testing special cases, such as AJAX forms, embedded forms, checkout redirects, or third-party booking tools.

A real test matters because websites often behave differently than expected. A form may submit without reloading the page. A thank-you message may appear inside the same URL. A checkout may send users through an external payment provider. A booking widget may run inside an iframe. A phone button may display differently on mobile and desktop. Each of these details affects how tracking should be implemented.

The final check is business reality. If the account reports ten leads but the CRM, email inbox, or order system shows something very different, the numbers need investigation. Reporting platforms are useful, but they are not the source of truth by themselves. The data must match what the business actually receives.

I make no optimization decision before this check. Changing bids, budgets, campaigns, or keywords before measurement is verified risks improving the wrong thing.

What clean measurement changes

Correct tracking makes every later decision better.

It helps identify which campaigns produce real enquiries or sales, not just clicks. It helps separate valuable traffic from cheap traffic. It makes bidding strategies more reliable because they are trained on meaningful actions. It makes reports easier to trust. It also reduces the amount of opinion in account management, because decisions can be tied back to verified outcomes.

For lead-generation accounts, clean tracking can show whether form leads, calls, WhatsApp conversations, or booking requests are coming from the right campaigns. For e-commerce accounts, it can show whether revenue is being attributed correctly and whether the account can optimize toward value rather than only order count.

It also prevents common false conclusions. A campaign may look weak because conversions are not firing. Another may look strong because it is double-counting. A branded campaign may appear to drive all sales because attribution is not understood. A Performance Max campaign may look profitable because the conversion value is inflated. Without measurement discipline, these problems are easy to miss.

A practical foundation for Google Ads management

Conversion tracking is the foundation of account management, not a one-time technical checkbox. It should be reviewed when the website changes, when new forms or landing pages are added, when the checkout changes, when consent settings are updated, or when new conversion goals are introduced.

Correct measurement is the foundation of Google Ads management; for ROAS measurement in e-commerce: e-commerce Google Ads. If you are not sure your account is measuring correctly, get in touch — a quick check and I will tell you.

Frequently asked questions

How do I know if my conversion tracking actually works?

The fastest way: trigger a real conversion (form, call) in Google Tag Assistant / Tag Manager preview mode and watch the tag fire. Then the conversion action in Google Ads should be 'Recording' and the numbers should match your real lead count. In most accounts this check has never been done.

Is a GA4 conversion the same as a Google Ads conversion?

No. GA4 records an analytics event; the conversion Google Ads uses for bidding is defined separately (either imported from GA4 or via a direct Ads tag). Mixed up, you get double-counting or under-counting. I set up clearly which one is primary.

What are enhanced conversions, and do I need them?

As cookie restrictions grow, some conversions are lost. Enhanced conversions reduce that loss by matching the user's (hashed, privacy-safe) email/phone data, giving the bidding algorithm a more accurate signal. In most accounts it provides a measurable benefit.

Do I need server-side tracking?

Not always. Server-side tagging gives more resilient data against browser restrictions and ad blockers, plus better control — but it has setup and maintenance cost. It makes sense once traffic and budget reach a certain scale; on a small account, getting client-side right first is enough.

Can you track phone and WhatsApp clicks?

Yes. Phone clicks, WhatsApp clicks, form submissions and (in e-commerce) sale/cart events are set up as separate conversion actions. Deciding which are 'primary' for bidding and which are just 'observation' is critical so the algorithm optimizes the right thing.

Have a project in mind?

Tell me what you're building. I usually reply within a day.

Start a project