Conversion tracking without creeping on your customers

There are two bad ways to run online advertising.

The first is flying blind: spend money on Google and Meta, watch the phone, and guess which ads are working. The second is the “install everything” approach: drop every tracking script on the site, switch on every automatic setting, and let the ad platforms vacuum up whatever they can, including things your customers typed into your forms.

There’s a better middle path. When we set up tracking for Mainland Truck & Trailer, Northland Equipment and Blue Capital Equipment Finance, the goal was simple: know precisely which ads produce leads, while sending the ad platforms as little personal information as possible. Here’s how.

Start with what you actually need to know

Most businesses don’t need to know everything a visitor did. They need answers to a few questions:

• Which campaigns, keywords and ads produce enquiries?
• Which of those enquiries turn into customers?
• What does each lead, and each customer, cost?

Answering those takes a small number of well-defined events, not a firehose.

Define a handful of meaningful conversions

We track the actions that represent a real lead or real intent, and name them consistently across sites:

Event	What it means
generate_lead	An enquiry or quote form was successfully sent
rental_request_submit	A rental request was submitted
credit_application_submit	A finance or credit application was submitted
click_call	Someone tapped to call
click_whatsapp	Someone tapped to message on WhatsApp
finance_handoff	A visitor moved from a dealer site to the finance partner

The first three are the primary conversions that Google Ads is told to optimise for. Calls, WhatsApp taps and finance hand-offs are secondary: reported so we can see them, but not used to steer bidding, because a tap isn’t the same as a submitted application.

Two more details keep the numbers honest:

1. Events fire only after success. A lead is counted when the form has actually been sent, not when someone clicks the button and the submission fails.
2. Automatic extras are switched off where they double-count. GA4’s built-in “form interactions” tracking, for example, would count the same enquiry a second time alongside our own event, so we turn it off.

Count each lead once

Ad platforms sometimes see the same conversion twice, once from the browser and again from a retry or another source. Each lead event therefore carries a unique event ID, the lead’s own reference number, so the platform can deduplicate it. One enquiry, one conversion. In Google Ads, conversions are also set to count once per click, so a single visitor sending three forms doesn’t look like three wins.

Send behaviour, not identities

This is the part most set-ups get wrong. Ad platforms offer features that read form fields automatically: names, emails, phone numbers. They hash them and match them to user profiles. It can make reporting slightly richer. It also means your customers’ contact details leave your website for an advertising company without anyone deciding that on purpose.

Our approach:

• Our tracking code sends no names, emails or phone numbers to Google or Meta. Events describe what happened (a lead, a call tap), not who did it.
• Meta’s automatic advanced matching and automatic event set-up are switched off, so its script isn’t quietly reading form fields.
• Personal details are stripped from page addresses in GA4, in case an email or phone number ever ends up in a URL.

The ad platform needs to know that an ad produced a lead. It doesn’t need to know who the lead is.

Ask first, and respect the answer

Tracking tags shouldn’t assume consent. On the sites we build:

• Google Consent Mode v2 starts with advertising storage and ad personalisation denied. Tags adapt to that state: they can still send cookieless, aggregate signals, but nothing personalised.
• Where a site has a cookie banner, the Meta pixel loads only after the visitor accepts marketing cookies. Decline, and it never runs.
• On pages with especially sensitive forms, such as account applications, we can leave ad pixels off entirely. On Northland’s onboarding pages, for example, the pixel is deliberately not loaded.

We also flag where rules get stricter. Quebec’s Law 25 and European privacy rules, for instance, may require asking before any marketing tag runs, which can mean adding a consent banner to a site that doesn’t have one. That’s a decision for the business owner, and we put it in front of them rather than making it silently.

Still know which ad produced which customer

Here’s the part that makes it all worthwhile. Even without sharing personal data with ad platforms, every lead that reaches you carries its source: the campaign, the ad network and the click identifier from the ad that brought the visitor. That lands with the lead in your inbox or CRM.

So when a lead becomes a customer, you can trace it back to the exact campaign that found them, inside your own systems. No ad platform needs your customer list for that.

What this looks like in practice

1. Visitor clicks an ad. The click ID and campaign are captured.
2. They browse; consent state is respected throughout.
3. They submit a rental request. The rental_request_submit event fires once, with a unique ID and no personal data.
4. GA4 records the conversion; Google Ads imports it and learns which searches produce requests.
5. The lead arrives in your inbox or CRM tagged with its source and click ID.
6. Weeks later, it becomes a customer, and you know exactly which ad to thank.

What this means for you

Good measurement and respect for your customers aren’t in conflict. A careful set-up gives you everything you need to spend your ad budget well, with less legal exposure and nothing to feel uneasy about.

See how it fits our marketing service, or ask us to audit your current tracking.