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

    CONNECTIONS / IBM DB2 / IBM DB2 to TikTok Custom Audience

    Db2 tables into TikTok, built for TikTok audience targeting.

    Connect IBM DB2 and point Signals at your Db2 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

    ibm-db2 -> tiktok-custom-audience :: live

    1. ● ibm db2 → tiktok.audience :: live
    2. > read segments rows=36,237
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 26,453 matched

    WHAT THIS ENABLES

    IBM DB2 to TikTok Custom Audience

    TikTok Custom Audience for IBM DB2: Signals delivers first-party segments to TikTok as match-ready custom audiences straight from your Db2 tables, hashed and consent-screened each time the read runs.

    • Customer segments from your Db2 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 Db2 tables by enterprise data teams on IBM DB2.

    WHAT FLOWS WHERE

    IBM DB2 to Custom Audience, mapped.

    Signals reads the customer segments from your Db2 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 Db2 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 Db2 tables and views.

    Enterprise data teams on IBM DB2 activating TikTok audience targeting straight from Db2 tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      A scheduled read pulls your Db2 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 Db2 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 Db2 tables and reads only the records changed since the last run.

    Targeting that mirrors your live segment from your Db2 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 Db2 tables.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: ibm-db2.tiktok-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /dmp/custom_audience source=ibm-db2.segments
    3. id_schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. action "add" · audience_id "aud_81474"
    5. id_list_size 36,237 · matched 26,453
    6. ✓ accepted match=73%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from IBM DB2

    IBM DB2 to Meta Custom Audience

    Meta Custom Audience for IBM DB2: Signals keeps Meta audiences synced as adds and removals…

    Learn more

    from IBM DB2

    IBM DB2 to Google Customer Match

    Google Customer Match for IBM DB2: Signals projects your segments into Google Ads as…

    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 IBM DB2 TikTok Custom Audience sync run?

    The pace follows your Db2 tables: Signals sends changes from IBM DB2 to TikTok each time the read runs. Because it reads only the records changed since the last run, TikTok custom audiences mirroring the segment your data team publishes stays current while enterprise data teams on IBM DB2 keep match quality on TikTok in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    IBM DB2 to TikTok Custom Audience, in production this week.

    Talk to our team All IBM DB2 use cases