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

    CONNECTIONS / GCS / GCS to TikTok Custom Audience

    Your GCS objects, wired to TikTok audience targeting.

    Connect GCS and point Signals at your GCS 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

    google-cloud-storage -> tiktok-custom-audience :: live

    1. ● gcs → tiktok.audience :: live
    2. > read segments rows=73,265
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 63,741 matched

    WHAT THIS ENABLES

    GCS to TikTok Custom Audience

    GCS to TikTok Custom Audience: your GCS 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 GCS 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 GCS objects by data teams landing exports in GCS.

    WHAT FLOWS WHERE

    GCS to Custom Audience, mapped.

    Each sync hands the customer segments from your GCS 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 GCS 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 Google Cloud Storage buckets and objects.

    Data teams landing exports in GCS activating TikTok audience targeting straight from GCS objects.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

      Signals picks up your GCS 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 GCS 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 GCS objects and processes only the newly dropped file.

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

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: google-cloud-storage.tiktok-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /dmp/custom_audience source=google-cloud-storage.segments
    3. id_schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. action "add" · audience_id "aud_54352"
    5. id_list_size 73,265 · matched 63,741
    6. ✓ accepted match=87%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from GCS

    GCS to Meta Custom Audience

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

    Learn more

    from GCS

    GCS to Google Customer Match

    GCS to Google Customer Match: your GCS objects, 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 GCS TikTok Custom Audience sync run?

    The pace follows your GCS objects: Signals sends changes from GCS to TikTok each time a new file lands. Because it processes only the newly dropped file, TikTok custom audiences mirroring the segment your data team publishes stays current while data teams landing exports in GCS keep match quality on TikTok in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    GCS to TikTok Custom Audience, in production this week.

    Talk to our team All GCS use cases