Scheduler Redirects

When someone books a call, most schedulers can send them on to a thank-you page on your own site with their name, email and phone added to the link. With scheduler identity capture turned on, the Atribu tracker reads those details on the thank-you page, links the booking to the visit (and the ad click) that produced it, and then removes the details from the address bar.

It is off by default because it reads personal data out of a link. Nothing is read until you turn it on.

Turn it on

1. Go to Settings → Tracking → Tracking Behavior and switch on Identify visitors from scheduler redirects. Save.
2. Copy the tracking snippet again and replace the one on your site. The new snippet contains window.ATRIBU_ENABLE_SCHEDULER_IDENTITY = true;.
3. Set up the redirect in your scheduler (below).

Both halves are needed: the tracker only reads the details when the snippet enables it, and Atribu discards them if the setting is off.

If you install with the npm package, pass enableSchedulerIdentity: true to init() instead of step 2.

Calendly

1. Open the event type → Booking page options (in older layouts: Confirmation page).
2. Under After booking, choose Redirect to an external site and enter your thank-you page, e.g. https://yoursite.com/thank-you.
3. Tick Pass event details to your redirected page.

Calendly then adds invitee_email, invitee_full_name, invitee_first_name, invitee_last_name, text_reminder_number (the phone for SMS reminders) and answer_1 … answer_10 (your booking questions) to the link. Atribu uses the email, the phone and the name; from the answers it only takes a value that is itself an email or a phone number. (Calendly's guide)

GoHighLevel

1. Open the calendar → Forms & Payment → Confirmation page, and choose Redirect to URL.
2. Enter your thank-you page with the contact's details as merge fields:

https://yoursite.com/thank-you?email={{contact.email}}&phone={{contact.phone}}&first_name={{contact.first_name}}&last_name={{contact.last_name}}

If your thank-you URL already has a ?, start with &email= instead.

Acuity Scheduling

Acuity does not add booking details to a redirect on its own. Use Integrations → Custom conversion tracking and paste a redirect that fills in Acuity's placeholders:

<script>
  window.top.location.href =
    "https://yoursite.com/thank-you" +
    "?email=" + encodeURIComponent("%email%") +
    "&phone=" + encodeURIComponent("%phone%") +
    "&first_name=" + encodeURIComponent("%first%") +
    "&last_name=" + encodeURIComponent("%last%");
</script>

What happens on the thank-you page

1. The tracker reads the email, phone and name from the link — before it records anything else.
2. It removes them from the address bar straight away (with history.replaceState), so they are not bookmarked, shared, re-sent on a refresh or passed on to the next page.
3. It sends one identify with the details inside the request body, never in a URL. Atribu links this visitor to the customer with that email or phone.

The booking itself still arrives from your scheduler's own integration (for example the GoHighLevel sync). This step is what connects it to the visit and the ad click.

An identify is only sent when a real email or phone number is present — a name on its own is not enough to recognise anyone. Placeholders that were never filled in ({{contact.email}}, %email%) are ignored.

Privacy

• Opt-in per profile. With the setting off, the tracker reads nothing and leaves the address bar alone. Atribu also drops any scheduler identify from a profile that has not opted in, without storing it.
• Never stored in a URL. For every profile — opted in or not — Atribu removes invitee_email, invitee_full_name, invitee_first_name, invitee_last_name, invitee_uuid, text_reminder_number, guests, assigned_to, answer_1 … answer_10, email, phone, first_name, last_name and full_name from every page URL and referrer before it is saved.
• Tell your visitors in your privacy notice that booking details are used to link their booking to their visit.

Next steps