Jump to a popular page, or start typing.

    CONNECTIONS / Databricks / Databricks to TikTok Custom Audience

    Your Databricks lakehouse, wired to TikTok audience targeting.

    Signals reads the Delta table through a Unity Catalog grant and delivers first-party segments to TikTok as match-ready custom audiences, hashed on the way out and governed like any other lakehouse job.

    databricks -> tiktok-custom-audience :: live

    1. ● databricks → tiktok.audience :: live
    2. > read main.audiences.segment_tier rows=22,115
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 19,904 matched

    WHAT THIS ENABLES

    Databricks to TikTok Custom Audience

    Databricks to TikTok Custom Audience: A notebook job reads the customer segments in your Databricks Delta tables, and Signals delivers first-party segments to TikTok as match-ready custom audiences, hashed and consent-checked each time the model rebuilds.

    • Signals delivers first-party segments to TikTok as match-ready custom audiences, reading your Databricks Delta tables each time the model rebuilds.
    • TikTok custom audiences mirroring the segment your data team publishes, fed by data engineers modeling in Databricks notebooks.

    WHAT FLOWS WHERE

    Databricks to Custom Audience, mapped.

    The notebook job streams customer segments into Signals for hashing and consent screening, then TikTok's Custom Audience API records the match-ready audiences with match quality on TikTok accounted for.

    The notebook job streams customer segments into Signals for hashing and consent screening, then TikTok's Custom Audience API records the match-ready audiences with match quality on TikTok accounted for.

    WHO THIS IS FOR

    Built for the teams that own the number.

    TikTok advertisers seeding lookalikes and suppressing existing customers, with the numbers already modeled in Databricks Delta tables governed by Unity Catalog.

    Data engineers modeling in Databricks notebooks who need TikTok custom audiences mirroring the segment your data team publishes.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A Unity Catalog-scoped service principal on the single Delta table in play to feed TikTok's Custom Audience API, sized for match quality on TikTok.

    2. Map

      A notebook job reads your Databricks Delta tables, and its columns map to TikTok's Custom Audience API in the visual mapper, hashed and checked for match quality on TikTok.

    3. Deliver

      Each time the model rebuilds, Signals delivers first-party segments to TikTok as match-ready custom audiences, reads only the rows the model rebuilt, with match quality on TikTok watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    TikTok custom audiences mirroring the segment your data team publishes on every run, since Signals reads only the rows the model rebuilt.

    Targeting that mirrors your live segment, delivered each time the model rebuilds without job-cluster time climbing.

    Each run returns a match report on match quality on TikTok from TikTok's Custom Audience API, read from your Databricks Delta tables each time the model rebuilds, at flat job-cluster time.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: databricks.tiktok-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /dmp/custom_audience source=databricks.main.audiences.segment_tier
    3. id_schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. action "add" · audience_id "aud_66523"
    5. id_list_size 22,115 · matched 19,904
    6. ✓ accepted match=90%
    FAQ

    Asked on almost every call.

    How often does the Databricks TikTok Custom Audience sync run?

    Cadence follows the job that rebuilds the table: a nightly model gives TikTok a nightly feed, an hourly one an hourly feed. Because a run picks up only the rows the model rebuilt, TikTok custom audiences mirroring the segment your data team publishes keeps pace on match quality on TikTok and job-cluster time stays modest.

    What match rate should a Databricks-sourced TikTok Custom Audience batch expect?

    Identifier quality in the Delta table drives it, not the cluster size. Rows carrying a live hashed email or phone land; rows with neither will not, and no rebuild changes that. The opening run's feedback from TikTok's Custom Audience API flags the gap for TikTok advertisers seeding lookalikes and suppressing existing customers tracking match quality on TikTok.

    NEXT STEP

    Databricks to TikTok Custom Audience, in production this week.