Jump to a popular page, or start typing.

    CONNECTIONS / Salesforce / Salesforce to Snap Custom Audience

    Salesforce segments, refreshed automatically into Snap.

    Signals watches the Salesforce report or list view you nominate and keeps the matching Snap audience aligned, hashing identifiers on the way through and pushing only what changed since the last sync.

    salesforce -> snap-custom-audience :: live

    1. ● salesforce → snap.custom_audience :: live
    2. > sync list view won_customers rows=19,204
    3. hash sha256(email,phone)
    4. route snap.custom_audience upsert
    5. ✓ audience refreshed · 14,209 matched

    WHAT THIS ENABLES

    Salesforce to Snapchat Custom Audience

    Salesforce to Snapchat Custom Audience keeps Snap's audience lists synced with the customer segments your Salesforce team already maintains as reports or list views, refreshing adds and removals on a schedule so suppression and lookalike campaigns stay current.

    • Salesforce list views mirrored into Snap Ads Manager without a manual export.
    • Lookalike seeds built from cohorts your Salesforce team already scores as high value.
    • Existing customers suppressed from Snap acquisition spend the moment Salesforce records the change.

    WHAT FLOWS WHERE

    Salesforce to Custom Audience, mapped.

    Salesforce list view changes flow through Signals, which hashes each record and updates the Snap Custom Audience with the corresponding adds and removals.

    Salesforce list view changes flow through Signals, which hashes each record and updates the Snap Custom Audience with the corresponding adds and removals.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Brands running suppression and lookalike plays on Snap from a Salesforce customer base.

    Teams manually re-uploading Salesforce list exports to Snap Ads Manager.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Connected App access, read-only, to the Salesforce report or list view that defines the segment.

    2. Segment

      Segment rules read directly from the Salesforce object, identifiers hashed for upload.

    3. Sync

      Scheduled push to Snap with automatic incremental refresh.

    WHAT YOU GET

    What ships with this use case.

    Suppression of existing Salesforce customers from Snap acquisition spend.

    Lookalike seeds built from high-value cohorts your Salesforce reports already identify.

    Audiences that stay current without a manual re-upload cycle.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /audience_match source=salesforce.list_view
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. external_audience_id "snap_won_customers"
    5. id_list_size 19,204 · matched 14,209
    6. ✓ accepted match=74%
    FAQ

    Asked on almost every call.

    What identifiers does Snap match a Salesforce segment on?

    Hashed email and phone pulled from the Salesforce report or list view you nominate, plus any mobile advertising ID present on the record. Datahash hashes every identifier before it leaves your environment and sends whichever combination the Salesforce data actually supports.

    Can the same Salesforce segment feed Snap and other ad platforms at once?

    Yes. A segment defined once as a Salesforce report or list view can sync to Snap, Meta, Google, and TikTok at the same time, each with its own hashed key handling and refresh schedule, so marketing does not maintain separate segment logic for every platform.

    NEXT STEP

    Salesforce to Snap Custom Audience, in production this week.