Local measurement without third-party cookies

Budget season starts the week after Labor Day, and it opens with the same argument every year. Somebody has a platform screen saying one number, somebody else has a schedule saying another.

They are not going to agree. The sooner that is accepted, the sooner you can measure what is still measurable and stop paying for certainty that no longer exists.

Here is how we set measurement up for local accounts now, and how we report it without pretending.

What actually broke, and what did not

Third-party cookies are still in Chrome. Google cancelled the plan to remove them in 2024 and has not revived it. Worth saying plainly, because proposals still open with a deadline that is not coming.

What did happen is quieter and more permanent. Safari and Firefox have blocked third-party cookies by default for years. App tracking permission took the mobile signal down. Link Tracking Protection strips parameters in Mail, Messages and private browsing. Mail privacy features made email open rates meaningless. Browsers cap how long a script-set cookie survives, so a visit in March and a booking in May are two different people as far as the tag is concerned.

None of it is one event you can point at. It is a slow reduction in how much of the path between an advert and a booking anyone can see.

What has not changed: the two ends. Demand is visible and the booking is visible. It is the middle that went dark.

Call tracking, set up so it does not cost you anything

For most local businesses the booking still happens on the phone, so call tracking carries the measurement load. It is also the easiest thing to install badly.

• Dynamic number insertion on the website, so the number shown swaps by source, with a pool big enough that two visitors in the same hour do not share a number.
• A separate static number per offline channel. Van, mailer, signage, sponsorship. Cheap, and it settles arguments that run for years.
• Consistent numbers where people compare them. Keep your real number as the primary on the profile and your contact page. If a tracking number goes on a listing, add the real one as an additional number.
• Recording rules checked before the first call. Several states require every party to consent. Announce it, and set a retention period.
• Spam and existing customers tagged out. Raw call volume is a vanity number. The one that matters is new customer calls, and it is always smaller than the total.
• Every call given an outcome in the CRM. Booked, not booked, wrong number, existing customer. Without this step you have call counts, not measurement.

The outcome is the step that fails in real offices, because it depends on whoever answers the phone updating a record while the next line rings. Make it two clicks or it will not happen.

Capture the event at your end

The principle: anything you want to report on next year has to be written down by your own systems this year.

1. Store the click identifiers with the lead. Whatever the ad platforms pass through on the landing page, captured as hidden fields on every form and kept on the contact record. It does nothing until the booking happens, and then it is the only clean line between spend and work.
2. Store the first landing page and the referrer too. Cheap to keep, and it survives when a click id does not.
3. Ask people. “How did you hear about us” answered into the same record as everything else. It is a weak signal alone and a useful one alongside two others.
4. Send outcomes back, not form fills. Offline conversion import from booked work. An automated bidding system fed real bookings buys differently from one fed form submissions.
5. Keep health information out of it. For dental and medical accounts the tracking-technology guidance has been revised and partly struck down in court since it first appeared, so the safe position is the conservative one rather than the current letter of it. No third-party pixels on pages that reveal a condition, no procedure names in event parameters, no identifiers leaving your systems from a booking confirmation page. Measure the channel, not the patient.

The CRM, not the analytics property, is the source of truth here. Analytics tells you about traffic. The record of who booked, for what, and whether they showed up, is the report.

Report a range, and say how you got it

This is the part most reporting gets wrong, and the part clients respect once you fix it.

Platform conversion numbers include modelling. Some conversions are observed, others estimated, and the total prints as a whole number with no indication of which is which. Presenting it as fact is how you end up defending it six months later.

What we send instead:

• Booked work, total. One number, from the schedule, not from a tag. This one is certain.
• Booked work by source, as a range. A floor from what is directly attributed, a ceiling that includes a reasonable share of the unknown bucket, and the method stated in one line.
• The unknown bucket, shown honestly, with its size tracked month to month. It growing slowly is normal. It doubling means something broke in capture.
• Cost per booked job as a range too, derived from the same floor and ceiling.
• One decision the numbers support, and nothing else dressed up as insight.

When a decision rides on it, stop modelling and run a test. Pause a channel for a fortnight and watch total booked work, or run it in half the service area and not the other half. A blunt experiment beats a precise model built on a path nobody can see.

If you sell reporting to clients

Two things are worth changing.

Put the measurement setup in the proposal as its own line: call tracking, event capture, CRM fields, conversion import. It is real work and real hours, and it is what makes every later report defensible. Clients who will not pay for it argue with the reports hardest.

Then say the range out loud in the first meeting rather than the fourth. “We can tell you exactly how much work you booked, and roughly where it came from” is a sentence that survives the year. A precise channel number that changes every time a platform updates its modelling does not.

What we are telling clients

• Check that your forms are still capturing click ids and a source field. They stop working silently after a site change more often than anything else here.
• Give every inbound call an outcome in the CRM, and make it two clicks for whoever answers.
• Turn on offline conversion import from booked work for your main paid campaign.
• Audit your dental or medical site for third-party pixels on pages that should not have them.
• Rebuild last month’s report with a floor, a ceiling and an unknown bucket, and see whether any decision changes.
• Pick the channel you argue about most and schedule a two-week holdout in a quiet fortnight.

The measurement work is unglamorous, and it is the only thing that keeps Google Ads spending honestly while the middle of the path stays dark. Almost all of it happens in the CRM rather than in an analytics tool, which is why we build the two together. Agencies reselling through our white-label side get the same setup and the same ranges.