X Ads conversion tracking for multi-location businesses
A multi-location business has one website, many Google Business Profiles, many phone numbers, and a reporting requirement that runs both ways — head office needs the portfolio view and each location needs its own numbers. What X Ads adds on top of that is a mechanical requirement: the twclid click identifier has to reach the record that holds the money, because X Ads can only credit a conversion it can tie back to a click it recognizes. This page covers both halves — what a conversion is in multi-location businesses, and what X Ads specifically needs to accept it.
Free30 minutesNo obligation
Specific to X Ads × Multi-location
X Ads for multi-location brands: brand-level only, keep it simple
On X, a multi-location business should run brand-level campaigns and send one server-side conversion, such as a booking or order, through the X Conversions API from the central booking or order system, matched on the twclid captured at landing, with the reference as conversion ID. Branch attribution stays in your own records.
X is rarely a good channel for a multi-location business. Its local targeting is coarser than search or Meta, its conversion volumes are small, and its audience isn't organized around neighborhoods. Where it helps is brand-level moments: a national promotion, a new-market launch or a service outage notice. Treat it as a brand channel and avoid splitting already small numbers by branch.
If you run it, send one conversion from the central system and attach the fulfilling branch in your own reporting. Don't create one X conversion per branch; a dozen near-empty conversions gives you nothing to compare. Store twclid on the booking or order record before it moves through a store locator, so the branch flow keeps the click identifier.
X's ad API has changed often enough that a setup can stop sending without obvious errors. In a multi-location stack, that tends to show up as one branch's booking engine updating and quietly dropping the stored twclid. Re-test a real conversion through the store locator at least once a quarter, and before every national promotion.
X Ads · Multi-location · what breaks
Why X Ads under-reports for multi-location businesses
- 01
Conversions in one undifferentiated pool
No location can be evaluated.
- 02
Location pages sharing one phone number
So calls can't be attributed to a branch.
- 03
Head office and branch reporting in conflict
Two audiences, one number.
- 04
The twclid click identifier never reaches the record
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.
X Ads · Multi-location · the fix
What working looks like — X Ads · Multi-location
Every conversion carrying a location
At the point it happens.
Per-location and portfolio views
From the same data.
Budget allocated on measured performance
Rather than on instinct.
X Ads · Multi-location · architecture
How X Ads and multi-location businesses actually connect
- 1
The conversion in multi-location businesses
Enquiry, booking or order, fulfilment — each carrying a location. The location dimension matters more than any individual stage.
- 2
X Ads needs a click to match
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.
- 3
The identifier: the twclid click identifier
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.
- 4
Where it gets sent from
each location's own booking, order or job records.
- 5
Deduplication and window
The pattern is familiar — the tag and the server event must agree on an identifier for the same conversion — but the implementation details have changed more than once. Test deduplication on a real conversion rather than assuming the configuration is correct. 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.
X Ads · Multi-location · events
The conversion map for multi-location businesses
The stages are ordinary. What makes this vertical hard is that every one of them needs a location attached.
| Event | What it means here |
|---|---|
| Enquiry with location | Browser-side, location from the page or the form. |
| Call with location | A tracked number pool per branch. |
| Booking or order with location | Server-side from the branch's own system. |
| Fulfilment with location | Server-side. The conversion that carries value. |
| Location dimension | Present on every event. Without it none of this is usable. |
X Ads · Multi-location · diagnose
Diagnostic order — X Ads · Multi-location
- 01
Count records carrying the twclid click identifier
- 02
One phone number across all location pages
Calls can't be attributed to a branch, which is usually most of the conversions.
- 03
Location missing from the conversion event
So the data exists and can't be split.
- 04
Google Business Profile calls uncredited
A large local channel, invisible.
- 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 · Multi-location · prove
How it gets proven — X Ads · Multi-location
Source of truth
each location's own booking, order or job records
- Location present on every conversion event, verified on live conversions at more than one branch.
- A tracked number pool confirmed per location.
- Per-location reconciliation for a closed month.
- Portfolio totals that add up from the per-location figures.
- The conversion reporting inside X Ads Manager, reconciled against your own records read directly, not inferred from an upload succeeding.
X Ads · Multi-location · free audit
What we check in the free audit
- Count records carrying the twclid click identifier
- One phone number across all location pages
- Location missing from the conversion event
- Google Business Profile calls uncredited
- Read the conversion reporting inside X Ads Manager, reconciled against your own records
Checked against
each location's own booking, order or job records
Free30 minutesNo obligation
X Ads · Multi-location · when not to buy
When you don't need this — X Ads · Multi-location
- If X Ads already reports conversions that reconcile against each location's own booking within a few percent, this is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred records and count how many carry the twclid click identifier.
- 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 · Multi-location · what we deliver
What gets built — X Ads · Multi-location
Location captured on every conversion
From the page, the form, or the number dialled.
A tracked number pool per location
So calls resolve to a branch.
Location-level records as the source of truth
The branch system, not a site-wide total.
Reporting built both ways
Portfolio and per branch.
Dispatch via the X Conversions API
Server events posted with the click identifier and hashed customer information. This is the least stable API surface of the platforms covered here — confirm the current specification against X's own developer documentation, and expect it to have moved since anyone last wrote about it.
Written guarantee
95%+ tracking accuracy
Measured against each location's own booking, order or job records. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
X Ads · Multi-location questions, answered
Usually only for brand-level moments such as launches or national promotions. Its local targeting and conversion volumes are too thin to run branch-level campaigns.
In your own reporting, not in X. Send one conversion from the central system and attribute it to the branch that fulfilled it using your records.
Yes, if location is captured on every conversion — from the page path, a form field, or the number dialled. Without that, the data is one undifferentiated pool.
A tracked number pool per location. One shared number makes branch-level call attribution impossible, and calls are usually most of the volume.
Track them per location and separately from paid. They're a real channel and mixing them makes both unreadable.
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.
Server events posted with the click identifier and hashed customer information. This is the least stable API surface of the platforms covered here — confirm the current specification against X's own developer documentation, and expect it to have moved since anyone last wrote about it.
By reading the conversion reporting inside X Ads Manager, reconciled against your own records and reconciling against each location's own booking, order or job records. An upload that succeeds is not an upload that matched.
More on X Ads · Multi-location
- Multi-locationConversion tracking for multi-location businesses, attributed to the right branc…
- Google Ads · Multi-locationGoogle Ads conversion tracking for multi-location businesses
- Meta · Multi-locationMeta Ads conversion tracking for multi-location businesses
RELATED GUIDES
More for multi location businesses: other angles on the same outcome
- Multi-locationConversion tracking for multi-location businesses, attributed to the right branch
- X Ads · Auto repairX Ads conversion tracking for auto repair and collision shops
- X Ads · Window tintingX Ads conversion tracking for window tinting businesses
- X Ads · Franchise enquiry → agreementHow to track franchise enquiry to signed agreement for X Ads
- X Ads × Call RecordsHow to reconcile X Ads against your call tracking records
- Lightspeed → X AdsConnecting Lightspeed to X Ads
- X Ads · Real estateX Ads conversion tracking for real estate companies
- X Ads · GolfX Ads conversion tracking for golf courses and clubs
Free · 30 min
Get X Ads reporting what multi-location businesses actually earn
WhatsAppFree30 minutesNo obligation
