CONNECTIONS / Google Drive / Google Drive to TikTok Offline eAPI
Your Google Drive files, wired to TikTok's Offline Events API.
Signals reads your Google Drive files through read-only OAuth access to the Google Drive folder you name, then sends register and phone sales so offline joins TikTok's web optimization so TikTok sees offline conversions without an export.
- ● google drive → tiktok.eapi :: live
- > read closed_deals rows=17,145
- hash sha256(email,phone) consent=filtered
- route tiktok deliver
- ✓ delivered · 14,402 matched
WHAT THIS ENABLES
Google Drive to TikTok Offline Events API
TikTok Offline Events API for Google Drive: Signals sends register and phone sales so offline joins TikTok's web optimization straight from your Google Drive files, hashed and consent-screened each time a new file lands.
- Signals sends register and phone sales so offline joins TikTok's web optimization, reading your Google Drive files each time a new file lands.
- A unified web-and-offline conversion view, with no export step out of your Google Drive files.
The click, the conversion, and the credit.
The conversion happens off TikTok, away from any pixel. Here is how Google Drive closes the loop.
Built for the teams that own the number.
Teams sharing exports via Google Drive who need counter sales deduped against any TikTok web event for the same buyer out of Google Drive files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the Google Drive folder you name, mapped to TikTok's Offline Events API and tuned for web-to-offline deduplication.
-
Map
Columns from your Google Drive files align to TikTok's Offline Events API in the visual mapper, hashed as the file lands and checked for web-to-offline deduplication.
-
Deliver
Each time a new file lands, Signals reads your Google Drive files and sends register and phone sales so offline joins TikTok's web optimization, processes only the newly dropped file, with web-to-offline deduplication watched 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 Google Drive records the event. |
What Offline eAPI actually receives.
- ● signals :: event payload
- > POST /event/track source=google-drive.closed_deals
- event "CompletePayment" · event_time 1784322886
- user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
- properties.value 14948 · properties.currency GBP
- ✓ accepted · dedupe=event_id
Adjacent moves on the same stack.
from Google Drive
Google Drive to Google OCI
Google Offline Conversions for Google Drive: Signals reconciles closed-won revenue to the…
Learn morefrom Google Drive
Google Drive to Google Store Sales
Google Store Sales for Google Drive: Signals matches in-person transactions to Google…
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 Google Drive TikTok Offline eAPI sync run?
Delivery tracks Google Drive, run by teams sharing exports via Google Drive: a near-real-time or scheduled sync of your Google Drive files feeds TikTok on that cadence. Each run processes only the newly dropped file, so a unified web-and-offline conversion view holds up on web-to-offline deduplication. The live debugger confirms every delivery inline.
What match rate should a Google Drive-sourced TikTok Offline eAPI batch expect?
Coverage of hashed identifiers across your Google Drive files decides it, and teams sharing exports via Google Drive own that inside Google Drive. A live email or phone matches into TikTok; neither, and it will not. First-run feedback flags web-to-offline deduplication, which teams sharing exports via Google Drive then raise inside your Google Drive files.
NEXT STEP