CONNECTIONS / Branch / Branch to TikTok App eAPI
Branch events into TikTok, built for TikTok's App Events API.
Signals reads your Branch events through a Branch webhook pointed at Signals, then reports in-app events to TikTok server-side so app campaigns bid on real actions so TikTok sees app conversions without an export.
- ● branch → tiktok.eapi :: live
- > read app_events rows=11,190
- hash sha256(email,phone) consent=filtered
- route tiktok deliver
- ✓ delivered · 8,169 matched
WHAT THIS ENABLES
Branch to TikTok App Events API
Branch to TikTok App Events API: Signals reads your Branch events and reports in-app events to TikTok server-side so app campaigns bid on real actions, hashed and consent-checked as in-app events fire.
- Signals reports in-app events to TikTok server-side so app campaigns bid on real actions, reading your Branch events as in-app events fire.
- Post-install actions TikTok can bid on, with no export step out of your Branch events.
WHAT FLOWS WHERE
Branch to App Events API, mapped.
Signals receives the in-app purchase and install events from your Branch events; Signals hashes and consent-screens each record before TikTok's App Events API accepts the app conversions for post-install event coverage.
Signals receives the in-app purchase and install events from your Branch events; Signals hashes and consent-screens each record before TikTok's App Events API accepts the app conversions for post-install event coverage.
Built for the teams that own the number.
Mobile teams running Branch who need in-app conversions TikTok optimizes on past the install out of Branch events.
From kickoff to verified events.
-
Connect
A Branch webhook pointed at Signals, mapped to TikTok's App Events API and tuned for post-install event coverage.
-
Map
Columns from your Branch events align to TikTok's App Events API in the visual mapper, hashed as each postback arrives and checked for post-install event coverage.
-
Deliver
As in-app events fire, Signals reads your Branch events and reports in-app events to TikTok server-side so app campaigns bid on real actions, forwards each app event as it arrives, with post-install event coverage watched in the debugger.
What ships with this use case.
In-app conversions TikTok optimizes on past the install from your Branch events, delivered as in-app events fire.
Post-install actions TikTok can bid on out of your Branch events, delivered as in-app events fire without event volume climbing.
Match feedback on post-install event coverage from TikTok's App Events API each run, tied back to your Branch events.
What App Events API actually receives.
- ● signals :: event payload
- > POST /app/track source=branch.app_events
- event "in_app_purchase" · event_time 1784264644
- user.idfa "8f2b…" · user.email sha256 "c4a1d0…"
- properties.value 2638 · properties.currency AED
- ✓ accepted · dedupe=event_id
Adjacent moves on the same stack.
from Branch
Branch to Meta App CAPI
Branch to Meta App Conversions: Signals reads your Branch events and sends in-app purchases…
Learn morefrom Branch
Branch to Snap App CAPI
Branch to Snap App Conversions: Signals reads your Branch events and posts in-app purchases…
Learn moresame use case
Adjust to TikTok App eAPI
Adjust to TikTok App Events API: Signals reads your Adjust postbacks and reports in-app…
Learn moregeneric
TikTok App Events API
Datahash sends in-app events to TikTok server-side, so installs and post-install actions…
Learn moreAsked on almost every call.
How often does the Branch TikTok App eAPI sync run?
You set the cadence, from near-real-time to a nightly Branch sync of your Branch events into TikTok. Since Signals forwards each app event as it arrives, in-app conversions TikTok optimizes on past the install keeps pace and mobile teams running Branch watch post-install event coverage. One scoped connection sets it up, cadence adjustable later.
What match rate should a Branch-sourced TikTok App eAPI batch expect?
Match rate follows identifier coverage in your Branch events, which mobile teams running Branch control, not Branch itself. A record with a current hashed email or phone matches for TikTok; one missing both cannot. First-run feedback from App Events API pinpoints post-install event coverage, the number mobile teams running Branch tune against.
NEXT STEP