Jump to a popular page, or start typing.

    CONNECTIONS / OVHcloud / OVHcloud to Snap Custom Audience

    From OVHcloud Object Storage files to Snapchat audience matching.

    Signals reads your OVHcloud Object Storage files through a read-only S3 key scoped to the OVHcloud container you name, then matches your segments into Snapchat for targeting and customer suppression so Snapchat sees match-ready audiences without an export.

    ovhcloud -> snap-custom-audience :: live

    1. ● ovhcloud → snap.audience :: live
    2. > read segments rows=35,319
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 28,962 matched

    WHAT THIS ENABLES

    OVHcloud to Snapchat Custom Audience

    OVHcloud to Snapchat Custom Audience: your OVHcloud Object Storage files, hashed and consent-checked, feed Snapchat as Signals matches your segments into Snapchat for targeting and customer suppression each time a new file lands.

    • Signals matches your segments into Snapchat for targeting and customer suppression, reading your OVHcloud Object Storage files each time a new file lands.
    • Audiences that rebuild as the segment does, with no export step out of your OVHcloud Object Storage files.

    WHAT FLOWS WHERE

    OVHcloud to Custom Audience, mapped.

    Signals picks up the customer segments from your OVHcloud Object Storage files; Signals hashes and consent-screens each record before Snapchat's Custom Audiences API accepts the match-ready audiences for list sizing on Snapchat.

    Signals picks up the customer segments from your OVHcloud Object Storage files; 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, working out of OVHcloud Object Storage containers and objects.

    Teams on OVHcloud Object Storage who need Snapchat audiences that stay in step as the segment rebuilds out of OVHcloud Object Storage files.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only S3 key scoped to the OVHcloud container you name, mapped to Snapchat's Custom Audiences API and tuned for list sizing on Snapchat.

    2. Map

      Columns from your OVHcloud Object Storage files align to Snapchat's Custom Audiences API in the visual mapper, hashed as the file lands and checked for list sizing on Snapchat.

    3. Deliver

      Each time a new file lands, Signals reads your OVHcloud Object Storage files and matches your segments into Snapchat for targeting and customer suppression, processes only the newly dropped file, with list sizing on Snapchat watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Snapchat audiences that stay in step as the segment rebuilds from your OVHcloud Object Storage files, delivered each time a new file lands.

    Audiences that rebuild as the segment does out of your OVHcloud Object Storage files, delivered each time a new file lands without transfer overhead climbing.

    Match feedback on list sizing on Snapchat from Snapchat's Custom Audiences API each run, tied back to your OVHcloud Object Storage files.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /audience_match source=ovhcloud.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. external_audience_id "aud_53787"
    5. id_list_size 35,319 · matched 28,962
    6. ✓ accepted match=82%
    FAQ

    Asked on almost every call.

    How often does the OVHcloud Snap Custom Audience sync run?

    You set the cadence, from near-real-time to a nightly OVHcloud sync of your OVHcloud Object Storage files into Snapchat. Since Signals processes only the newly dropped file, Snapchat audiences that stay in step as the segment rebuilds keeps pace and teams on OVHcloud Object Storage watch list sizing on Snapchat. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your OVHcloud Object Storage files, which teams on OVHcloud Object Storage control, not OVHcloud itself. A record with a current hashed email or phone matches for Snapchat; one missing both cannot. First-run feedback from Custom Audiences API pinpoints list sizing on Snapchat, the number teams on OVHcloud Object Storage tune against.

    NEXT STEP

    OVHcloud to Snap Custom Audience, in production this week.