Attributing booked calls back to the campaign that produced them
A booked call is the conversion that matters for most service businesses, and it almost always happens on someone else's domain — Calendly, HubSpot Meetings, an embedded scheduler. The booking confirmation fires on a page you don't own, so either nothing is tracked or every booking is credited to the scheduler as a referral. The fix is to capture the click ID before the visitor leaves and to source the conversion from the booking record, not the confirmation page.
Free30 minutesNo obligation
Booked calls · what breaks
The situation, as it usually presents — Booked calls
- 01
Bookings not appearing as conversions at all
Or all credited to the scheduler.
- 02
No way to tell which campaign produces calls that show up
Booked and attended are different outcomes.
- 03
Bidding optimizing toward form fills
Because that's the only thing being measured.
Booked calls · the fix
What changes — Booked calls
Bookings attributed to their source campaign
Not to the scheduler domain.
Attended calls distinguishable from no-shows
Two different conversion values.
Platforms fed the outcome that matters
Rather than the nearest proxy.
Booked calls · architecture
Why this pattern keeps recurring — Booked calls
Booked-call tracking fails in a specific and consistent way, and it's about custody of the identifier rather than about tags.
- 1
The confirmation page isn't yours
You cannot put a tag on a scheduler's confirmation screen, so the event has to come from the booking record.
- 2
The click ID dies at the domain boundary
Unless deliberately carried, it's gone before the booking exists.
- 3
Booked is not attended
Treating them as one conversion teaches bidding to buy no-shows.
- 4
Reschedules and cancellations move the outcome
And most implementations never send them.
Booked calls · diagnose
How the root cause gets found — Booked calls
In this order. Each step rules out a class of cause, so the last one usually has a single explanation standing.
- 01
Check what source bookings are attributed to
Scheduler as referral is the tell.
- 02
Book a real test call from a tagged click
Follow the click ID all the way.
- 03
Confirm the scheduler can carry hidden fields
Most can; some don't.
- 04
Check whether the webhook is available
Determines whether attended can be tracked.
- 05
Match a month of bookings on booking ID
Against platform conversions.
Booked calls · prove
How the work is proven — Booked calls
Against the client's own records, not a dashboard turning green.
Source of truth
Scheduler booking records, matched on booking ID
- Click ID present on a real booking record, verified end to end.
- Bookings attributed to campaigns rather than to the scheduler.
- Attended and no-show sent as distinct events with distinct values.
- Booking count reconciled against platform conversions for a closed month.
- Reconciled over a fully closed window, matched on ID rather than on totals.
- Payload evidence captured from real transactions and handed over.
- The same reconciliation repeated 30 days later.
Booked calls · free audit
What we check in the free audit
- Check what source bookings are attributed to
- Book a real test call from a tagged click
- Confirm the scheduler can carry hidden fields
- Check whether the webhook is available
- Match a month of bookings on booking ID
Checked against
Scheduler booking records, matched on booking ID
Free30 minutesNo obligation
Booked calls · when not to buy
Why there are no client numbers on this page — Booked calls
Most agency case studies lead with a percentage. This one doesn't, and the reason is worth stating.
- We don't publish client results we can't substantiate. An audit of this site in August 2026 found named testimonials and before-and-after figures that had never been measured — all of it was removed, and nothing has replaced it that isn't checkable.
- The results that do exist belong to clients under agreement. Publishing anonymised numbers without their sign-off would be the same problem in a thinner disguise.
- What we will commit to in writing is 95%+ conversion accuracy and 8+ Meta Event Match Quality, reconciled against your own order records. That is checkable by you, which a case study percentage never is.
- For proof from actual clients, the video testimonials on the site are real people describing their own rebuild. That is the strongest evidence we have, and it isn't a number we wrote.
Booked calls · what we deliver
What the work involves — Booked calls
Click ID captured before the visitor leaves
And carried into the booking as a hidden field.
Booking webhook wired to a server event
Created, attended and cancelled each handled.
Cross-domain linking where the scheduler supports it
Belt and braces.
Values assigned deliberately
A no-show isn't worth the same as an attended call.
Written guarantee
95%+ tracking accuracy
Measured against Scheduler booking records, matched on booking ID. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs the fault in your existing browser-side setup and verifies it on a live transaction. Honest about its ceiling: it fixes this instance, not the class.
- Root cause fixed, not worked around
- Verified on a live transaction
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Removes the class of failure rather than this instance. Money events sent from your order records through a first-party container on your own subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your order records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, for advertisers whose spend makes an attribution leak more expensive than the build.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds reversed at every destination
- Monitoring so the next break surfaces in days
FAQ
Booked calls questions, answered
Any that support hidden fields and a webhook — Calendly, HubSpot Meetings, Cal.com, Acuity and most others. If it supports neither, the ceiling is much lower and we'll say so.
Both, as separate events with different values. Booked gives volume for bidding to learn from; attended is the outcome you actually want.
Those need call tracking to attribute the source, then the same offline import path. Different mechanism, same principle.
Yes. The click ID captured at booking is exactly what an offline import needs, inside the 90-day window.
Free · 30 min
Attribute your booked calls properly
WhatsAppFree30 minutesNo obligation
