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

    CONNECTIONS / Microsoft SQL Server / SQL Server to TikTok Custom Audience

    Your SQL Server tables, wired to TikTok audience targeting.

    Connect SQL Server and point Signals at your SQL Server tables; it delivers first-party segments to TikTok as match-ready custom audiences each time the read runs, hashed and consent-checked for TikTok.

    Talk to our team Explore the setup

    microsoft-sql-server -> tiktok-custom-audience :: live

    1. ● sql server → tiktok.audience :: live
    2. > read segments rows=71,808
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 52,420 matched

    WHAT THIS ENABLES

    SQL Server to TikTok Custom Audience

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

    • Customer segments from your SQL Server tables activated for TikTok, as Signals delivers first-party segments to TikTok as match-ready custom audiences.
    • TikTok custom audiences mirroring the segment your data team publishes, drawn from your SQL Server tables by data teams running SQL Server.

    WHAT FLOWS WHERE

    Microsoft SQL Server to Custom Audience, mapped.

    Signals reads the customer segments from your SQL Server 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 SQL Server 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, with the records already in SQL Server tables, views, and indexed views.

    Data teams running SQL Server activating TikTok audience targeting straight from SQL Server tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the SQL Server tables you name to feed TikTok's Custom Audience API, sized for match quality on TikTok.

    2. Map

      A scheduled read pulls your SQL Server 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

      On each run, Signals pulls your SQL Server tables, delivers first-party segments to TikTok as match-ready custom audiences, and reads only the records changed since the last run, with match quality on TikTok 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, as Signals reads your SQL Server tables and reads only the records changed since the last run.

    Targeting that mirrors your live segment from your SQL Server tables, with read load on the database steady because Signals reads only the records changed since the last run.

    A per-run match report from TikTok's Custom Audience API on match quality on TikTok, straight out of your SQL Server tables.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: microsoft-sql-server.tiktok-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /dmp/custom_audience source=microsoft-sql-server.segments
    3. id_schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. action "add" · audience_id "aud_53116"
    5. id_list_size 71,808 · matched 52,420
    6. ✓ accepted match=73%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Microsoft SQL Server

    SQL Server to Meta Custom Audience

    SQL Server to Meta Custom Audience: Signals reads your SQL Server tables and keeps Meta…

    Learn more

    from Microsoft SQL Server

    SQL Server to Google Customer Match

    SQL Server to Google Customer Match: Signals reads your SQL Server tables and projects your…

    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 SQL Server TikTok Custom Audience sync run?

    Delivery tracks SQL Server, run by data teams running SQL Server: a near-real-time or scheduled sync of your SQL Server 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 SQL Server-sourced TikTok Custom Audience batch expect?

    Match rate follows identifier coverage in your SQL Server tables, which data teams running SQL Server control, not SQL Server itself. A record with a current hashed email or phone matches for TikTok; one missing both cannot. First-run feedback from Custom Audience API pinpoints match quality on TikTok, the number data teams running SQL Server tune against.

    NEXT STEP

    SQL Server to TikTok Custom Audience, in production this week.

    Talk to our team All Microsoft SQL Server use cases