Jump to a popular page, or start typing.

    CONNECTIONS / AWS S3 / AWS S3 to TikTok Offline eAPI

    S3 exports into TikTok, built for TikTok's Offline Events API.

    Signals reads your S3 exports through a read-only IAM key scoped to the one S3 bucket you name, then sends register and phone sales so offline joins TikTok's web optimization so TikTok sees offline conversions without an export.

    aws-s3 -> tiktok-offline-eapi :: live

    1. ● aws s3 → tiktok.eapi :: live
    2. > read closed_deals rows=24,937
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 21,945 matched

    WHAT THIS ENABLES

    AWS S3 to TikTok Offline Events API

    TikTok Offline Events API for AWS S3: Signals sends register and phone sales so offline joins TikTok's web optimization straight from your S3 exports, 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 S3 exports each time a new file lands.
    • A unified web-and-offline conversion view, with no export step out of your S3 exports.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off TikTok, away from any pixel. Here is how AWS S3 closes the loop.

    TikTok credits the campaign that sourced the conversion conversion happens off-platform Ad click on TikTok A File drop sync recorded in AWS S3 S Signals hash · dedupe Offline Events API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Brands whose TikTok conversions finish at a till, not a checkout, working out of S3 objects, prefixes, and export drops.

    Data teams landing exports in S3 who need counter sales deduped against any TikTok web event for the same buyer out of S3 exports.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only IAM key scoped to the one S3 bucket you name, mapped to TikTok's Offline Events API and tuned for web-to-offline deduplication.

    2. Map

      Columns from your S3 exports align to TikTok's Offline Events API in the visual mapper, hashed as the file lands and checked for web-to-offline deduplication.

    3. Deliver

      Each time a new file lands, Signals reads your S3 exports 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 YOU GET

    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 AWS S3 records the event.
    ON THE WIRE

    What Offline eAPI actually receives.

    signals :: aws-s3.tiktok-offline-eapi :: wire

    1. ● signals :: event payload
    2. > POST /event/track source=aws-s3.closed_deals
    3. event "CompletePayment" · event_time 1784418218
    4. user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
    5. properties.value 42565 · properties.currency GBP
    6. ✓ accepted · dedupe=event_id
    FAQ

    Asked on almost every call.

    How often does the AWS S3 TikTok Offline eAPI sync run?

    You set the cadence, from near-real-time to a nightly AWS S3 sync of your S3 exports into TikTok. Since Signals processes only the newly dropped file, counter sales deduped against any TikTok web event for the same buyer keeps pace and data teams landing exports in S3 watch web-to-offline deduplication. One scoped connection sets it up, cadence adjustable later.

    What match rate should a AWS S3-sourced TikTok Offline eAPI batch expect?

    Match rate follows identifier coverage in your S3 exports, which data teams landing exports in S3 control, not AWS S3 itself. A record with a current hashed email or phone matches for TikTok; one missing both cannot. First-run feedback from Offline Events API pinpoints web-to-offline deduplication, the number data teams landing exports in S3 tune against.

    NEXT STEP

    AWS S3 to TikTok Offline eAPI, in production this week.