Jump to a popular page, or start typing.

    CONNECTIONS / File drops / File drops to Snap Custom Audience

    Your file drops, wired to Snapchat audience matching.

    Connect File drops and point Signals at your file drops; it matches your segments into Snapchat for targeting and customer suppression each time a new file lands, hashed and consent-checked for Snapchat.

    files -> snap-custom-audience :: live

    1. ● file drops → snap.audience :: live
    2. > read segments rows=63,201
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 49,929 matched

    WHAT THIS ENABLES

    File drops to Snapchat Custom Audience

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

    • Customer segments from your file drops 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 file drops by teams landing POS and back-office exports as files.

    WHAT FLOWS WHERE

    File drops to Custom Audience, mapped.

    Signals reads the customer segments from your file drops each time a new file lands, hashes and screens each record, and posts the match-ready audiences to Snapchat's Custom Audiences API, keeping list sizing on Snapchat in view.

    Signals reads the customer segments from your file drops each time a new file lands, hashes and screens each record, and posts the match-ready audiences to Snapchat's Custom Audiences API, keeping list sizing on Snapchat in view.

    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 POS, SFTP, S3, and GCS file drops.

    Teams landing POS and back-office exports as files activating Snapchat audience matching straight from file drops.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only access to the SFTP, S3, or GCS drop you name to feed Snapchat's Custom Audiences API, sized for list sizing on Snapchat.

    2. Map

      Signals picks up your file drops, 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 file drops, matches your segments into Snapchat for targeting and customer suppression, and processes only the newly dropped file, 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 file drops and processes only the newly dropped file.

    Audiences that rebuild as the segment does from your file drops, with transfer overhead steady because Signals processes only the newly dropped file.

    A per-run match report from Snapchat's Custom Audiences API on list sizing on Snapchat, straight out of your file drops.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /audience_match source=files.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. external_audience_id "aud_79248"
    5. id_list_size 63,201 · matched 49,929
    6. ✓ accepted match=79%
    FAQ

    Asked on almost every call.

    How often does the File drops Snap Custom Audience sync run?

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

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

    In File drops, match rate tracks the email and phone quality your file drops carry. Clean identifiers land for Snapchat; blank ones never will. The first Custom Audiences API report shows teams landing POS and back-office exports as files where list sizing on Snapchat needs work, a data-quality task handled in File drops.

    NEXT STEP

    File drops to Snap Custom Audience, in production this week.