CallTrackingMetrics says every call is a lead. Your crew knows better.
You pay for CallTrackingMetrics to learn which ads make the phone ring, yet Google Ads counts robocalls, quick hang-ups and existing customers as conversions while Meta sees almost nothing. That's rarely CTM failing. It's Direct Connect lead rules firing on every activity, a number pool sized for last year's traffic, and a Meta dataset still waiting on CTM's partner approval. Fixed means Google and Meta learn from scored calls and paid jobs, each counted once and matched to the click.
Free30 minutesNo obligation
CallTrackingMetrics · what breaks
What goes wrong with CallTrackingMetrics
- 01
"Google Ads shows a pile of leads and we booked a handful"
CTM's global lead rules fire the moment any call, text or form ends, and its Direct Connect trigger preset is literally named All Activities. Unless something filters first, Smart Bidding treats a wrong number like a roof replacement and buys more of them.
- 02
"Our conversions doubled the week we added a trigger"
CTM's own docs recommend lead and sale rules or a Direct Connect trigger, not both. Run both, or keep Google's own call conversions primary beside CTM's upload, and one call can count twice.
- 03
"Our north office's calls show up under the south office's campaigns"
An undersized number pool makes visitors share numbers and drags likelihood scores down. Linking a manager account and its child accounts together can send conversions to the wrong account.
- 04
"Meta gets calls with no value, or nothing at all"
The Facebook integration stays incomplete until CTM approves its partner request on your dataset. After that, the default trigger sends every activity as a Lead valued at {{sale.value}}, empty unless someone scores the call.
CallTrackingMetrics · the fix
What changes — CallTrackingMetrics
Google bids toward calls that become jobs
Lead conversions only for calls passing your duration and tag rules; sale conversions carry the amount your team enters when scoring.
One call, one conversion, one account
A single sending path per platform and the right Google Ads account mapped to each office.
Meta and GA4 match your call log
An approved Meta dataset fed scored calls with values, and GA4 call events with duplicate prevention on.
CallTrackingMetrics · architecture
What CallTrackingMetrics actually lets you hook into
Every hook below comes from CTM's own help center, and each has a setting that decides whether it helps or hurts.
- 1
Google Ads Direct Connect
Uploads conversions for activities with a GCLID, GBRAID or WBRAID through global rules or per-account triggers, and sends enhanced conversions for leads once they're turned on in the Google Ads account.
- 2
Google Call Analytics for call assets
With call reporting on and CTM as the analytics provider, Google's forwarding number sits over CTM's so both see the call.
- 3
Facebook Conversions API dataset
An offline dataset with CTM approved as partner, fed by triggers you can filter by duration or source.
- 4
GA4 Measurement Protocol
Web data streams only, with offline-source calls, first-time versus repeat caller labels and a duplicate-event block.
- 5
Webhooks, Zapier and GTM
Webhooks fire at set phases, including sale and PPC data updates. Zapier reaches CRMs without a connector. A GTM integration publishes the DNI tag.
CallTrackingMetrics · diagnose
Where CallTrackingMetrics tracking breaks, in diagnostic order
We start with what gets sent, because on CTM accounts the costliest fault is junk reaching Smart Bidding, not calls going missing.
- 01
Read the lead rule and trigger conditions
No duration floor or tag filter means every hang-up is a conversion.
- 02
Count the paths sending one call
Global rules, triggers and Google's native call conversions, each checked for primary status.
- 03
Check DNI scripts on the page
A leftover CallRail tag, Google's forwarding-number snippet, or the WordPress plugin plus GTM all fight CTM's swap.
- 04
Run the accuracy report
CTM suggests one number per 20 daily visitors per source and wants likelihood scores of 90% or better. Lower scores usually mean too many visitors share each number.
- 05
Open the Direct Connect log and Meta dataset
Look for blank GCLIDs, rejected uploads and a partner request that was never approved.
CallTrackingMetrics · prove
The QA evidence — CallTrackingMetrics
Run on real calls to your live tracking numbers from ad-tagged sessions, not CTM's test-call button.
Source of truth
The CallTrackingMetrics activity log: calls, texts and forms by date with tracking source, likelihood score, reporting tags and scored conversion value
- A Google Ads call with its GCLID on the CTM activity and an accepted upload in the Direct Connect log.
- A short or spam-tagged call absent from every ad platform.
- A scored sale carrying its dollar value to Google and Meta.
- One GA4 event per activity.
- Each office's calls in its own mapped Google Ads account.
- Paid-source likelihood scores at 90% or above.
- The month reconciled again 30 days later and after any pool or site change.
CallTrackingMetrics · free audit
What we check in the free audit
- Read the lead rule and trigger conditions
- Count the paths sending one call
- Check DNI scripts on the page
- Run the accuracy report
- Open the Direct Connect log and Meta dataset
Checked against
The CallTrackingMetrics activity log: calls, texts and forms by date with tracking source, likelihood score, reporting tags and scored conversion value
Free30 minutesNo obligation
CallTrackingMetrics · when not to buy
When you don't need this on CallTrackingMetrics
Plenty of CTM accounts need an afternoon of settings, not a project.
- If you run Google Ads only and uploaded conversions already match your scored calls, leave it alone.
- If most calls come from directories, yard signs or referrals on static numbers, there's no click to match, and CTM's source reports already answer the question.
- If nobody in the office will tag or score calls, value-based bidding has nothing to learn from. Fix that habit first.
- If the only fault is a CallRail or other old DNI script loading beside CTM's, follow CTM's own advice: confirm CTM's swap works, remove the old script, and place one test call.
CallTrackingMetrics · what we deliver
The event map on CallTrackingMetrics
Activity logged
Call, text or FormReactor submission recorded with session, click ID and likelihood score. Not sent anywhere yet.
Qualified lead
Passes the duration floor and isn't tagged spam, vendor or existing customer. Sent to Google Ads, Microsoft Ads and Meta.
Estimate or consultation booked
A reporting tag your office applies, sent through a trigger as a custom conversion group. Key for long cycles like roofing, mold remediation or employment cases.
Job sold or retainer signed
The call scored as converted with a dollar amount, sent as the sale conversion with that value.
Call-asset and iOS calls
No GCLID, or GBRAID and WBRAID instead, routed to their own conversion actions.
Excluded on purpose
Blocked callers, existing customers, transfers and outbound calls never count as acquisition.
Written guarantee
95%+ tracking accuracy
Measured against The CallTrackingMetrics activity log: calls, texts and forms by date with tracking source, likelihood score, reporting tags and scored conversion value. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
CallTrackingMetrics questions, answered
CTM's lead rules send every completed activity unless you filter them. A duration floor and tag filters, or bidding on scored sale conversions, fixes it.
Not website calls: CTM's docs say Google only accepts conversions with a GCLID, GBRAID or WBRAID, so auto-tagging must be on. Call-asset calls go through Google Call Analytics with CTM as provider.
Yes, on CTM's Marketing Pro, Sales Engage, Enterprise, Growth and Connect plans, through an offline Meta dataset where CTM is an approved partner. We confirm which caller details reach it, since that decides how many calls Meta can match.
CTM recommends one per 20 daily visitors from a source, and its accuracy report shows whether you're there. A roofer's storm-season traffic may need a bigger pool than winter's.
Yes, through Direct Connect customer mapping. Connect the manager account or the individual accounts, not both.
One, never both. Rules are simpler across many accounts, triggers allow finer conditions, and both together can send a call twice.
More on CallTrackingMetrics
- CallTrackingMetrics → Google AdsConnecting CallTrackingMetrics to Google Ads
- CallTrackingMetrics → MetaConnecting CallTrackingMetrics to Meta Conversions API
- CallTrackingMetrics → GA4Connecting CallTrackingMetrics to GA4
RELATED GUIDES
Booking tools beside CallTrackingMetrics, and what their bookings feed
Free · 30 min
Find out what CallTrackingMetrics is really telling your ads
Free30 minutesNo obligation
