TikTok Offline eAPI
TikTok Offline Events API, live and reconciled.
Move your in-store and call-centre conversions to TikTok server-side, so TikTok can optimize campaigns on the outcomes that matter.
- ● tiktok.offline_eapi :: live
- > batch offline_sales rows=8,940
- hash sha256(em,ph) pii=cleared
- match hashed identifiers 47%
- ✓ uploaded · offline events received
Built for the teams that own the number.
Teams closing sales through call centres and branch networks.
From kickoff to verified events.
-
Source
Ingest offline events from POS, call-centre, CRM, or file drop.
-
Reconcile
Match with hashed customer identifiers per TikTok spec.
-
Deliver
TikTok Offline Events API delivery on a monitored schedule.
WHAT FLOWS WHERE
One use case, every source.
A sale closes in your POS or CRM, Signals hashes the customer identifiers on a scheduled batch, matches them, then delivers the conversion to TikTok's Offline Events API.
A sale closes in your POS or CRM, Signals hashes the customer identifiers on a scheduled batch, matches them, then delivers the conversion to TikTok's Offline Events API.
What ships with this offering.
Offline outcomes feeding TikTok campaign optimization.
Hashed, privacy-safe identifier handling end to end.
Delivery cadence matched to your operations.
ON THE WIRE
What the platform actually receives.
Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.
- ● signals :: offline payload
- > POST /open_api/v1.3/event/track/ event_source=offline
- event "CompletePayment" · event_id "pos-48112"
- user email_sha256 "a2c9…" · phone_sha256 "6d41…"
- properties value 249 · currency AED
- ✓ code 0 · message OK
Adjacent moves on the same stack.
tiktok
TikTok Web eAPI
Datahash is a TikTok Partner. We deliver server-side TikTok Events API with dedupe against your existing Pixel and full support for TikTok's advanced matching parameters.
Learn moretiktok
TikTok CRM Integration
Sync qualified lead stages from your CRM back to TikTok so lead-based campaigns optimize on outcomes rather than form fills.
Learn more
meta
Meta Offline CAPI
Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to Meta with hashed identifiers, event dedupe, and closed-loop match reporting.
Learn more
snap
Snap Offline CAPI
Deliver offline conversions to Snap on a schedule that fits your operations.
Learn moreBring it from where the data lives.
Every source that supports this use case. Pick a platform to see the exact setup.
CRM
Databases
Files / storage
Data warehouses
Datahash API
Custom
Questions your team will ask.
What events are supported offline?
Any conversion your source systems record, most commonly in-store purchases, call-centre sales, and completed CRM deals. Each event type is mapped to TikTok's offline event taxonomy during setup, so purchases from a POS system and closed deals from a CRM both arrive as recognized conversions. Custom event types from a file drop or warehouse export are supported the same way.
What is the delivery cadence?
Delivery cadence is configurable, ranging from near real time to daily or weekly batches depending on how your source systems export data. Fresher delivery feeds TikTok's optimization sooner, so we default to daily batches wherever POS, call-centre, or CRM exports allow it. Cadence can be revisited later if your operations change, without rebuilding the underlying pipeline.
How do you dedupe offline events?
Each event carries a stable event identifier derived from your source system, so re-sent batches and overlapping feeds never double count toward the same conversion. This matters for offline data, where a file can be resubmitted after a failed upload or a CRM export can overlap with the previous run. We verify dedupe on sample data before any campaign relies on it.
NEXT STEP
Live in fifteen minutes. Measurable in a week.
Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.