CONNECTIONS / GCS / GCS to TikTok Offline eAPI
Your GCS objects, wired to TikTok's Offline Events API.
Connect GCS and point Signals at your GCS objects; it sends register and phone sales so offline joins TikTok's web optimization each time a new file lands, hashed and consent-checked for TikTok.
- ● gcs → tiktok.eapi :: live
- > read closed_deals rows=65,705
- hash sha256(email,phone) consent=filtered
- route tiktok deliver
- ✓ delivered · 58,477 matched
WHAT THIS ENABLES
GCS to TikTok Offline Events API
GCS to TikTok Offline Events API: your GCS objects, hashed and consent-checked, feed TikTok as Signals sends register and phone sales so offline joins TikTok's web optimization each time a new file lands.
- Offline and in-store sales from your GCS objects activated for TikTok, as Signals sends register and phone sales so offline joins TikTok's web optimization.
- Counter sales deduped against any TikTok web event for the same buyer, drawn from your GCS objects by data teams landing exports in GCS.
The click, the conversion, and the credit.
The conversion happens off TikTok, away from any pixel. Here is how GCS closes the loop.
Built for the teams that own the number.
Data teams landing exports in GCS activating TikTok's Offline Events API straight from GCS objects.
From kickoff to verified events.
-
Connect
A read-only service account scoped to the one GCS bucket you name to feed TikTok's Offline Events API, sized for web-to-offline deduplication.
-
Map
Signals picks up your GCS objects, and its columns map to TikTok's Offline Events API in the visual mapper, hashed and checked for web-to-offline deduplication.
-
Deliver
On each run, Signals pulls your GCS objects, sends register and phone sales so offline joins TikTok's web optimization, and processes only the newly dropped file, with web-to-offline deduplication in the debugger.
What changes when the CSV goes away.
| Capability | Manual CSV upload | Datahash |
|---|---|---|
| Reporting | Offline sales sit in a separate export, reconciled by hand. | Revenue counted in the same Offline eAPI reporting as web conversions. |
| Deduplication | A re-uploaded file risks counting the same conversion twice. | Deduped delivery, so a resent record never counts as a second conversion. |
| Match visibility | Match quality is a guess until the numbers look off. | Match rate reported per upload, tied to the source event set that produced it. |
| Effort and latency | An analyst exports and uploads on a manual cadence. | Server-side and automatic the moment GCS records the event. |
What Offline eAPI actually receives.
- ● signals :: event payload
- > POST /event/track source=google-cloud-storage.closed_deals
- event "CompletePayment" · event_time 1784347875
- user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
- properties.value 12272 · properties.currency SAR
- ✓ accepted · dedupe=event_id
Adjacent moves on the same stack.
from GCS
GCS to Google OCI
GCS to Google Offline Conversions: your GCS objects, hashed and consent-checked, feed…
Learn morefrom GCS
GCS to Google Store Sales
GCS to Google Store Sales: your GCS objects, hashed and consent-checked, feed Google Ads as…
Learn moresame use case
ActiveCampaign to TikTok Offline eAPI
ActiveCampaign to TikTok Offline Events API: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
TikTok Offline eAPI
Move your in-store and call-centre conversions to TikTok server-side, so TikTok can…
Learn moreAsked on almost every call.
How often does the GCS TikTok Offline eAPI sync run?
The pace follows your GCS objects: Signals sends changes from GCS to TikTok each time a new file lands. Because it processes only the newly dropped file, counter sales deduped against any TikTok web event for the same buyer stays current while data teams landing exports in GCS keep web-to-offline deduplication in view. Delivery needs no export and no manual upload.
What match rate should a GCS-sourced TikTok Offline eAPI batch expect?
Coverage of hashed identifiers across your GCS objects decides it, and data teams landing exports in GCS own that inside GCS. A live email or phone matches into TikTok; neither, and it will not. First-run feedback flags web-to-offline deduplication, which data teams landing exports in GCS then raise inside your GCS objects.
NEXT STEP