How to Track Chatbot Conversions in Google Ads, GA4 and Meta When the Booking Is the Win

Why "chat started" is the most expensive conversion you can count

Ad platforms learn from what you call a conversion. Tell Google Ads or Meta that an opened chat window is a win, and the system goes looking for more people who open chat windows: the curious, the bored, the competitor checking your prices. The reports look wonderful. The calendar does not change.

• Widget opened measures curiosity. Useful in a funnel, useless as a goal.
• First message sent measures engagement, including the visitor who asked whether you are hiring.
• Contact captured is closer, but a phone number is a lead to chase, not an appointment.
• Booking made is the event a business owner would pay for. It is the only one Kairos treats as the conversion, and the only one its ad platform sync, now rolling out to Growth and Pro plans, will send.

The earlier steps still matter for diagnosis, and the Clio dashboard shows each of them as a funnel. They just should not be what your bidding chases. This page covers how the booking carries its source all the way back. The Kairos overview explains the widget itself, and our conversion tracking setup service covers tracking beyond chat.

Keeping the ad click attached from the landing page to the booking

Attribution breaks in the gap between the page view and the booking. The visitor lands with tags in the address bar, reads two pages, opens the chat on a third, and books. If nothing caught those tags on arrival, the booking shows up as "direct" and the ad that paid for it gets no credit. Kairos records them when the visit starts and keeps them with the conversation.

Google's GA4 guidance on UTM parameters recommends always setting utm_source, utm_medium and utm_campaign, and warns that missing ones show up as "(not set)". Write them consistently. "Facebook", "facebook" and "fb" are three sources to a report and one to you.

One booking, written down: what the record should hold

Before any data goes to an ad platform, the booking needs to exist as a clean record in one place. Clio, the record-keeping agent in Athena, holds that record for every Kairos widget, and the analytics dashboard page shows how the metrics roll up. Here is what a single booking looks like underneath. The values are invented for illustration.

Clio keeps this record on every plan today, and you can export it as CSV. Late bookings like this one are common enough to have their own after-hours guide. The booking time carries an offset because Google requires it, as the next section explains. The contact data is sent only in hashed form to ad platforms and only for the purpose your privacy policy describes. We are not lawyers; your counsel decides the privacy wording.

Sending bookings to Google Ads after the June 2026 change

Google's model is simple to describe. Google Ads assigns a Google Click ID to every ad click. For offline conversions, Google's help center says you store the GCLID with the lead and "you give that GCLID back to Google Ads along with a few details" when the lead converts. A booking made in a chat is exactly that kind of conversion, as described in Google's article on offline conversion import.

Google calls enhanced conversions for leads "an upgraded version of offline conversion import that uses user-provided data", meaning hashed email and phone, and still advises including GCLIDs whenever possible. The plumbing changed in 2026. Google says that starting June 15, 2026, offline conversion import and enhanced conversions for leads uploads migrate to the Data Manager API and are blocked in the Google Ads API, and its developer docs say upload requests fail if the developer token had not sent requests before that date.

Field-service platforms handle this their own way. ServiceTitan's Marketing Pro sends its own conversion actions to Google, covered in our ServiceTitan Google Ads tracking guide; the Housecall Pro and Jobber sources we checked list no Google Ads conversion integration, which is why the Jobber attribution guide and the Housecall Pro attribution guide matter. Once Kairos booking into those platforms is live (it is rolling out), pick one system to report each booking to Google so it is not counted twice.

GA4: the booking as a key event, sent from the server

Google defines a key event as "an event that measures an action that's particularly important to the success of your business." A booking qualifies. In GA4 you create or identify the event, then mark it as a key event. Google's help also says key events can be used to create Google Ads conversions, which is handy and also the classic way to count one booking twice.

Because a booking is confirmed on the server, the clean way to record it is Google's Measurement Protocol. Google says its intent is "to augment automatic collection" through the tag, not replace it, and that events are joined with the visit through the client ID, which "should match the ID generated by the Google Analytics tag on your website." Events can be backdated up to 72 hours. That is why the widget is built to read the client ID when the chat opens.

• Use the same event name for every booking, and put the booking type in a parameter, not the name.
• Choose one path for Google Ads credit: the direct upload with the GCLID, or the GA4 key event imported into Ads. Not both.
• Keep the browser-side "chat opened" event as an ordinary event for funnel analysis, never a key event.

Meta: the Conversions API and the fbc value

Sending bookings to Meta, for clients who run Meta ads, is part of the sync rolling out to Growth and Pro plans. Meta describes its Conversions API as a connection from an advertiser's server, website platform, mobile app or CRM to Meta systems. Meta's documentation says the fbc value takes the form version.subdomainIndex.creationTime followed by the fbclid from the page URL, and that the click ID is case sensitive, so it is stored exactly as it arrived.

If the site also runs the Meta Pixel, the two must not double count. Meta's deduplication rules match a Pixel event and a server event when both the event ID and the event name agree, and only within 48 hours. Clio gives each booking one ID, and the sync is designed to reuse it for every destination. The ServiceTitan section has a separate Meta ads guide for contractors already sending job events from ServiceTitan.

The order we set it up in, and what you will see afterward

1. 1

   Agree on the conversion

   A booked appointment, by booking type. Opens and contacts stay in Clio as funnel steps, not goals.

2. 2

   Tag every paid and social link

   Consistent utm_source, utm_medium and utm_campaign values; Google Ads set up so the click ID reaches the landing page.

3. 3

   Capture identifiers on arrival

   The widget stores tags, click IDs, the GA4 client ID and the landing page when the visit starts, before any chat.

4. 4

   Create the destinations

   An offline conversion action in Google Ads, a key event in GA4, and a Conversions API dataset in Meta where you run Meta ads. You approve access in your own accounts.

5. 5

   Send test bookings and check each platform

   One test booking per source, followed into Google Ads, GA4 and Meta's Events Manager, then removed or excluded.

6. 6

   Compare totals every week

   Bookings in Clio against conversions reported in each platform. A gap that grows is a broken link, not a mystery.

Every Kairos build includes conversion tracking setup, and Clio's record of bookings by page, source, campaign and click ID is available on every plan now. Automatic conversion sync to Google Ads, GA4 and Meta is rolling out to Growth and Pro plans and is not live yet; until it arrives, every booking and its click ID sit in Clio and its CSV export, so nothing collected now is lost. Plan details are on the Kairos pricing page. If your ads need attention as well, see PPC advertising and our Google Ads library. Running a trade business? The home services page shows how bookings are triaged before they ever count.