Skip to main content
TikTok · Multi-locationTikTok × Multi-location

TikTok 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 TikTok Ads adds on top of that is a mechanical requirement: ttclid has to reach the record that holds the money, because TikTok 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 TikTok specifically needs to accept it.

Free30 minutesNo obligation

Specific to TikTok × Multi-location

TikTok for multi-location brands: regional reach, branch-level truth

On TikTok, a multi-location brand should send CompletePayment or SubmitForm through the Events API from each branch's booking or order system, matched on the ttclid captured at landing plus hashed contact data, with the order or booking reference as event_id and the branch stored on your side for per-location reporting.

TikTok suits consumer chains with a younger customer: gyms, fast casual, salons, entertainment venues, auto services aimed at first-time owners. Its creative tends to be brand-level, and a good video gets seen far beyond the branch's catchment. That means TikTok conversions land at branches nobody targeted, and per-branch cost comparisons for TikTok will mostly reflect where viewers lived rather than campaign quality.

Run TikTok at a regional or brand level and attribute conversions to the fulfilling branch in your own reporting. If you split campaigns by market, check how precisely TikTok's location targeting follows your branch catchments before treating campaign geography as branch geography. Send the conversion from the branch system, since a regional landing page can't know which branch will finally serve the customer.

The usual break is the store locator. A user taps a TikTok ad, lands on a brand page, picks a branch, and moves to that branch's booking widget, often on another subdomain, where ttclid is gone. Persist ttclid on landing at the brand level, and pass it through the locator into the branch booking flow so the branch record still carries it.

TikTok · Multi-location · what breaks

Why TikTok under-reports for multi-location businesses

  1. 01

    Conversions in one undifferentiated pool

    No location can be evaluated.

  2. 02

    Location pages sharing one phone number

    So calls can't be attributed to a branch.

  3. 03

    Head office and branch reporting in conflict

    Two audiences, one number.

  4. 04

    Ttclid never reaches the record

    TikTok's click identifier, appended to the landing URL. Capture it on landing and persist it exactly as you would gclid or fbclid — it's the strongest matching signal available and the most commonly missing one, because TikTok is often added to a stack that was built around Google and Meta.

TikTok · Multi-location · the fix

What working looks like — TikTok · 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.

TikTok · Multi-location · architecture

How TikTok and multi-location businesses actually connect

  1. 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. 2

    TikTok Ads needs a click to match

    A standard event name, an event timestamp, a shared event ID, hashed and normalized user identifiers, and ttclid where available. Confirm the current required fields in TikTok's documentation before building.

  3. 3

    The identifier: ttclid

    TikTok's click identifier, appended to the landing URL. Capture it on landing and persist it exactly as you would gclid or fbclid — it's the strongest matching signal available and the most commonly missing one, because TikTok is often added to a stack that was built around Google and Meta.

  4. 4

    Where it gets sent from

    each location's own booking, order or job records.

  5. 5

    Deduplication and window

    Send the same event ID from the browser pixel and the server event. The mechanics mirror Meta's closely enough that a team who has done one can do the other, but verify TikTok's current requirements rather than assuming parity — the deduplication window in particular isn't a figure we'll guess at. Verify the current attribution and import windows in TikTok's documentation. They differ from Google's and Meta's, and quoting a number here that goes stale would be worse than sending you to the source.

TikTok · 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.

Enquiry with locationBrowser-side, location from the page or the form.
Call with locationA tracked number pool per branch.
Booking or order with locationServer-side from the branch's own system.
Fulfilment with locationServer-side. The conversion that carries value.
Location dimensionPresent on every event. Without it none of this is usable.

TikTok · Multi-location · diagnose

Diagnostic order — TikTok · Multi-location

  1. 01

    Count records carrying ttclid

  2. 02

    One phone number across all location pages

    Calls can't be attributed to a branch, which is usually most of the conversions.

  3. 03

    Location missing from the conversion event

    So the data exists and can't be split.

  4. 04

    Google Business Profile calls uncredited

    A large local channel, invisible.

  5. 05

    Read TikTok's own event diagnostics, plus a reconciliation against your records

    TikTok is usually the third platform added to a stack, and it typically inherits whatever assumptions were made for Google and Meta. The most common result is that ttclid is never captured at all, because the capture code was written naming gclid and fbclid and nobody revisited it.

TikTok · Multi-location · prove

How it gets proven — TikTok · 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.
  • TikTok's own event diagnostics, plus a reconciliation against your records read directly, not inferred from an upload succeeding.

TikTok · Multi-location · free audit

What we check in the free audit

  • Count records carrying ttclid
  • One phone number across all location pages
  • Location missing from the conversion event
  • Google Business Profile calls uncredited
  • Read TikTok's own event diagnostics, plus a reconciliation against your records

Checked against

each location's own booking, order or job records

Get my free conversion tracking audit

Free30 minutesNo obligation

TikTok · Multi-location · when not to buy

When you don't need this — TikTok · Multi-location

  • If TikTok 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 ttclid.
  • If TikTok is a small share of your spend, the effort is better spent making Google and Meta correct first — the same infrastructure then extends to TikTok as one additional tag rather than a separate project.

TikTok · Multi-location · what we deliver

What gets built — TikTok · 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 Events API

    Structurally similar to the other server-side conversion APIs: event name, timestamp, event ID, hashed user identifiers, event properties. TikTok's exact field names change more often than the other major platforms', so build against their current documentation rather than a blog post — including this one.

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.

Get my free conversion tracking audit

From $400 · See packages

FAQ

TikTok · Multi-location questions, answered

Not from TikTok's reporting alone. Send conversions from each branch's system and keep the branch in your own data, then report TikTok by branch there, since TikTok's audiences don't follow branch catchments.

Free · 30 min

Get TikTok reporting what multi-location businesses actually earn

Free30 minutesNo obligation