How to track Chili Piper bookings as conversions in Google Ads
If you run Google Ads and use Chili Piper to book sales meetings, the gap between the two is usually the same: Google knows someone clicked, Chili Piper knows someone booked, and nothing connects the two reliably. This guide walks through a server-side approach that captures the GCLID at booking time and sends the conversion back to Google Ads — either immediately or after the lead becomes a customer.
Why browser-based tracking falls short for Chili Piper
Standard conversion tracking — Google Tag Manager events, thank-you page visits, button click listeners — runs into three recurring problems:
- Ad blockers. The Google Tag may never load, so nothing the visitor does can be tracked.
- Browser privacy limits. Safari and similar browsers clear tracking cookies within roughly a day, so a click on Monday and a booking on Thursday cannot be connected.
- Device switching. A prospect who clicks on a phone and books on a laptop leaves two sessions that browser tracking cannot join.
Chili Piper makes this harder still: it does not send guests to a dedicated thank-you page after a booking, and its scheduler runs inside a widget on your page. A simple button click listener cannot reliably tell you a meeting was actually booked rather than a form abandoned.
Server-side tracking sidesteps all of this by sending the lead's details directly to Google's servers. Google's own published data has reported an average 23% increase in recorded conversions and a 10% reduction in cost per conversion when server-side tracking is used, largely because the bidding algorithms get enough signal to learn what a good customer looks like.
Choose when the conversion fires
There are two main ways to send a Chili Piper booking to Google Ads, and the right one depends on when you want the conversion reported.
Option 1 — fire when the meeting is booked. A visual workflow tool such as Converly can watch for new Chili Piper bookings, capture the GCLID, IP address and user agent, pull the guest's name, email and phone number, hash the personal data with SHA-256, and pass everything to Google Ads. That level of detail helps Google match the booking back to the exact campaign, ad and keyword. You get the benefits of server-side tracking without writing custom code or handling Google's API directly.
Option 2 — fire when the lead becomes a customer. If bookings flow into a CRM, you can capture the GCLID at booking time, store it on the contact record, and send the conversion later — for example when a deal is created or the lead becomes a paying customer. Zapier and Make are common choices for that final handoff because they connect to most CRMs.
Decision checklist:
- Do you close enough new customers each month to feed Google's bidding algorithms? If not, fire on booking.
- Do you need revenue-weighted bidding? If so, fire on closed-won and attach a value.
- Can your CRM store a custom field on the contact? If not, the closed-won route will lose the GCLID.
- Do you want the simplest setup? Fire on booking.
Capture the GCLID on the Chili Piper form
The GCLID is the unique identifier Google attaches to every ad click. To keep it, you need it stored somewhere the booking can carry forward.
- Install the tracking script on your site. Add the snippet provided by your attribution tool to your website. Trial length and plan terms are set by that provider, so check them before you commit.
- Add a hidden GCLID field to the Chili Piper form. Create a field for the GCLID, set it to hidden so guests never see it, and configure it to receive the value automatically rather than by manual entry.
- Let the script write the value. When a visitor arrives from a Google Ads click, the script stores the GCLID so it survives browsing and return visits. When the guest opens the Chili Piper widget and books, the stored value is written into the hidden field without the lead noticing.
- Send the data to your CRM. Chili Piper's native CRM integrations can pass the GCLID along with the guest's name, email, phone number and any other form answers. The value then sits on the contact record until you need it.
- Push the conversion to Google Ads. When the milestone you chose occurs, send the conversion with the stored GCLID and the lead details.
A note on conversion volume
Smart bidding in Google Ads — Maximise Conversions, Target CPA and similar strategies — learns from the conversions you feed it, and Google's documentation puts the working level at about 50 conversions per month per campaign. Meta's Advantage+ targeting has a comparable threshold of about 50 conversions per week per ad set.
That matters when you decide between the two timing options. Sending conversions only when a lead becomes a customer sounds cleaner, but most businesses close far fewer customers than they book meetings. If the closed-won volume is thin, the algorithms never get enough data. Firing on booking usually produces the volume needed to learn.
Four reasons server-side conversions hold up
1. Ad blockers stop mattering. Research cited in the source puts the share of internet users running some form of ad blocker above 30%. Server-side sending bypasses the browser entirely.
2. Safari and iOS privacy limits are bypassed. Apple's Intelligent Tracking Prevention clears tracking cookies within a day or two. Sending name, email and phone with each conversion gives Google another way to tie the booking back to the original click.
3. Cross-device journeys are joined. A prospect who discovers your site on a phone and books later on a laptop can still be credited, because the lead data travels with the conversion.
4. Duplicate and messy data is eliminated. A button click can be abandoned mid-form; a thank-you page can be visited without a submission, indexed by search engines, reached by autocomplete or hit by bots. Server-side tracking logs a conversion only when a meeting is genuinely booked.
Three reports worth running once the data flows
Conversions by keyword. Most advertisers bid across many keywords for different products or use cases — an accounting software company might bid on 'accounting software', 'invoicing software' and 'QuickBooks alternative' at once. This report shows which keywords actually produce booked meetings, so you can shift budget toward them and pause the rest.
Conversion value by campaign. When conversions come from your CRM, you can attach a value to each one, usually the deal value. You can then see that one campaign produced $1,000 in pipeline while another produced $10,000, and allocate budget accordingly.
Conversions by geography. This is especially useful for businesses that serve clients locally — financial advisors, accounting firms, law practices. Break conversions down by country, state, city or postcode to see whether meetings come from areas you can realistically serve. Location bid adjustments then let you bid harder where your best customers are and pull back elsewhere.
Getting the setup right
Accurate conversion tracking in Google Ads does two things: it gives you the data to make manual adjustments, such as bidding up on certain keywords or locations, and it gives the bidding algorithms the signal they need to find more people like your best customers.
Both depend on the underlying data being trustworthy. Thank-you page visits and browser-fired events are not reliable for a Chili Piper booking. Whichever timing you choose — on booking, on closed-won, or somewhere in between — send the conversion server-side.
Frequently asked questions
Why can't I just track a thank-you page after a Chili Piper booking?
Chili Piper does not send guests to a dedicated thank-you page after a booking, and its scheduler runs inside a widget on your page. A button click listener also cannot reliably distinguish a completed booking from an abandoned form.
What is the GCLID and why does it matter?
The GCLID is the unique identifier Google attaches to every ad click. Storing it at booking time is what lets you send the conversion back to Google Ads later and have it credited to the right click.
How many conversions does Google Ads smart bidding need?
Google's documentation puts the working level for smart bidding strategies such as Maximise Conversions or Target CPA at about 50 conversions per month per campaign. Meta's Advantage+ targeting has a comparable threshold of about 50 per week per ad set.
Should I fire the conversion on booking or on closed-won?
Fire on booking if your closed-won volume is too thin to feed the algorithms. Fire on closed-won if you need revenue-weighted bidding and your CRM can store the GCLID on the contact record.