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

    CONNECTIONS / Wasabi / Wasabi to TikTok Custom Audience

    Wasabi objects into TikTok, built for TikTok audience targeting.

    Connect Wasabi and point Signals at your Wasabi objects; it delivers first-party segments to TikTok as match-ready custom audiences each time a new file lands, hashed and consent-checked for TikTok.

    Talk to our team Explore the setup

    wasabi -> tiktok-custom-audience :: live

    1. ● wasabi → tiktok.audience :: live
    2. > read segments rows=66,434
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 49,826 matched

    WHAT THIS ENABLES

    Wasabi to TikTok Custom Audience

    Wasabi to TikTok Custom Audience: your Wasabi objects, hashed and consent-checked, feed TikTok as Signals delivers first-party segments to TikTok as match-ready custom audiences each time a new file lands.

    • Customer segments from your Wasabi objects 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 Wasabi objects by teams archiving to Wasabi.

    WHAT FLOWS WHERE

    Wasabi to Custom Audience, mapped.

    Each sync hands the customer segments from your Wasabi objects to Signals, which hashes and filters every record, then TikTok's Custom Audience API logs the match-ready audiences for match quality on TikTok.

    Each sync hands the customer segments from your Wasabi objects to Signals, which hashes and filters every record, then TikTok's Custom Audience API logs the match-ready audiences for match quality on TikTok.

    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 Wasabi hot-storage buckets and objects.

    Teams archiving to Wasabi activating TikTok audience targeting straight from Wasabi objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only key scoped to the Wasabi bucket you name to feed TikTok's Custom Audience API, sized for match quality on TikTok.

    2. Map

      Signals picks up your Wasabi objects, 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 Wasabi objects, delivers first-party segments to TikTok as match-ready custom audiences, and processes only the newly dropped file, 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 Wasabi objects and processes only the newly dropped file.

    Targeting that mirrors your live segment from your Wasabi objects, with transfer overhead steady because Signals processes only the newly dropped file.

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

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /dmp/custom_audience source=wasabi.segments
    3. id_schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. action "add" · audience_id "aud_63210"
    5. id_list_size 66,434 · matched 49,826
    6. ✓ accepted match=75%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Wasabi

    Wasabi to Meta Custom Audience

    Wasabi to Meta Custom Audience: your Wasabi objects, hashed and consent-checked, feed Meta…

    Learn more

    from Wasabi

    Wasabi to Google Customer Match

    Wasabi to Google Customer Match: your Wasabi objects, hashed and consent-checked, feed…

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

    Delivery tracks Wasabi, run by teams archiving to Wasabi: a near-real-time or scheduled sync of your Wasabi objects feeds TikTok on that cadence. Each run processes only the newly dropped file, 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 Wasabi-sourced TikTok Custom Audience batch expect?

    Match rate follows identifier coverage in your Wasabi objects, which teams archiving to Wasabi control, not Wasabi 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 teams archiving to Wasabi tune against.

    NEXT STEP

    Wasabi to TikTok Custom Audience, in production this week.

    Talk to our team All Wasabi use cases