Intaker shows you every chat. Your ads can't tell which ones signed.
Your Intaker dashboard fills with chats, but Google Ads can't tell a signed injury case from someone who opened the bubble and left. Intaker's GA4 integration sends 11 events, from WidgetOpen to ClickToCall, and importing the wrong ones teaches Smart Bidding to buy taps. We count one lead per captured phone number and send retained cases back to Google and Meta, matched to the ad click.
Free30 minutesNo obligation
Intaker · what breaks
What goes wrong with Intaker and paid ads
- 01
Google Ads counts curiosity as leads
Intaker's GA4 integration sends WidgetOpen, startConversation and ClickToCall alongside PhoneCaptured, and ClickToCall records a tap on the call button, not a connected call. Import those as primary and Smart Bidding buys bubble-tappers, so cost per signed case climbs while the conversion column looks great.
- 02
The signed case never reaches the ad account
Intaker hands the contact and transcript to Clio Grow, Lawmatics or Filevine, where the retainer gets recorded. Google and Meta only see the chat, so a price-shopper and a serious injury case count the same and budget keeps flowing to keywords that never sign.
- 03
Meta sees chats only if someone pasted the listener
Intaker's Pixel guide is browser code you paste in yourself, calling trackCustom with no event ID. Ad blockers drop part of it, so Meta optimizes on a partial count, and adding the Conversions API later double counts every chat.
- 04
LSA and text leads blur into website chats
LSA Responder leads, texts to the Intaker number on your Google Business Profile and Facebook, Instagram or WhatsApp messages all land in the same dashboard. None came from a website ad click, yet they inflate Search's numbers and hide what LSA really delivers.
Intaker · the fix
What changes — Intaker
Bidding learns from retained clients
Signed matters go to Google Ads as offline conversions on the stored GCLID, and to Meta server-side, so personal injury, criminal defense and family law budgets drift toward searches that become cases.
One lead per person, not per widget event
Phone captured and callback requested count once per chat, and Pixel and Conversions API send the same event ID so Meta keeps one. Widget opens and pop-up answers stay in reporting only.
Every Intaker lead has an honest source
Website chats carry their ad click; LSA, profile texts and social messages are tagged by channel, so the Intaker leads list and each ad platform agree over a closed month.
Intaker · architecture
What Intaker actually lets you hook into
From Intaker's help center. Anything it doesn't document is listed as something we confirm on your account.
- 1
A widget that talks to your page
Intaker installs as one snippet in your site's body or a WordPress plugin, and posts events to the page tagged INTAKER_CHAT_WIDGET, such as chatStarted, phoneCaptured and CallBackRequest. A page-level listener turns them into tag events.
- 2
GA4 integration with a Measurement Protocol secret
You paste a Measurement ID and API secret into Intaker and it reports 11 labeled events. Google joins these to a visit by client ID, so we check they land in the ad session.
- 3
Chat tracking info on every lead
Current, landing and referring URL plus parsed UTMs are saved on the transcript. A GCLID field isn't documented, so we test it or capture it ourselves.
- 4
Zapier triggers
Lead Status Changed, New Chat, New Callback Request, New Call Now and New LSA Lead Received. The status trigger is how a qualified lead leaves Intaker.
- 5
Case management connections
Documented integrations with Clio Grow, Clio Manage, Lawmatics, Filevine, MyCase, Lead Docket and more. Lawmatics, for one, receives every new contact and chat transcript.
- 6
No ad platform sending
No documented Google Ads conversion connection or Meta Conversions API. Server-side delivery comes from your own container.
Intaker · diagnose
Where Intaker tracking breaks, in diagnostic order
Start in Google Ads, because on Intaker sites the costliest fault is usually the wrong event marked primary.
- 01
Check which Intaker events are primary conversions
WidgetOpen, startConversation, PopupYes or ClickToCall should never steer bidding.
- 02
Count what fires on one test chat
Intaker's GA4 integration, a GTM listener and the Pixel snippet can report one phone number three ways.
- 03
Chat from a URL carrying a test GCLID
Then open the lead's tracking info and the record it created in your CRM.
- 04
Find Intaker's events in GA4 traffic reports
Under direct or unassigned means the hits aren't joining the ad visit.
- 05
Follow a signed case back
Confirm the click ID and Intaker lead ID survive until the matter is marked retained.
- 06
Separate the non-website channels
LSA, profile texts and Facebook, Instagram or WhatsApp messages tagged before they touch a Search report.
Intaker · prove
The QA evidence — Intaker
Run on real chats through the Intaker widget on your live site, from ad-tagged URLs, not from the dashboard's bot preview.
Source of truth
Intaker leads list and chat tracking info, plus retained matters in your case management system
- A test chat opened from a URL carrying UTMs and a test click ID, with both confirmed on the Intaker lead and the CRM record.
- One lead conversion per captured phone number in Google Ads, GA4 and Meta, with Pixel and Conversions API sharing an event ID.
- A ClickToCall tap confirmed absent from call conversions unless the call connected.
- An LSA Responder lead and a profile text confirmed absent from Search conversions.
- Retained matters matched lead by lead to Google Ads offline conversions over a closed window.
- Rerun 30 days on, and again whenever someone edits the Intaker bot flow.
Intaker · free audit
What we check in the free audit
- Check which Intaker events are primary conversions
- Count what fires on one test chat
- Chat from a URL carrying a test GCLID
- Find Intaker's events in GA4 traffic reports
- Follow a signed case back
- Separate the non-website channels
Checked against
Intaker leads list and chat tracking info, plus retained matters in your case management system
Free30 minutesNo obligation
Intaker · when not to buy
When an Intaker firm can skip us
Some firms on Intaker are better off with a short settings fix.
- If most Intaker leads come from the LSA Responder, Google's LSA lead reporting matters more than website tracking.
- If you run one small Search campaign and PhoneCaptured, imported from GA4, already matches your Intaker leads list, leave it.
- If chat signs only a few cases a month, bidding can't learn from retainers yet; get lead counts right first.
- If the only fault is ClickToCall marked primary, switching it to secondary in Google Ads takes five minutes, and we'll say so on the call.
Intaker · what we deliver
The event map on Intaker
Chat started on your site
From Intaker's chatStarted message, with UTMs and GCLID stored on the lead. Reporting only, never the bidding target.
Phone or email captured
The lead conversion, once per chat with an event ID. A reset chat capturing the same number doesn't count twice.
Callback requested or call tapped
CallBackRequest counts as a lead. ClickToCall is a tap, and counts as a call only if your call tracking confirms it connected.
Qualified by intake
From Intaker's Lead Status Changed trigger, when intake moves the lead to your viable-case status.
Retained client
The signed matter in Clio Grow, Lawmatics or your CRM, sent to Google Ads and Meta with its fee value if you share one.
Excluded from ad conversions
Widget opens, pop-up answers, LSA Responder leads, profile texts and Facebook, Instagram or WhatsApp messages, kept for channel reporting.
Written guarantee
95%+ tracking accuracy
Measured against Intaker leads list and chat tracking info, plus retained matters in your case management system. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Intaker questions, answered
Not that its help center documents. It offers GA4 and Zapier, so Google Ads conversions come from GA4 imports or tags on Intaker's widget events, and signed cases return as offline conversions.
A retained client for bidding, with PhoneCaptured or CallBackRequest as the lead signal. Intaker suggests ClickToCall too, but it fires on the tap, so we treat it as a call only when the call connects.
Its help center only documents a browser Pixel listener that calls trackCustom. Server-side events with a matching event ID come from your own first-party container.
Yes, the chat tracking info shows UTMs plus landing, referring and current URL. A GCLID field isn't documented, so we test it on a live chat.
Separately. They start in Google's Local Services messaging, not your website, so they belong in LSA reporting; Intaker's New LSA Lead Received trigger lets us tag them.
More on Intaker
- 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…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside Intaker, and what their bookings feed
- GavelYour Gavel bundles sell. Google Ads says they don't.
- Assembly NeosNeos shows which intakes became cases. Google Ads never finds out.
- Lead DocketLead Docket shows which sources sign cases. Your ad accounts still don't.
- LawmaticsLawmatics knows which leads hired you. Your ads don't.
- Case StatusYour clients love Case Status. Your ads still can't tell who signed.
- SmartAdvocateSmartAdvocate shows which intakes signed. Google Ads never hears about it.
- LitifyLitify knows which callers signed. Your ads don't.
- Law RulerLaw Ruler shows who signed. Your ad accounts still think every intake won.
Free · 30 min
Find out which Intaker chats your ads actually paid for
WhatsAppFree30 minutesNo obligation
