Loading
Google Ads and Meta
Booking
Form
When someone books through the Calendly embed on your site, Hippo cleans the booking, then sends Google Ads and Meta a conversion for each booking you count. You own the record of which campaign brought each booking Hippo receives, whoever runs your ads.
No annual contracts.
Transparent pricing.
We set it up for you.
Calendly offers no BAA (as of 10/13/26), and its terms have you promise that the data in your Calendly account contains no protected health information. That promise covers what people type when they book, since Calendly treats it as your data.
Meta integration
With Calendly's Meta Pixel integration connected, your Meta (Facebook) Pixel records visits and bookings on your Calendly booking page, under Calendly's own event names. Meta's terms(opens in a new tab) bar data that includes or is based on health information.
Analytics integration
Calendly's Google Analytics integration labels booking events with the event type's name(opens in a new tab), so when an event type is named for a service, Google gets the service's name. Google offers no BAA for Google Analytics.
Workaround
Calendly can send people who book to your thank-you page, where your tags count the conversion. With Pass event details turned on(opens in a new tab), Calendly adds the invitee's name, email and any answers to that page's address, which those tags can pass on to Google and Meta.
Book your appointment
Book now
Call us
Sent
Hippo sends Google Ads and Meta a conversion under a neutral name for the bookings you count, and Meta gets it through the Conversions API in place of your Meta Pixel. On your pages, Hippo waits for consent where it is required.
Excluded
Names, emails, phone numbers, dates of birth and IP addresses. The event type's name, the answers to invitee questions and routing forms, and the URL path are left out too.
Held
An event Hippo doesn't recognize stays in Hippo, so a new form on your site can't start sending to Google Ads or Meta on its own.
Kept
Hippo stores what it records in its own storage under the BAA it signs with every customer, with a log of what Hippo sent Google Ads and Meta and what it removed first.
Their reports stop at the click on the booking button.
If you see 50 clicks a month to the booking page but only a handful of actual bookings, it's impossible to troubleshoot.
I've found Calendly borderline impossible to track.
They find out when they go looking for one.
Calendly does not have a BAA, or at least not as of the last time I checked, so it is not HIPAA if you're letting clients use it to schedule.
Up to $3.5 million
The laser and injectables chain settled claims that tracking on its website shared the personal information of people who used it to schedule a consultation. Payments for approved claims were issued on September 30, 2026.
Proposed
Patients alleged that Google tracking was installed on the scheduling software dental clinics put on their own websites, and that what they entered to book was disclosed to third parties, including Google. The vendor has agreed to a $5.75 million settlement(opens in a new tab), and the final approval hearing(opens in a new tab) is set for March 25, 2027.
Hippo ties each booking it receives to the campaign that produced it, in a record you own, and sends the ones you count to Google Ads and Meta as conversions, whatever each platform does with them.
An independent record of results in an account you own. If you change agencies, it stays with you.
Calls that start from an ad are counted as conversions alongside forms and bookings.
A log of what Hippo sent Google Ads and Meta and what it removed first.
Hippo works with the ad platforms and website tools your practice already uses.
$99/month
Month to month.
Start now, no demo call1,000 visitors/month$199/month
Month to month.
Start now, no demo call2,000 visitors/month$299/month
Month to month.
Start now, no demo callCalendly publishes no BAA for any plan, Enterprise included. Its customer terms(opens in a new tab) have you promise that your Calendly data contains no protected health information, and Calendly treats what invitees enter(opens in a new tab) as your data, so that promise reaches invitee questions and routing forms. The same terms let Calendly suspend an account(opens in a new tab) that breaks it. Under HIPAA, you may share protected health information with a business associate only with that business associate's own assurance(opens in a new tab).
See which campaigns bring new clients.
Connect campaign spend to intake inquiries.
Measure consultation bookings by campaign.
Understand what drives online bookings.
See which campaigns bring transfers and refills.
Booking
Form
Records events
Removes identifying information
Sends clean conversion data
Excluded from conversion events
Names
Conditions
IP addresses
Clean conversion events only
Booking
Form
We take the Google tag and the Meta Pixel off your pages and install Hippo on a subdomain of your domain. We change your Calendly settings with an owner or admin of the account.
When someone who clicked your ad books through the Calendly embed on your site, Calendly tells Hippo, and Hippo ties the booking to the campaign that brought them.
For the bookings you choose to count, it leaves the event type's name out and gives each conversion a neutral name of its own.
Hippo sends it from its own server. Whoever runs your ads sees the booking conversions arrive in Google Ads and in Meta's Events Manager.
During setup we switch off both integrations, turn off Pass event details on any redirect and take the booking tags off your pages, so Calendly's integrations and Hippo do not both report the same booking.
Proposed
The mental health practice group agreed to a $3,027,874.44 settlement of claims that tracking pixels on its public website disclosed patients' information to companies including Meta and Google. One group in the class is the patients who booked a session through its online booking tool, and the final approval hearing is set for October 16, 2026.
Pending
A patient alleges that Google's tracking technologies on the physical therapy network's booking website sent Google information about the appointments he booked, including the type of appointment. In July 2026 the court refused to throw out the amended complaint(opens in a new tab).
Pending
Patients allege that Google tracking on the telehealth dietitian service's website sent what they entered while booking, including the appointment date and the dietitian's name, and the consolidated complaint names Meta as a recipient too. In April 2026 the court refused to throw out the federal Wiretap Act claim(opens in a new tab).
Each case involves tracking on a site where patients booked care online.
See what your site sends to Google Ads and Meta(opens in a new tab)Hippo
Server-side conversion tracking under a BAA, at a price a practice can actually pay.
No. Hippo takes over one job: getting the bookings you choose to count to Google Ads and Meta as conversions. Your event types, invitee questions and booking pages stay in Calendly, under Calendly's terms. The BAA you sign with Hippo covers Hippo. Meta Ads offers no BAA, and Google offers one for Local Services Ads(opens in a new tab) and none for the Google Ads campaigns advertisers run on search, display and YouTube, so Hippo controls only what it sends them.
We switch off both during setup, and Hippo sends Google Ads and Meta the booking conversion instead. Calendly's Meta Pixel integration(opens in a new tab) puts your Meta Pixel on your Calendly booking page, where it records visits and bookings, and Meta's terms bar data that includes or is based on health information. Its Google Analytics integration labels booking events with the event type's name, and Google offers no BAA for Google Analytics(opens in a new tab). For Google Ads, Calendly has you link Google Analytics with Google Ads(opens in a new tab) and import the conversions, and it has no Google Ads integration of its own.
Calendly shows its own confirmation page(opens in a new tab) unless you set a redirect. With Pass event details turned on, Calendly adds the event type name and the invitee's name, email, any text reminder number and answers(opens in a new tab) to your thank-you page's address. Keep personal information out of the page addresses Google receives(opens in a new tab), and check the URL parameters you send Meta, which can carry data Meta prohibits(opens in a new tab). During setup we turn off Pass event details and take the booking tags off your thank-you page.
Hippo sends them a conversion under a neutral name, for the bookings you choose to count. Before a booking leaves Hippo, Hippo removes names, emails, phone numbers, dates of birth and IP addresses. The event type's name, the answers to invitee questions and routing forms, and the URL path are not part of the conversion. Hippo gives each conversion a name that implies no condition, treatment or service, as Meta's terms require(opens in a new tab) of event names.
Yes. When someone who clicked your ad books through the Calendly embed on your site, Calendly tells Hippo, and Hippo ties the booking to the campaign that brought them, in a record you own. If it is a booking you count, Hippo sends Google Ads and Meta a conversion under a neutral name.
Not from a Calendly integration and Hippo both sending it. During setup we switch off Calendly's Meta Pixel and Google Analytics integrations, turn off Pass event details and take the booking tags off your pages. Google Ads removes duplicates only within one conversion action(opens in a new tab), so a booking reported by two conversion actions active in the same campaign can count twice. We check your Google Ads account on a walkthrough for booking conversions it already counts, such as ones imported from Google Analytics.
You choose which bookings count as conversions, and Hippo sends Google Ads and Meta only those. We set that up with you. Hippo names each conversion itself, so an event type's name never becomes the name of a conversion it sends.
We do. Whoever controls your domain adds a DNS record for your Hippo subdomain, and we install Hippo. With an owner or admin of your Calendly account, we disconnect Calendly's Meta Pixel(opens in a new tab), switch off its Google Analytics integration and turn off Pass event details on any event type that redirects. Your agency keeps running the campaigns and sees the booking conversions arrive in Google Ads and in Meta's Events Manager.
Yes. Your developers can send a booking from your own server to Hippo, and Hippo cleans it and sends Google Ads and Meta a conversion under a neutral name, as it does for a booking in the embed.
No. Meta's terms cover booking conversions like any other event, and sending an event from a server changes the route and leaves what it carries as it was. Meta can restrict certain mid and lower funnel standard events(opens in a new tab) for sites in its health and wellness category, and under a restriction, custom events stay blocked(opens in a new tab) until you review and confirm them. Hippo cannot lift a category Meta assigns or restore an event Meta blocks, and it never renames an event to get past a restriction. You can ask Meta to review(opens in a new tab) the category. Hippo still records your bookings by campaign, whatever Meta blocks.
Yes, if you want to know how these laws apply to your business. This page describes Calendly's terms, laws and court cases for general information and is not legal advice. Hippo handles the tracking; an attorney can advise you on your obligations. Hippolytics is not affiliated with, endorsed by or sponsored by Calendly.
Compare acquisition across your campaigns.
See which campaigns drive consultations.
Know your cost per booked patient.
See which promotions get booked.
Connect campaign spend to appointments.
See which campaigns book consultations.
Measure calls and booking inquiries.
See which campaigns bring new patients.
See which campaigns bring walk-ins and online check-ins.
Understand which campaigns drive inquiries.
See which campaigns bring quote requests and calls.
Connect campaigns to appointment inquiries.
See which campaigns bring trials, subscriptions and orders.