TikTok Ads attribution and tracking, from the click to the closed deal

It can run alongside it or instead of it. TikTok deduplicates a pixel event and an Events API event when both carry the same event name and the same event ID, keeping the first copy within 48 hours. LeadJourney's tracking is server-side, so it does not depend on the pixel, and its events reach TikTok through the Events API with an event ID, so a conversion the pixel also reports is counted once.

The Events API is a pipe: it moves events you already have. The hard part is having the right events. TikTok asks you to read the ttclid from the landing page URL and keep it with the form or order yourself, and the access token is generated per pixel in Events Manager. LeadJourney captures the click and the ttclid server-side, follows the lead through your CRM, enriches the event with the value and hashed match keys from the record, and sends it as the stage changes. A hand-built setup only ever knows what your website knows, which is still just the form fill.

Because TikTok counts differently, not wrongly. TikTok credits a conversion to a view as well as a click: a web campaign carries a 1-day view-through window by default, up to 7 days, beside a click-through window of up to 28 days, chosen per ad group. Your CRM only knows the people who arrived and became leads. LeadJourney shows both: TikTok's conversions where you buy, and the revenue that TikTok clicks actually produced, measured on its own.

Yes, that is the point of tracking server-side. The click, the ttclid and the visit are recorded on your own domain before an ad blocker, Safari or a declined banner can remove them, at 95%+ accuracy. Ads Manager keeps reporting what the pixel can see; LeadJourney shows you the measured numbers.

Because TikTok opens links in its own in-app browser, and that browser often sends your site no referrer. Analytics that classify by referrer then file the visit under direct. An ad click carries the ttclid on the URL whatever the browser sends, and LeadJourney reads it server-side on arrival, so the visit is filed under TikTok and the campaign behind it.

In LeadJourney, yes. The TikTok click is stored on the visitor's LeadJourney Click ID, so when the same person comes back through Google brand search, a ChatGPT answer or a typed URL and converts, TikTok is still part of that journey. Multi-touch models then share the revenue between TikTok and the channel that closed, instead of handing all of it to the search.

Any CRM stage or paid order you map: marketing qualified, sales qualified, deal won, a Shopify or Stripe purchase, or all of them. Each event carries the value and currency, so the campaign is judged on revenue rather than a flat lead value.

Instant Forms collect contact details inside TikTok, so the lead never visits your site and there is no ttclid to capture. TikTok's Leads Center hands them to your CRM, directly for HubSpot and Salesforce or through Zapier and Make. Once they are there with their campaign, LeadJourney follows them to the deal like any other lead. For campaigns that send people to a form on your own site, the click, the ttclid and the form fill are tracked server-side by default.

TikTok's app shares store data at three levels, and only the higher two add the Events API. Either way it reports TikTok's view of the order. LeadJourney reads the paid order from Shopify and sends it to TikTok server-side with its value, so an order the pixel missed still reaches TikTok, and the same order is attributed next to Meta, Google and email in one model.

HubSpot's ads tool does connect TikTok, alongside Meta, Google, LinkedIn and Microsoft, and reports the contacts those ads produced inside HubSpot. LeadJourney records the TikTok click server-side with its ttclid, follows each lead into HubSpot to the deal next to every other channel including organic and AI search, and sends the qualified leads and won deals back through the Events API with their value.

No. TikTok's MCP server works on the ad account: it creates campaigns, pulls TikTok's reports and manages creatives and audiences. LeadJourney's MCP server answers with your attribution data, so a question about which TikTok campaigns started the deals you closed is answered from your CRM revenue, next to every other channel.

By the click. An ad click arrives with the ttclid and the UTMs TikTok fills in from its macros, such as __CAMPAIGN_NAME__ and __CID__, so it is filed under the campaign. Bio links and video links are the organic side, covered on the TikTok integration page, and they stay on their own line.

In LeadJourney, yes: the journey has no window, so the deal is credited to the campaign that started it regardless of the cycle length. TikTok credits a conversion only inside the click-through window you chose for the ad group, 28 days at most, so for a long cycle map an early stage that predicts revenue, such as the qualified lead, as the event delivery learns from. The report that matches the late revenue to the ad lives in LeadJourney.

Identifiers are hashed before they leave, you control which stages and which fields are used for matching, and nothing is sent that you have not mapped. LeadJourney itself processes and stores data in the EU, signs a data processing agreement, and tracks first-party and server-side, so consent decisions are respected rather than worked around.

No. Connecting TikTok Ads is a sign in, the CRM connection is the same, and mapping stages to events is a settings screen. Most accounts are live in about 21 minutes, and our team will do the setup with you on a call if you prefer.

The TikTok Ads integration is part of the platform rather than a paid add on. Plans are priced by the marketing spend you track, not by seats, so your whole team can share one workspace, and every plan comes with onboarding by a tracking expert and a 30-day money-back guarantee.