Jump to a popular page, or start typing.

    Snap Custom Audience

    Snap Custom Audiences, refreshed automatically.

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

    snap.custom-audience :: live

    1. ● snap.custom_audience :: live
    2. > sync segment "repeat_buyers_90d"
    3. rows 184,203 identifiers sha256(em,ph)
    4. snap.custom_audience upserted
    5. ✓ audience refreshed from source of truth
    WHO THIS IS FOR

    Built for the teams that own the number.

    Brands running suppression and lookalike plays on Snap.

    Teams manually re-uploading customer lists to Snap Ads Manager.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Audience source connection to CRM, warehouse, or SingleView.

    2. Segment

      Segment rules applied and identifiers hashed.

    3. Sync

      Scheduled push to Snap with automatic refresh.

    WHAT FLOWS WHERE

    One use case, every source.

    A segment is defined once from your CRM, warehouse, or SingleView, Signals hashes the identifiers and applies the rules, then syncs the audience to Snap and keeps it refreshed on a schedule.

    A segment is defined once from your CRM, warehouse, or SingleView, Signals hashes the identifiers and applies the rules, then syncs the audience to Snap and keeps it refreshed on a schedule.

    WHAT YOU GET

    What ships with this offering.

    Suppression of existing customers from Snap acquisition spend.

    Lookalike seeds built from high-value cohorts.

    Audiences that stay current without manual uploads.

    ON THE WIRE

    What the platform actually receives.

    Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.

    signals :: snap-custom-audience :: wire

    1. ● signals :: audience payload
    2. > POST /v3/segments/{id}/users action=ADD
    3. schema [EMAIL_SHA256, PHONE_SHA256, MOBILE_AD_ID_SHA256]
    4. hashed_email "c4d9…" · hashed_phone_number "2a71…"
    5. rows 184,203 · op upsert
    6. ✓ audience updated · members synced
    FAQ

    Questions your team will ask.

    What identifiers does Snap match on?

    Hashed email, phone, and mobile advertising IDs. Datahash hashes everything before upload and picks the strongest key set your source data supports, whether that source is your CRM, a warehouse table, or SingleView. Segment rules and hashing run in the same step, so the identifiers Snap receives are never exposed as raw customer data at any point in the sync.

    How often do audiences refresh?

    On the schedule you choose, from hourly to weekly. Refreshes send incremental adds and removes, so segments track your source of truth without full re-uploads. This keeps suppression lists and lookalike seeds current as customers convert or churn, without the manual list exports teams used to push to Snap Ads Manager by hand.

    Can the same segment feed Snap and other platforms?

    Yes. A segment defined once in Datahash can sync to Snap, Meta, Google, and TikTok simultaneously, each with its own hashed key handling suited to that platform's audience API. You maintain one segment definition and one refresh schedule instead of separate exports per channel, and updates to the underlying source data propagate to every connected platform on the next sync.

    NEXT STEP

    Live in fifteen minutes. Measurable in a week.

    Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.