All integrations

Stripe logo

Calendly Server-Side Tracking

Calendly Server-Side Tracking

Calendly Server-Side Tracking

Send every Calendly booking to your ad platforms, matched back to the ad that drove it.

Send every Calendly booking to your ad platforms, matched back to the ad that drove it.

Bookings happen on Calendly’s domain where no pixel can fire. PixelFlow receives each confirmed booking by webhook, matches it to the visit on your site and sends one Schedule event to Meta, TikTok and the rest.

Bookings happen on Calendly’s domain where no pixel can fire. PixelFlow receives each confirmed booking by webhook, matches it to the visit on your site and sends one Schedule event to Meta, TikTok and the rest.

LIVE CONNECTIONBrowser + server
Calendly
Snapchat logo

Why your ad platforms can’t attribute bookings from Calendly

Why your ad platforms can’t attribute bookings from Calendly

Why your ad platforms can’t attribute bookings from Calendly

The moment someone clicks Book a call, they leave your website for calendly.com and your ad tracking is left behind. Cookies can’t cross domains, so the click ID that ties that person to your ad stays behind on your site, and you cannot load a script on a page Calendly owns.

The moment someone clicks Book a call, they leave your website for calendly.com and your ad tracking is left behind. Cookies can’t cross domains, so the click ID that ties that person to your ad stays behind on your site, and you cannot load a script on a page Calendly owns.

A webhook alone is not the answer either. It says a booking happened and who booked, but nothing about the ad they came from.

Meta Ads Manager

0

booked calls attributed to your ads in Meta

Calendly

12

calls booked through Calendly

How PixelFlow fixes it

How PixelFlow fixes it

How PixelFlow fixes it

PixelFlow holds on to the visit, joins each Calendly booking to the click that caused it, then sends one Schedule event to every ad platform.

PixelFlow holds on to the visit, joins each Calendly booking to the click that caused it, then sends one Schedule event to every ad platform.

Stitches the click back on

Stitches the click back on

The click ID and browser details from the visit are joined to the booking the moment Calendly confirms it.

The click ID and browser details from the visit are joined to the booking the moment Calendly confirms it.

Fires from Calendly’s webhook

Fires from Calendly’s webhook

Every confirmed booking, even if the invitee closes the tab or never comes back to your site.

Every confirmed booking, even if the invitee closes the tab or never comes back to your site.

A value on every call

A value on every call

Give bookings a fixed value so your ad platforms can optimise towards booked revenue and report a return.

Give bookings a fixed value so your ad platforms can optimise towards booked revenue and report a return.

Sends the invitee’s details

Sends the invitee’s details

Name and email from the booking form, hashed before they are sent, plus the UTM parameters Calendly recorded.

Name and email from the booking form, hashed before they are sent, plus the UTM parameters Calendly recorded.

Sent once and logged

Sent once and logged

One Schedule event per booking, keyed to Calendly’s invitee ID, and logged so you can see it went out.

One Schedule event per booking, keyed to Calendly’s invitee ID, and logged so you can see it went out.

Connects in one click

Connects in one click

Sign in to Calendly and PixelFlow registers its own webhook. Nothing to paste and nothing to install on Calendly.

Sign in to Calendly and PixelFlow registers its own webhook. Nothing to paste and nothing to install on Calendly.

Embeds, pop-ups and links

Embeds, pop-ups and links

Inline widget, pop-up or a plain Calendly link, the webhook fires the same way for all of them.

Inline widget, pop-up or a plain Calendly link, the webhook fires the same way for all of them.

Every ad platform

Every ad platform

One connection feeds Meta, TikTok, Snapchat, Pinterest, Reddit and ChatGPT.

One connection feeds Meta, TikTok, Snapchat, Pinterest, Reddit and ChatGPT.

Choose what to send

Choose what to send

Pick the event name your ad platforms should receive for a booking. Schedule is the default.

Add a value if you want each call to count towards revenue and return on ad spend. Leave it blank to send the booking without one.

Calendly booking
Fires when an invitee confirms a booking
$
Sends Schedule on every confirmed booking.

Before & after using PixelFlow

Before & after using PixelFlow

Before & after using PixelFlow

What changes in Ads Manager once bookings are stitched back to the click.

What changes in Ads Manager once bookings are stitched back to the click.

Without PixelFlow
PixelFlow
Booked calls never appear against a campaign in Ads Manager
Every Calendly booking is matched back to the ad that drove it
Ad platforms optimise for clicks, not for people who book
Meta and the rest optimise towards confirmed bookings
Button clicks get counted as leads even when nobody books
Only confirmed bookings are sent, as a Schedule event
Lead events have a low Event Match Quality score
Hashed email, name, IP and click ID raise Event Match Quality
Bookings behind ad blockers or closed tabs go missing
The webhook fires on every confirmed booking, whatever the browser did
No value on a booking, so nothing to report a return on
Set a value per call and see a return on your lead campaigns

Send bookings from Calendly to your ad platforms

Send bookings from Calendly to your ad platforms

Send bookings from Calendly to your ad platforms

Connect any ad platform in one click. The same Calendly booking feeds each platform’s conversions API with the invitee’s hashed details and the ad click, so every Ads Manager sees the same booking once.

Connect any ad platform in one click. The same Calendly booking feeds each platform’s conversions API with the invitee’s hashed details and the ad click, so every Ads Manager sees the same booking once.

Set it up with your AI agent.

Set it up with your AI agent.

Set it up with your AI agent.

Connect the PixelFlow MCP server to your agent can set up and install everything. Prefer to build your own custom tracking? Just use our infrastructure and build on top of it.

Connect the PixelFlow MCP server to your agent can set up and install everything. Prefer to build your own custom tracking? Just use our infrastructure and build on top of it.

Setup

FAQ

Calendly tracking questions, answered

Calendly tracking questions, answered

Can’t find the answer you’re looking for? Get in touch and we’ll help you get set up.

It means your Calendly bookings reach Meta, TikTok and your other ad platforms from a server, through each platform's conversions API, rather than from a pixel in the visitor's browser. That matters more for Calendly than for most tools, because the booking happens on calendly.com where your pixel cannot run at all. PixelFlow receives each confirmed booking from Calendly by webhook and sends it on as a Schedule event.

Booking happens on Calendly's domain, not yours. Cookies do not travel between domains, so the click ID that ties a booking to an ad stays behind on your site. The call gets booked, but Meta only ever saw a click, so it reports no conversion and keeps optimising for clicks instead of for people who book.

PixelFlow captures the visitor's ad click and browser data when they land on your site and holds that visit while they book. When Calendly confirms the booking, PixelFlow waits a short moment for the thank-you page on your site, matches the booking to the visit by Calendly's invitee ID or the hashed email, and sends one Schedule event carrying the click ID, browser ID, IP address and user agent. If the visitor never reaches the thank-you page, the event still goes out with the hashed email and name.

No. The booking page belongs to Calendly, and embedded widgets run inside an iframe, so you cannot load your own scripts there. That is why a browser pixel alone can never attribute Calendly bookings, and why the fix has to happen server side.

Nothing goes on Calendly. In PixelFlow open Track More Events, choose Calendly and sign in with your Calendly account. PixelFlow registers its own webhook for new bookings and you are done. Calendly only offers webhooks on its paid plans, so the free plan will not work.

A Schedule event with the invitee's hashed email and name from the booking form, the UTM parameters Calendly recorded, an optional fixed value, plus the ad click ID, browser ID, IP address and user agent from their visit to your site. Personal data is hashed before it leaves PixelFlow, and each booking is sent exactly once.

Yes. The webhook fires on Calendly's side, so an inline embed, a pop-up widget and a plain Calendly link all behave the same. To stitch the ad click back on, point Calendly's redirect at a thank-you page on your site and include the invitee details in the link, which the setup guide walks through.

Meta, TikTok, ChatGPT Ads, Snapchat, Pinterest and Reddit. One Calendly connection feeds every platform you connect. Plans include one, three or five ad platforms, and you can add more from $10 a month each.

No. PixelFlow sends one Schedule event per booking, keyed to Calendly's invitee ID, so repeated webhooks never produce a second event. A click on your booking button is a different, earlier step, so if you track it at all, give it its own event name rather than calling it a booking.

Yes. PixelFlow supports consent-aware tracking so events respect your cookie banner, and personal data is hashed before it is sent to any ad platform. A data processing agreement is available.

Smarter, server-side tracking

Start sending accurate conversions today - no tag manager, no code, no developer required.

Compatible with

  • GoHighLevel logo
  • Kajabi logo
  • Stripe logo