Birdeye Webchat fills your Inbox with patient leads. Your ad accounts count chat opens, or nothing.
Birdeye Webchat collects contact details before the chat starts, then keeps the conversation going by text once the visitor leaves your site. Its Google Analytics switch still offers a Universal Analytics method, and the actions it reports describe the chat window, not the lead. We wire Birdeye's data layer and Inbox into Google Ads and Meta so bidding learns from chats that became booked patients and paid jobs.
Free30 minutesNo obligation
Birdeye Webchat · what breaks
What goes wrong with Birdeye Webchat and paid ads
- 01
Google Ads says the chat widget produced almost nothing
Birdeye's Google Analytics setting offers a 'Universal Analytics' method. Universal Analytics stopped processing hits in July 2023, so a widget left on it reports to a dead property and Smart Bidding never sees a chat lead.
- 02
Every chat bubble that pops open counts as a lead
Birdeye's Google Analytics integration reports six actions: Open, Send, Close, Send another message, Receive and Timeout. Birdeye says Open counts the window opening automatically or manually, so importing it has your dermatology or vein clinic campaigns paying for visitors who closed the bubble.
- 03
The lead books by text, and the ad gets no credit
After the visitor leaves, the thread continues as SMS, and Birdeye's conversation records label each message by channel, LIVE_CHAT or SMS. A consult booked three texts later looks like a texting win, not a paid search win, unless someone ties it back to the chat that started it.
- 04
Meta never learns which chats became patients
We found no Meta Pixel or Conversions API setting in Birdeye's webchat docs. Facebook and Instagram campaigns for your LASIK center or OB-GYN practice optimize on page views while the real outcomes sit in Birdeye Contacts under the green fire icon.
Birdeye Webchat · the fix
What changes after we fix it — Birdeye Webchat
One conversion per real chat lead
Built on Birdeye's Send action, counted once per visitor and checked against the new lead in Birdeye Contacts.
Bidding learns from booked and paid outcomes
Birdeye's conversation.created webhook tells us a new chat thread exists. We match it to the new lead in Contacts and the click captured on your site, then send booked and paid outcomes to Google Ads as offline conversions and to Meta server-side.
Each location gets its own numbers
Multi-location widgets make visitors pick a location before chatting, and Birdeye records that location on the lead, so we carry it onto each conversion and budget follows the clinics or showrooms that convert.
Birdeye Webchat · architecture
What Birdeye Webchat actually lets you hook into
Everything here comes from Birdeye's help center and API docs. Where the docs stop, we test on your widget.
- 1
Google Analytics setting per widget
Under Settings > Inbox > Chatbot AI, with a 'Universal Analytics' or 'Google Site Tag' method. Birdeye says the Inbox then shows the page each chat started on.
- 2
Data layer events for Google Tag Manager
A webchatCTATracking event with sectionName, actionName and actionValue. Birdeye's guide maps it to GA4 events birdeye_webchat_all_actions and birdeye_webchat_send.
- 3
Webhook subscriptions
conversation.created, conversation.updated, message.added and conversation.closed. Failed deliveries are retried with the same eventId, so the receiver has to de-duplicate.
- 4
Lead and conversation exports
The API lists contacts by type and source, webchat included, and exports threads with the channel on each message.
- 5
No direct ad platform connection
No Google Ads conversion, Meta Pixel, Conversions API or Zapier setup in Birdeye's webchat docs. API calls need a Birdeye-issued key, so confirm your plan includes one.
Birdeye Webchat · diagnose
Where Birdeye Webchat tracking breaks, in the order we check
Start inside the widget settings: the commonest fault is a Google Analytics option still set to Universal Analytics.
- 01
Check each widget's tracking method and ID
A UA-style ID or the 'Universal Analytics' option means the chat events land nowhere useful.
- 02
Find which Birdeye action is imported as the conversion
Open, Receive or the all-actions event inflate lead counts. Send is the closest browser signal to a real lead.
- 03
Start a test chat from an ad-tagged URL
Confirm the GCLID survives to the first message, and whether Send fires before or after the visitor enters contact details.
- 04
Compare Birdeye leads with reported conversions
Lead by lead, by day and location, over a closed week.
- 05
Trace text follow-ups back to the web chat
When the booking happened by SMS, make sure it still credits the original chat and the ad behind it.
Birdeye Webchat · prove
The QA evidence — Birdeye Webchat
Run on the live widget on your site, with a real chat started from a tagged ad URL, not in GTM preview alone.
Source of truth
Birdeye Contacts and Inbox: leads with source Webchat by date and location, and the conversation threads behind them
- One test chat from an ad-tagged URL, with the click ID stored at the first message.
- Exactly one Send-based conversion for that chat, even after several messages.
- The matching lead in Birdeye Contacts under source Webchat, at the right location.
- Each webhook eventId processed once, retries ignored.
- A booking made by text credited to the original chat.
- Webchat leads reconciled one by one against Google Ads and Meta over a closed window.
- Repeated 30 days later and after any widget or GTM change.
Birdeye Webchat · free audit
What we check in the free audit
- Check each widget's tracking method and ID
- Find which Birdeye action is imported as the conversion
- Start a test chat from an ad-tagged URL
- Compare Birdeye leads with reported conversions
- Trace text follow-ups back to the web chat
Checked against
Birdeye Contacts and Inbox: leads with source Webchat by date and location, and the conversation threads behind them
Free30 minutesNo obligation
Birdeye Webchat · when not to buy
When you don't need this on Birdeye Webchat
Plenty of Birdeye accounts are better served by a quick settings fix.
- If you don't run paid ads, Birdeye's chat reporting by location and user already tells you what you need.
- If most chats come from existing patients asking about appointments or billing, the widget is a service tool, and feeding it to ad bidding would mislead it.
- If the only fault is a widget still set to Universal Analytics, following Birdeye's own GTM guide to GA4 may be enough, and we'll tell you to do it yourself.
- If chat brings in a handful of leads a month next to hundreds of phone calls, fix call tracking first. That's where your ad money is decided.
Birdeye Webchat · what we deliver
The event map on Birdeye Webchat
Chat window opened
Birdeye's Open action, kept in GA4 to judge the widget and never used for bidding.
First message sent
The Send action, fired once per visitor with landing page, GCLID and UTMs attached.
Birdeye lead created
A new contact with lead source Webchat, matched to the conversation.created webhook. Existing customers are flagged, since Birdeye creates no new lead for them.
Qualified chat
Right location, real service request, working phone or email. Job seekers and vendors drop out.
Consult or estimate booked
From the Inbox thread, including ones finished by text.
Paid job or attended visit
The money conversion. Message text and health details stay out of every ad platform.
Written guarantee
95%+ tracking accuracy
Measured against Birdeye Contacts and Inbox: leads with source Webchat by date and location, and the conversation threads behind them. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Birdeye Webchat questions, answered
Partly. The widget's own setting still lists a Universal Analytics method, but Birdeye also pushes data layer events that its guide sends to GA4 through Google Tag Manager. Build on the GTM route.
Send, counted once per visitor, is the closest browser event to a lead. Better still is the booked or paid outcome sent back from Birdeye with the click ID.
Not natively, as far as Birdeye's docs show. We use its webhook to catch new chat leads and send outcomes to Meta server-side, sharing an event ID with any browser event.
Birdeye continues the thread by SMS after the visitor leaves, and its records label each message LIVE_CHAT or SMS. We tie the ad click to the chat message that opened the thread, so the text follow-up doesn't steal the credit.
The conversion name, time, value and click ID, plus hashed contact details only where your consent setup allows it. Message text, symptoms and treatment names stay in Birdeye.
This page covers the chat widget. If chats hand visitors to Birdeye Appointments, we confirm whether the booking keeps the chat's click ID. The standalone Birdeye Appointments widget has its own guide on our site.
More on Birdeye Webchat
- Birdeye AppointmentsConversion tracking for Birdeye Appointments
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
RELATED GUIDES
Booking tools beside Birdeye Webchat, and what their bookings feed
- GuildQualityGuildQuality surveys every finished project. Your ads never hear about one.
- Press GaneyPress Ganey makes your ratings look great. Your ads still can't tell which patients they brought in.
- GatherUpYour ads count form fills. GatherUp already knows who actually paid.
- PodiumYour Podium inbox is full. Your ads can't tell which chats paid.
- Facebook Messenger / Instagram DirectMessenger and Instagram DM tracking that counts customers, not chats
- ReputationReputation says your location pages drive calls and bookings. Your ads can't tell which ones they paid for.
- rater8rater8 proves your reviews are growing. Nothing proves which ads brought the patients.
- BroadlyBroadly fills your inbox. Your ad accounts still can't tell which clicks did it.
Free · 30 min
Get Birdeye Webchat counting real leads
WhatsAppFree30 minutesNo obligation
