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

    CONNECTIONS / CouchDB / CouchDB to TikTok Custom Audience

    CouchDB documents into TikTok, built for TikTok audience targeting.

    Signals reads your CouchDB documents through a read-only database user scoped to the CouchDB documents 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

    couchdb -> tiktok-custom-audience :: live

    1. ● couchdb → tiktok.audience :: live
    2. > read segments rows=29,933
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 23,348 matched

    WHAT THIS ENABLES

    CouchDB to TikTok Custom Audience

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

    • Signals delivers first-party segments to TikTok as match-ready custom audiences, reading your CouchDB documents each time the read runs.
    • Targeting that mirrors your live segment, with no export step out of your CouchDB documents.

    WHAT FLOWS WHERE

    CouchDB to Custom Audience, mapped.

    Each sync hands the customer segments from your CouchDB documents 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 CouchDB documents 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, working out of CouchDB documents and map/reduce views.

    Application teams running CouchDB who need TikTok custom audiences mirroring the segment your data team publishes out of CouchDB documents.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the CouchDB documents you name, mapped to TikTok's Custom Audience API and tuned for match quality on TikTok.

    2. Map

      Columns from your CouchDB documents align to TikTok's Custom Audience API in the visual mapper, hashed as the read runs and checked for match quality on TikTok.

    3. Deliver

      Each time the read runs, Signals reads your CouchDB documents and delivers first-party segments to TikTok as match-ready custom audiences, reads only the records changed since the last run, 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 CouchDB documents, delivered each time the read runs.

    Targeting that mirrors your live segment out of your CouchDB documents, delivered each time the read runs without read load on the database climbing.

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

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /dmp/custom_audience source=couchdb.segments
    3. id_schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. action "add" · audience_id "aud_50819"
    5. id_list_size 29,933 · matched 23,348
    6. ✓ accepted match=78%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from CouchDB

    CouchDB to Meta Custom Audience

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

    Learn more

    from CouchDB

    CouchDB to Google Customer Match

    Google Customer Match for CouchDB: 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 CouchDB TikTok Custom Audience sync run?

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

    Coverage of hashed identifiers across your CouchDB documents decides it, and application teams running CouchDB own that inside CouchDB. A live email or phone matches into TikTok; neither, and it will not. First-run feedback flags match quality on TikTok, which application teams running CouchDB then raise inside your CouchDB documents.

    NEXT STEP

    CouchDB to TikTok Custom Audience, in production this week.

    Talk to our team All CouchDB use cases