CoachingClient work

Your Tracking Is Fine. Your Ad Isn't.

An audit of a Spain-based coaching funnel separated an underperforming ad from a working Lead signal. I then built a client-owned Calendly-to-Meta server route.

The brief

Context

A Spain-based coaching business used a WordPress landing page and Calendly for bookings. Meta ads were sending visitors to the funnel, but the owner suspected that broken tracking explained the lack of leads.

I audited the browser events, server activity, campaign result signal and booking path before proposing changes.

Sounds familiar?

Symptoms

The investigation

Diagnosis

The standard Lead event was active and the campaign was reporting Lead results. Other ads in the same campaign did generate leads. The evidence did not support a global Pixel or CAPI outage as the explanation for the underperforming ad.

My first recommendation was to review that ad’s message and its fit with the landing page and booking intent. I did not sell a tracking rebuild as the cure for its conversion rate. The audit identified ad-level underperformance; it did not prove whether the underlying cause was the creative, the audience or the offer.

The event diagnostics also showed a useful distinction:

Signal in the audit	Event Match Quality
Standard Lead	7.1
Calendly booking event	9.3

Those are different event types in the audit, not a before-and-after score for the same Lead event. The stronger booking signal supported a separate improvement: carry the completed booking back to Meta reliably.

Handover

What I built

Delivery noteDelivered Jun 2026

I built a Calendly booking route through a Cloudflare Worker to Meta Conversions API. The Worker verifies the webhook signature with HMAC, accepts the booking event, constructs the server Lead and hashes the customer fields before sending them.

I connected the booking to the browser session so the browser and server Lead share an event identifier for deduplication. The campaign information also travels through the booking path, so the booking is connected to the visit that produced it.

I moved the Worker into the client’s own Cloudflare account. The handover explains where each piece lives, how the shared identifier travels through Calendly, and how to check a booking in Meta. I also put the revised landing page into production.

Before → after

Results

Client work Done for real clients. Client details are anonymised.

The audit separated a working conversion signal from an ad that was not converting. The implementation then gave the completed booking a verified server route, browser/server deduplication and infrastructure the client owns.

The observed ad result remained 94 clicks and 0 reported leads in the audit window. This case does not claim a later improvement in lead volume, conversion rate or advertising return. The booking route improves the measurement of bookings that happen; it does not make an unconvincing ad produce them.

Traffic and reported leads for one underperforming ad, same audit window

May 2026-27

94 link clicks

Before
94 link clicks

After
0 reported leads

A note from Daniilbefore you decide

What this means for a similar business

Before rebuilding tracking, I check whether the campaign’s conversion event is arriving and whether the failure affects every ad or only one. Once that is clear, a booking webhook can improve the evidence around a real appointment. It is a separate engineering decision from changing the ad.

— Daniil

Situations this case answers

All situations

Read another case

67 Days of Zero Purchases in GA4, and Nobody Noticed

An audit of a UK subscription supplements brand: 67 days of zero GA4 purchases, renewals credited to 119-day-old clicks, and 44% of new orders untraceable.

Hi, I’m Daniil.

I work with you from defining the problem to implementation and handover. You talk to the person who does the work. I work in English and Russian.

My story My work

Have a similar task?

Describe your task

The first answer is free, within one working day. Or write directly: next@taskfordaniel.com