Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / MySQL / MySQL to TikTok Custom Audience

    From MySQL tables to TikTok audience targeting.

    Signals reads your MySQL tables through a read-only database user scoped to the MySQL tables you name, then delivers first-party segments to TikTok as match-ready custom audiences so TikTok sees match-ready audiences without an export.

    Talk to our team Explore the setup

    mysql -> tiktok-custom-audience :: live

    1. ● mysql → tiktok.audience :: live
    2. > read segments rows=62,567
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 48,802 matched

    WHAT THIS ENABLES

    MySQL to TikTok Custom Audience

    MySQL to TikTok Custom Audience: Signals reads your MySQL tables and delivers first-party segments to TikTok as match-ready custom audiences, hashed and consent-checked each time the read runs.

    • Signals delivers first-party segments to TikTok as match-ready custom audiences, reading your MySQL tables each time the read runs.
    • Targeting that mirrors your live segment, with no export step out of your MySQL tables.

    WHAT FLOWS WHERE

    MySQL to Custom Audience, mapped.

    Signals reads the customer segments from your MySQL tables each time the read runs, hashes and screens each record, and posts the match-ready audiences to TikTok's Custom Audience API, keeping match quality on TikTok in view.

    Signals reads the customer segments from your MySQL tables each time the read runs, hashes and screens each record, and posts the match-ready audiences to TikTok's Custom Audience API, keeping match quality on TikTok in view.

    WHO THIS IS FOR

    Built for the teams that own the number.

    TikTok advertisers seeding lookalikes and suppressing existing customers, working out of MySQL tables and views.

    Application teams on MySQL who need TikTok custom audiences mirroring the segment your data team publishes out of MySQL tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the MySQL tables you name, mapped to TikTok's Custom Audience API and tuned for match quality on TikTok.

    2. Map

      Columns from your MySQL tables align to TikTok's Custom Audience API in the visual mapper, hashed as the read runs and checked for match quality on TikTok.

    3. Deliver

      Each time the read runs, Signals reads your MySQL tables and delivers first-party segments to TikTok as match-ready custom audiences, reads only the records changed since the last run, 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 from your MySQL tables, delivered each time the read runs.

    Targeting that mirrors your live segment out of your MySQL tables, delivered each time the read runs without read load on the database climbing.

    Match feedback on match quality on TikTok from TikTok's Custom Audience API each run, tied back to your MySQL tables.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /dmp/custom_audience source=mysql.segments
    3. id_schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. action "add" · audience_id "aud_72877"
    5. id_list_size 62,567 · matched 48,802
    6. ✓ accepted match=78%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MySQL

    MySQL to Meta Custom Audience

    MySQL to Meta Custom Audience: Signals reads your MySQL tables and keeps Meta audiences…

    Learn more

    from MySQL

    MySQL to Google Customer Match

    MySQL to Google Customer Match: Signals reads your MySQL tables and projects your segments…

    Learn more

    same use case

    ActiveCampaign to TikTok Custom Audience

    ActiveCampaign to TikTok Custom Audience: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    TikTok Custom Audience

    Datahash syncs hashed customer audiences from your CRM, warehouse, or files to TikTok for…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the MySQL TikTok Custom Audience sync run?

    Delivery tracks MySQL, run by application teams on MySQL: a near-real-time or scheduled sync of your MySQL tables feeds TikTok on that cadence. Each run reads only the records changed since the last run, so targeting that mirrors your live segment holds up on match quality on TikTok. The live debugger confirms every delivery inline.

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

    Coverage of hashed identifiers across your MySQL tables decides it, and application teams on MySQL own that inside MySQL. A live email or phone matches into TikTok; neither, and it will not. First-run feedback flags match quality on TikTok, which application teams on MySQL then raise inside your MySQL tables.

    NEXT STEP

    MySQL to TikTok Custom Audience, in production this week.

    Talk to our team All MySQL use cases