How to reconcile X Ads against your call tracking records
This is the check we run first on every account, written out so you can run it without us. It takes about thirty minutes and needs two numbers: what X Ads says it produced, and what your call tracking records actually shows. The gap between them is the only honest measure of whether your tracking works — and if it comes back small, you do not need us.
Free30 minutesNo obligation
Specific to X Ads × Call Records
X Ads vs qualified calls: a thin signal on a moving API
Match X to qualified calls on the twclid your call tracking tool captures for the visitor's session, with the hashed caller phone in the X Conversions API as a backup key. Confirm the per-conversion window setting first. Expect X to show very few calls; a large X count against your call log points to a misdefined event.
X rarely drives phone calls. Most clicks come from people reading a timeline on a phone, who open your site briefly and go back. When one calls, the twclid from that visit is the click key, captured by your call tracking tool on landing and bound to the dynamic number shown. Send qualified calls through the Conversions API with the twclid and a hashed caller phone, and check the current API documentation before building, because it has changed often.
Attribution windows on X are set per conversion, so the call event can carry a different window from your site events without anyone noticing. Read the setting on the call conversion itself, and check whether view-through is included, since a timeline impression followed by a call from a search result can be credited to X.
Use the conversion columns in X Ads Manager for the call event, compared against qualified calls carrying an X source in your call tracking tool. Single digits against a busy call log is a normal result. The most common reason the two disagree is that the call conversion was set up on a click-to-call button, so X counts taps that never became a connected, qualified call.
X Ads × Call Records · what breaks
Why X Ads and your call tracking records disagree
- 01
Raw call volume counted as conversions
Wrong numbers, existing customers, suppliers and hang-ups all ring the same line. In some trades the call-to-job rate is under half.
- 02
Number pool too small
If tracking numbers recycle faster than your sales cycle, two prospects share one number and the attribution is simply wrong.
- 03
Dynamic number insertion failing on cached pages
A cached page serving a stale number sends a whole segment's calls into the wrong pool, silently.
- 04
Call answered but outcome never recorded
Without joining the call to the job or deal, you are measuring how often the phone rang rather than how often it earned.
X Ads × Call Records · the fix
What you get from this — X Ads × Call Records
A number instead of a suspicion
The likely cause, narrowed
A basis for deciding
X Ads × Call Records · architecture
What each side is actually counting — X Ads × Call Records
- 1
What X Ads counts
An event name X recognizes, a conversion identifier matched to the tag if you run one, a timestamp, hashed customer information, and the click identifier.
- 2
How X Ads attributes it
X appends twclid to your landing page URL. The platform's advertising stack has changed substantially and repeatedly, so treat any documentation older than a few months as unreliable and verify parameter names and endpoints directly before building.
- 3
The window it uses
X's attribution windows are configurable per conversion. Confirm the setting in your account before comparing any number, and verify the accepted event-freshness limit against current documentation.
- 4
What your call tracking records counts
Calls that were qualified and produced work, not calls received, found in CallRail, CallTrackingMetrics, Invoca or your phone system, joined to whatever records the outcome.
- 5
The filter that makes them comparable
Calls longer than your qualifying threshold, classified as genuine enquiries.
X Ads × Call Records · events
Reading the gap — X Ads × Call Records
| What you see | What it usually means |
|---|---|
| 15%+ platform higher | Usually the wrong event entirely — raw call volume is being counted rather than qualified calls, so wrong numbers and existing customers are in the figure. |
| 20%+ platform lower | Usually structural — number insertion is failing for some traffic, or calls are arriving on a number that is not tracked at all. |
X Ads × Call Records · diagnose
Diagnostic order — X Ads × Call Records
- 01
Confirm both numbers cover the same period and channel
- 02
Raw call volume counted as conversions
Wrong numbers, existing customers, suppliers and hang-ups all ring the same line. In some trades the call-to-job rate is under half.
- 03
Number pool too small
If tracking numbers recycle faster than your sales cycle, two prospects share one number and the attribution is simply wrong.
- 04
Dynamic number insertion failing on cached pages
A cached page serving a stale number sends a whole segment's calls into the wrong pool, silently.
- 05
Read the conversion reporting inside X Ads Manager, reconciled against your own records
The platform's ad products and APIs have been rebuilt repeatedly, which means integration guidance ages faster here than anywhere else in this library. Anything you build should be re-verified periodically rather than assumed stable.
X Ads × Call Records · prove
How to know you did it right — X Ads × Call Records
Source of truth
your call tracking records — qualified calls for a fully closed month
X Ads × Call Records · free audit
What we check in the free audit
- Confirm both numbers cover the same period and channel
- Raw call volume counted as conversions
- Number pool too small
- Dynamic number insertion failing on cached pages
- Read the conversion reporting inside X Ads Manager, reconciled against your own records
Checked against
your call tracking records — qualified calls for a fully closed month
Free30 minutesNo obligation
X Ads × Call Records · when not to buy
When the answer is that you do not need us — X Ads × Call Records
- If almost all of your qualified calls come from a channel with no click behind it, no tracking work will reach them — and knowing that is worth more than a build.
- If X is a small experimental line on your plan, the integration effort is hard to justify against a platform whose API has moved this often.
X Ads × Call Records · what we deliver
The method, step by step — X Ads × Call Records
Pull what X Ads reports
The conversion reporting inside x ads manager, reconciled against your own records.
Pull what your call tracking records shows
Export tracked calls for a closed month with duration and outcome, and join each to the job, appointment or deal it produced.
Filter both to the same thing
Calls longer than your qualifying threshold, classified as genuine enquiries.
Compare per record, not on totals
FAQ
X Ads × Call Records questions, answered
Only if it carries meaningful spend for a phone-led business. As an experimental line, the integration effort is hard to justify for so few calls.
Usually the conversion counts taps on a phone link, or view-through is on. Check both settings before suspecting your call tracking.
Because you should know the size of the problem before anyone quotes you for it. If the gap is small, you have saved yourself a purchase. If it is large, you now know what you are buying rather than taking our word for it.
No. Both numbers come from systems you already own and neither leaves them. There is no tool to sign up for and nothing to upload.
Then compare totals for a closed period and treat the result as directional rather than exact. The conversion reporting inside x ads manager, reconciled against your own records is still the right place to read the platform's side.
Under five percent is working. Five to fifteen usually means reversals are missing. Above twenty is normally the wrong event being counted, not a broken tag — which is why debugging tags first wastes so much time.
Then fix the filter before drawing any conclusion. Calls longer than your qualifying threshold, classified as genuine enquiries. A mismatch in scope produces a gap that looks like a tracking fault and is not one.
Book the free thirty-minute call and bring both numbers. We will tell you which of the causes above it is, and whether it is something you can fix yourself — which it sometimes is.
More on X Ads × Call Records
- Google Ads × Call RecordsHow to reconcile Google Ads against your call tracking records
- Meta × Call RecordsHow to reconcile Meta Ads against your call tracking records
- TikTok × Call RecordsHow to reconcile TikTok Ads against your call tracking records
RELATED GUIDES
Systems of record beside call records, and the funnels it settles
- X Ads × Enrolment SystemHow to reconcile X Ads against your application or enrolment system
- X Ads × Appointment SystemHow to reconcile X Ads against your practice or scheduling system
- X Ads · Directory listing → enquiryHow to track directory listing to enquiry for X Ads
- X Ads · Phone call → saleHow to track phone call to sale for X Ads
- X Ads · LASIKX Ads conversion tracking for LASIK and refractive surgery practices
- X Ads · Addiction treatmentX Ads conversion tracking for addiction treatment centers
- RingCentral → X AdsConnecting RingCentral to X Ads
- kvCORE → X AdsConnecting kvCORE to X Ads
Free · 30 min
Found a gap between X Ads and your call tracking records?
WhatsAppFree30 minutesNo obligation
