Jump to a popular page, or start typing.

    CONNECTIONS / Redshift / Redshift to TikTok Offline eAPI

    Offline and in-store sales in Redshift, activated for TikTok's Offline Events API.

    Grant a scoped IAM role, name the table or materialized view, and Signals sends register and phone sales so offline joins TikTok's web optimization with no UNLOAD to S3 and no file to hand off.

    redshift -> tiktok-offline-eapi :: live

    1. ● redshift → tiktok.eapi :: live
    2. > read sales.pos_fact rows=52,070
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 43,218 matched

    WHAT THIS ENABLES

    Redshift to TikTok Offline Events API

    Redshift to TikTok Offline Events API: The Redshift Data API reads the offline and in-store sales in your Redshift tables, and Signals sends register and phone sales so offline joins TikTok's web optimization, hashed and consent-checked as the materialized view refreshes.

    • Signals sends register and phone sales so offline joins TikTok's web optimization, reading your Redshift tables as the materialized view refreshes.
    • Counter sales deduped against any TikTok web event for the same buyer, fed by analytics teams maintaining Redshift tables and materialized views.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    TikTok credits the campaign that sourced the conversion conversion happens off-platform Ad click on TikTok R Scheduled read sync recorded in Redshift 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, with the numbers already modeled in Redshift tables and materialized views.

    Analytics teams maintaining Redshift tables and materialized views who need counter sales deduped against any TikTok web event for the same buyer.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A scoped IAM role with SELECT on the schema you name to feed TikTok's Offline Events API, sized for web-to-offline deduplication.

    2. Map

      The Redshift Data API reads your Redshift tables, and its columns map to TikTok's Offline Events API in the visual mapper, hashed and checked for web-to-offline deduplication.

    3. Deliver

      As the materialized view refreshes, Signals sends register and phone sales so offline joins TikTok's web optimization, touches only the rows changed since the last read, 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 Redshift records the event.
    ON THE WIRE

    What Offline eAPI actually receives.

    signals :: redshift.tiktok-offline-eapi :: wire

    1. ● signals :: event payload
    2. > POST /event/track source=redshift.sales.pos_fact
    3. event "CompletePayment" · event_time 1784742285
    4. user.email sha256 "c02fa8…" · user.phone sha256 "6b91dd…"
    5. properties.value 45885 · properties.currency USD
    6. ✓ accepted · dedupe=event_id
    FAQ

    Asked on almost every call.

    How often does the Redshift TikTok Offline eAPI sync run?

    The refresh schedule drives it: when the materialized view rebuilds nightly, TikTok gets a nightly feed, and an hourly refresh runs hourly. Each read touches only changed rows, so counter sales deduped against any TikTok web event for the same buyer stays fresh for web-to-offline deduplication without RA3 load rising.

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

    The fill rate of the view matters more than Redshift itself. A clean hashed email or phone matches; a blank one never will. The first scheduled read reports quality from TikTok's Offline Events API, the figure brands whose TikTok conversions finish at a till, not a checkout weigh against web-to-offline deduplication.

    NEXT STEP

    Redshift to TikTok Offline eAPI, in production this week.