Skip to main content
Acuity → Apple Search AdsIntegration guide

Connecting Acuity Scheduling to Apple Search Ads

Acuity holds the appointment for a very large number of small service businesses, and its booking page sits on Acuity's own domain. Apple Search Ads sells App Store placement, which means it lives entirely inside Apple's privacy framework and behaves unlike every other destination here. The join between them succeeds or fails on one thing: whether no user-level click identifier reaches the Acuity appointment before the conversion happens, because Apple Search Ads can only match a conversion it can tie back to a click it recognizes.

Free30 minutesNo obligation

Specific to this pair

Acuity and Apple Search Ads: why there is almost nothing to join

For most Acuity businesses there is nothing to measure: bookings happen on a web page with no app involved. Only a business whose own iOS app books through the Acuity API or a web view can report completed bookings as post-install events through its mobile measurement partner, while Apple attributes installs in aggregate.

Apple Search Ads sells App Store installs. Acuity takes bookings on a web page. For the large majority of Acuity businesses there is no app at all, and therefore nothing for Apple Search Ads to attribute. Clients do not install anything to book through Acuity; the scheduling page runs in a browser, so a booking never passes through Apple's install attribution path.

The only version of this pair that makes sense is a business with its own iOS app that books appointments through the Acuity API or an in-app web view. In that case the attribution token is read in the app at first launch, the install is attributed in aggregate by Apple, and a completed booking is reported as a post-install event through whatever mobile measurement partner you use. The Acuity appointment never touches Apple directly. The appointment ID belongs in your own database next to the app user, so you can at least count how many app-originated bookings were attended rather than canceled.

If you run Apple Search Ads to promote an app but clients still book on the web, the honest answer is that you will measure installs at campaign level and bookings separately, and the connection between the two is a judgement over a settled period, not a join.

Acuity → Apple Search Ads · what breaks

Why this join usually fails — Acuity → Apple Search Ads

  1. 01

    No user-level click identifier never reaches Acuity

    The booking page is a different origin, so your first-party cookies do not follow the client there. The identifier has to be passed as a prefilled custom intake field, and that single hop is where almost every Acuity setup fails.

  2. 02

    The hosted booking page loses the thread

    Cookies do not cross the origin boundary, so unless the identifier is passed deliberately the appointment record has no trace of the campaign that produced it.

  3. 03

    Expecting per-user attribution that does not exist

    Teams arrive expecting a click ID to join against and there is not one. Apple's framework is aggregate by design, with thresholds and delays, and no vendor can engineer around it.

  4. 04

    Nothing reconciles afterwards

    Apple Search Ads reports at campaign level with built-in delay and privacy thresholds. Reconciling it per user against your own records is not possible by design; compare install and post-install volumes at aggregate level over a settled window instead.

Acuity → Apple Search Ads · the fix

What working looks like — Acuity → Apple Search Ads

  • No user-level click identifier on every appointment

  • Conversions arriving in Apple Search Ads

    Results appear in Apple Search Ads reporting at campaign or keyword level, aggregated and delayed by design rather than by fault.

  • Reconciled against the source

    Acuity Scheduling's own records are the reference, not either dashboard.

Acuity → Apple Search Ads · architecture

How Acuity and Apple Search Ads actually connect

  1. 1

    Acuity Scheduling holds the truth

    Appointment types carry prices, so the record already distinguishes a free discovery call from a paid session. That distinction is the most useful thing in the whole dataset.

  2. 2

    Apple Search Ads needs a click to match

    Apple Search Ads needs the install and post-install events reported through its supported attribution path. There is no offline conversion upload in the sense the other platforms mean it, and expecting one is the usual source of wasted effort.

  3. 3

    The identifier is the bridge

    No user-level click identifier, captured at the visit and carried into the Acuity appointment.

  4. 4

    The event source decides reliability

    Fire on attendance where the business marks it rather than on booking, because no-show rates on cold paid traffic are meaningful and vary by campaign.

  5. 5

    Deduplication at the destination

    Deduplication is largely not your problem here, because you are not sending duplicate user-level events — Apple aggregates. What matters instead is not double-counting an install across your own MMP and Apple's reporting.

Acuity → Apple Search Ads · normal or broken

Working vs. broken, side by side — Acuity → Apple Search Ads

Normal, not a fault

  • No user-level click identifier present on the appointment

    Visible on the record itself in Acuity Scheduling, not merely captured somewhere on the site.

  • Sent from the Acuity appointment webhook

  • Deduplicated correctly

    Deduplication is largely not your problem here, because you are not sending duplicate user-level events — Apple aggregates. What matters instead is not double-counting an install across your own MMP and Apple's reporting.

  • Reconciles with the source

    Apple Search Ads's count and Acuity Scheduling's records agree within a few percent over a closed window.

Actually broken

  • No user-level click identifier missing on most records

    The booking page is a different origin, so your first-party cookies do not follow the client there. The identifier has to be passed as a prefilled custom intake field, and that single hop is where almost every Acuity setup fails.

  • Sent from the browser

    Cookies do not cross the origin boundary, so unless the identifier is passed deliberately the appointment record has no trace of the campaign that produced it.

  • Counted twice, or not at all

    Teams arrive expecting a click ID to join against and there is not one. Apple's framework is aggregate by design, with thresholds and delays, and no vendor can engineer around it.

  • Nobody has reconciled it

    The dashboard shows a number and no one has compared it to Acuity Scheduling.

Acuity → Apple Search Ads · diagnose

Diagnostic order — Acuity → Apple Search Ads

  1. 01

    Count appointments carrying no user-level click identifier

  2. 02

    Follow one real conversion end to end

  3. 03

    Pull a recent appointment and read the custom field

    Empty means the booking URL is not carrying it, which is the usual cause and the ceiling on everything else.

  4. 04

    Check whether your reporting expectations match Apple's framework

    If someone has promised per-user joins on App Store installs, that is the problem — not the implementation.

  5. 05

    Read the match rate, not the success message

    Apple Search Ads reports at campaign level with built-in delay and privacy thresholds. Reconciling it per user against your own records is not possible by design; compare install and post-install volumes at aggregate level over a settled window instead.

Acuity → Apple Search Ads · prove

How it gets proven — Acuity → Apple Search Ads

Against Acuity Scheduling's own records, not against either platform's dashboard.

Source of truth

Acuity's appointment records — appointments attended by date, with their types.

  • No user-level click identifier confirmed present on a live appointment.
  • Aggregate install and post-install volumes reconciled over a settled window, with the framework's delay stated.
  • A booking made through the Acuity page with the identifier confirmed on the appointment record.

Acuity → Apple Search Ads · free audit

What we check in the free audit

  • Count appointments carrying no user-level click identifier
  • Follow one real conversion end to end
  • Pull a recent appointment and read the custom field
  • Check whether your reporting expectations match Apple's framework
  • Read the match rate, not the success message

Checked against

Acuity's appointment records — appointments attended by date, with their types.

Get my free conversion tracking audit

Free30 minutesNo obligation

Acuity → Apple Search Ads · when not to buy

When you don't need this — Acuity → Apple Search Ads

  • If Apple Search Ads already reports conversions that reconcile against Acuity Scheduling's records within a few percent, this join is working and there is nothing to buy.
  • Measure identifier coverage yourself first — pull your last hundred appointments and count how many carry no user-level click identifier.
  • This is one of the smaller builds here and a competent developer can do it — a prefill parameter and a hidden field.
  • If you have no iOS app, this destination does not apply at all — and if you do, budget for aggregate reporting rather than the per-order joins the rest of this library describes.

Acuity → Apple Search Ads · what we deliver

What gets built — Acuity → Apple Search Ads

  • Identifier capture into Acuity

    Append the identifier to the booking URL and map it to a hidden custom question, then confirm on a real booking that the value actually landed rather than trusting the configuration.

  • Event source: the Acuity appointment webhook

    Fire on attendance where the business marks it rather than on booking, because no-show rates on cold paid traffic are meaningful and vary by campaign.

  • Dispatch to Apple Search Ads

    Attribution through Apple's own APIs, with post-install events reported through your mobile measurement partner where you use one.

  • Reversals where they exist

    Cancellations reverse; reschedules move the conversion rather than reversing it, and the two need distinguishing.

Written guarantee

95%+ tracking accuracy

Measured against Acuity's appointment records — appointments attended by date, with their types.. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Acuity → Apple Search Ads questions, answered

Only indirectly, and only if your own iOS app is where the booking starts. Apple attributes installs in aggregate; the booking has to be reported as a post-install event through your measurement partner.

Free · 30 min

Get Acuity and Apple Search Ads joined properly

Free30 minutesNo obligation