Google Ads hears about every finished TrackDrive call. Your buyers only paid for some of them.
TrackDrive's own setup guide says a call doesn't have to be marked converted to reach Google Ads, and a call with no revenue goes up at $0. Leave that call action as your bidding goal and a Medicare or debt relief campaign chases short hang-ups as hard as the calls a buyer accepted. We keep the gclid alive through your landing page and lead flow, put buyer revenue on a purchase action Google bids on, and add Meta, which TrackDrive doesn't document a connection for.
Free30 minutesNo obligation
TrackDrive · what breaks
What goes wrong with TrackDrive and your ads
- 01
"Google Ads counts calls our buyers never paid for"
Any finished call on a mapped offer with a gclid can upload, converted or not. If that call action is primary, Maximize Conversions counts a caller who hung up before the buyer said a word the same as a Medicare call your buyer paid for, and goes looking for more of them.
- 02
"The call log keeps saying the click ID token is blank"
TrackDrive's integration doesn't capture the gclid. A static number, a ring pool too small for your traffic, or a form that drops the parameter keeps real ad calls from Google, so your best keywords look like losers.
- 03
"Meta has no idea which ads make the phone ring"
TrackDrive's help center documents no Meta Pixel or Conversions API connection. So a timeshare exit or debt settlement campaign on Facebook optimizes for cheap clicks while the paying calls stay invisible to it.
- 04
"The buyer returned the call. Google kept the revenue."
When a call's revenue drops to zero, TrackDrive sends nothing and Google keeps the value it already has. Returned mass tort or insurance calls keep inflating your return on ad spend.
TrackDrive · the fix
What changes once TrackDrive is fixed
Bidding trained on billable calls
Revenue lands on a purchase action set as primary, while the per-call action stays secondary, so Google bids toward the callers your buyers actually pay for.
Every ad call carries its click
The ring pool and lead posts hold the gclid, the pool is sized for your concurrent visitors, and the token is confirmed on real call records instead of assumed.
Meta finally sees converted calls
TrackDrive's call-converted webhook feeds a first-party server container that sends Meta the calls Google gets, with a shared event ID so nothing counts twice.
TrackDrive · architecture
What TrackDrive actually lets you hook into
Everything here comes from TrackDrive's help center. Where the docs are silent, we list it as a check.
- 1
Native Google Ads integration
One Google sign-in, a client account (not a manager account), and a row per offer mapping a click ID token, gclid by default, to a conversion action and an optional purchase action. Calls go up three hours later, dated at their end time, in USD.
- 2
Upload status in the call log
About 30 minutes after submitting, TrackDrive records whether Google accepted, rejected or already had the conversion, and flags it if still unconfirmed at 48 hours.
- 3
Ring pools via trackdrive-optimizer.js
Collects query string parameters like gclid and utm_source and stamps them on the call. Number Limit and Token Hold Time decide whether busy hours reuse numbers.
- 4
Lead capture API
Extra keys on a lead posted to /api/v1/leads/capture are stored as lead tokens. We confirm a gclid posted this way reaches the call.
- 5
Outgoing webhooks and offer postbacks
Triggers fire when a call converts, when a lead is created, or around the call, with token substitution. This is the hook for Meta's Conversions API.
- 6
Not documented
No Meta connection, and the technical guide mentions only gclid, never gbraid or wbraid. Both gaps are checked on your account.
TrackDrive · diagnose
Where TrackDrive tracking breaks, in diagnostic order
Start with what Google is bidding on, because on TrackDrive the commonest fault is counting too much, not too little.
- 01
Check which TrackDrive action is primary in Google Ads
The per-call action, the purchase action, or Google's own call conversions running beside them.
- 02
Read a week of call log skip reasons
Blank click ID tokens point upstream at the page or lead flow.
- 03
Click a test ad and call the ring pool number
Open the call record and confirm the gclid and UTMs are on it.
- 04
Compare pool size with peak concurrent visitors
Reused numbers hand one visitor's click to another caller.
- 05
Look for returned calls Google still values
Revenue that went to zero in TrackDrive but never left Google.
TrackDrive · prove
The QA evidence on a live TrackDrive call
Run on a real call to a live ring pool number from an ad-tagged URL, routed to a real buyer, not a test target.
Source of truth
TrackDrive call records: buyer conversion, revenue and tokens (gclid, UTMs, traffic source) per call, plus the Google Ads upload notes in each call log
- One call from an ad-tagged URL with the gclid confirmed on the TrackDrive call record.
- The call log showing the upload accepted by Google, not skipped or unconfirmed.
- A buyer-converted call landing on the purchase action with its revenue, and a $0 call adding nothing to bidding.
- Exactly one Meta Purchase per converted call, with a shared event ID.
- A returned call corrected in Google Ads.
- Buyer-converted calls reconciled record by record across a closed window, then again 30 days later.
TrackDrive · free audit
What we check in the free audit
- Check which TrackDrive action is primary in Google Ads
- Read a week of call log skip reasons
- Click a test ad and call the ring pool number
- Compare pool size with peak concurrent visitors
- Look for returned calls Google still values
Checked against
TrackDrive call records: buyer conversion, revenue and tokens (gclid, UTMs, traffic source) per call, plus the Google Ads upload notes in each call log
Free30 minutesNo obligation
TrackDrive · when not to buy
When you don't need this on TrackDrive
Plenty of TrackDrive accounts are fine as they are, and we'll say so.
- If you only buy calls from publishers and run no Google or Meta ads yourself, TrackDrive's traffic source reporting is already the record that matters.
- If your Google traffic is call ads that ring you without a landing page visit, trackdrive-optimizer.js never runs, so there's no gclid for TrackDrive to send and Google's own call reporting is where we'd start.
- If the call log shows uploads confirmed with click IDs and you only need a purchase tracker added, that's a settings change you can make yourself.
TrackDrive · what we deliver
The event map on TrackDrive
Ring pool session
trackdrive-optimizer.js assigns a number and stamps gclid, UTMs and referrer onto the visitor's session. Diagnostic only.
Web lead posted
Form leads posted to TrackDrive's lead capture endpoint with the gclid as a lead token, so leads TrackDrive texts or dials keep their source. Carry-over to the call is tested.
Inbound call
Reporting only. Off-hook buyer calls are already skipped by TrackDrive, and calls without a click ID stay out.
Buyer conversion
The qualified signal: a duration rule or a buyer postback fires. Uploaded to the call action as secondary, for observation.
Revenue on the call
The bidding conversion: revenue above zero goes to the purchase action in Google and as a Purchase event to Meta.
Revenue changed or returned
Increases are resent by TrackDrive as an update to the same purchase. Drops to zero are logged and corrected by hand in Google Ads.
Written guarantee
95%+ tracking accuracy
Measured against TrackDrive call records: buyer conversion, revenue and tokens (gclid, UTMs, traffic source) per call, plus the Google Ads upload notes in each call log. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
TrackDrive questions, answered
Yes. The native integration, available on every account, uploads finished calls carrying a gclid on offers you've mapped to a conversion action in a Google Ads client account, with call revenue as the value.
TrackDrive's setup guide says a call doesn't need to be marked converted to upload, and calls without revenue go up at $0. If that call action is primary, every one counts; making the purchase action primary fixes it.
Its help center documents no Meta connection. We send converted calls to Meta's Conversions API from TrackDrive's call-converted webhook through a server container you own.
Because TrackDrive doesn't capture the gclid itself. It has to arrive through the ring pool script on the landing page or with the lead post; a static number on the page carries nothing.
If revenue is raised, TrackDrive resends it as an update to the same purchase. If it drops to zero, nothing is sent and Google keeps the old value, so that correction is made in Google Ads.
More on TrackDrive
- 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 TrackDrive, and what their bookings feed
- LiineLiine shows which ads book patients. Your ad accounts still bid on calls.
- CallRevuCallRevu shows which calls set a showroom appointment. Your Google Ads still counts the service lane.
- 800responseYour 1-800 number rings all day. Google Ads can't tell which calls it paid for.
- Patient PrismPatient Prism says who booked. Your Google Ads still pays for every caller.
- RingbaRingba knows which calls your buyers paid for. Google Ads is still counting the ones they rejected.
- CallSourceCallSource knows which calls booked an estimate. Your Google Ads doesn't.
- RetreaverGoogle Ads counts every Retreaver call. Only the converted ones pay you.
- WhatConvertsGoogle Ads is counting every WhatConverts call, hang-ups and all. It should only learn from the leads you'd quote.
Free · 30 min
See what Google Ads is learning from your TrackDrive calls
Free30 minutesNo obligation
