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

    CONNECTIONS / FTP / FTP to TikTok Custom Audience

    Your FTP drops, wired to TikTok audience targeting.

    Signals reads your FTP drops through read-only credentials scoped to the SFTP path 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

    ftp -> tiktok-custom-audience :: live

    1. ● ftp → tiktok.audience :: live
    2. > read segments rows=71,672
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 60,204 matched

    WHAT THIS ENABLES

    FTP to TikTok Custom Audience

    FTP to TikTok Custom Audience: your FTP drops, 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.

    • Signals delivers first-party segments to TikTok as match-ready custom audiences, reading your FTP drops each time a new file lands.
    • Targeting that mirrors your live segment, with no export step out of your FTP drops.

    WHAT FLOWS WHERE

    FTP to Custom Audience, mapped.

    Signals reads the customer segments from your FTP drops each time a new file lands, 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 FTP drops each time a new file lands, 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 FTP and SFTP drop folders.

    Teams exporting nightly to SFTP who need TikTok custom audiences mirroring the segment your data team publishes out of FTP drops.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only credentials scoped to the SFTP path you name, mapped to TikTok's Custom Audience API and tuned for match quality on TikTok.

    2. Map

      Columns from your FTP drops align to TikTok's Custom Audience API in the visual mapper, hashed as the file lands and checked for match quality on TikTok.

    3. Deliver

      Each time a new file lands, Signals reads your FTP drops and delivers first-party segments to TikTok as match-ready custom audiences, processes only the newly dropped file, 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 FTP drops, delivered each time a new file lands.

    Targeting that mirrors your live segment out of your FTP drops, delivered each time a new file lands without transfer overhead climbing.

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

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /dmp/custom_audience source=ftp.segments
    3. id_schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. action "add" · audience_id "aud_60653"
    5. id_list_size 71,672 · matched 60,204
    6. ✓ accepted match=84%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from FTP

    FTP to Meta Custom Audience

    FTP to Meta Custom Audience: your FTP drops, hashed and consent-checked, feed Meta as…

    Learn more

    from FTP

    FTP to Google Customer Match

    FTP to Google Customer Match: your FTP drops, hashed and consent-checked, feed Google Ads…

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

    You set the cadence, from near-real-time to a nightly FTP sync of your FTP drops into TikTok. Since Signals processes only the newly dropped file, TikTok custom audiences mirroring the segment your data team publishes keeps pace and teams exporting nightly to SFTP watch match quality on TikTok. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your FTP drops, which teams exporting nightly to SFTP control, not FTP 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 exporting nightly to SFTP tune against.

    NEXT STEP

    FTP to TikTok Custom Audience, in production this week.

    Talk to our team All FTP use cases