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

    CONNECTIONS / Cockroach / Cockroach to Snap Custom Audience

    From Cockroach tables to Snapchat audience matching.

    Connect Cockroach and point Signals at your Cockroach tables; it matches your segments into Snapchat for targeting and customer suppression each time the read runs, hashed and consent-checked for Snapchat.

    Talk to our team Explore the setup

    cockroach -> snap-custom-audience :: live

    1. ● cockroach → snap.audience :: live
    2. > read segments rows=40,170
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 31,734 matched

    WHAT THIS ENABLES

    Cockroach to Snapchat Custom Audience

    Snapchat Custom Audience for Cockroach: Signals matches your segments into Snapchat for targeting and customer suppression straight from your Cockroach tables, hashed and consent-screened each time the read runs.

    • Customer segments from your Cockroach tables activated for Snapchat, as Signals matches your segments into Snapchat for targeting and customer suppression.
    • Snapchat audiences that stay in step as the segment rebuilds, drawn from your Cockroach tables by platform teams running CockroachDB.

    WHAT FLOWS WHERE

    Cockroach to Custom Audience, mapped.

    A scheduled read pulls the customer segments from your Cockroach tables; Signals hashes and consent-screens each record before Snapchat's Custom Audiences API accepts the match-ready audiences for list sizing on Snapchat.

    A scheduled read pulls the customer segments from your Cockroach tables; Signals hashes and consent-screens each record before Snapchat's Custom Audiences API accepts the match-ready audiences for list sizing on Snapchat.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Snapchat advertisers building lookalikes and excluding current buyers, with the records already in Cockroach tables and secondary indexes.

    Platform teams running CockroachDB activating Snapchat audience matching straight from Cockroach tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the Cockroach tables you name to feed Snapchat's Custom Audiences API, sized for list sizing on Snapchat.

    2. Map

      A scheduled read pulls your Cockroach tables, and its columns map to Snapchat's Custom Audiences API in the visual mapper, hashed and checked for list sizing on Snapchat.

    3. Deliver

      On each run, Signals pulls your Cockroach tables, matches your segments into Snapchat for targeting and customer suppression, and reads only the records changed since the last run, with list sizing on Snapchat in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Snapchat audiences that stay in step as the segment rebuilds on every run, as Signals reads your Cockroach tables and reads only the records changed since the last run.

    Audiences that rebuild as the segment does from your Cockroach 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 Snapchat's Custom Audiences API on list sizing on Snapchat, straight out of your Cockroach tables.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: cockroach.snap-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /audience_match source=cockroach.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. external_audience_id "aud_68050"
    5. id_list_size 40,170 · matched 31,734
    6. ✓ accepted match=79%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Cockroach

    Cockroach to Meta Custom Audience

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

    Learn more

    from Cockroach

    Cockroach to Google Customer Match

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

    Learn more

    same use case

    ActiveCampaign to Snap Custom Audience

    ActiveCampaign to Snapchat Custom Audience: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Snap Custom Audience

    Build and refresh Snap audiences from your CRM, warehouse, or SingleView with hashed…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Cockroach Snap Custom Audience sync run?

    The pace follows your Cockroach tables: Signals sends changes from Cockroach to Snapchat each time the read runs. Because it reads only the records changed since the last run, Snapchat audiences that stay in step as the segment rebuilds stays current while platform teams running CockroachDB keep list sizing on Snapchat in view. Delivery needs no export and no manual upload.

    What match rate should a Cockroach-sourced Snap Custom Audience batch expect?

    Coverage of hashed identifiers across your Cockroach tables decides it, and platform teams running CockroachDB own that inside Cockroach. A live email or phone matches into Snapchat; neither, and it will not. First-run feedback flags list sizing on Snapchat, which platform teams running CockroachDB then raise inside your Cockroach tables.

    NEXT STEP

    Cockroach to Snap Custom Audience, in production this week.

    Talk to our team All Cockroach use cases