Jump to a popular page, or start typing.

    CONNECTIONS / Dropbox / Dropbox to Snap Custom Audience

    Your Dropbox files, wired to Snapchat audience matching.

    Signals reads your Dropbox files through read-only OAuth access to the Dropbox folder you name, then matches your segments into Snapchat for targeting and customer suppression so Snapchat sees match-ready audiences without an export.

    dropbox -> snap-custom-audience :: live

    1. ● dropbox → snap.audience :: live
    2. > read segments rows=18,948
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 14,400 matched

    WHAT THIS ENABLES

    Dropbox to Snapchat Custom Audience

    Snapchat Custom Audience for Dropbox: Signals matches your segments into Snapchat for targeting and customer suppression straight from your Dropbox files, hashed and consent-screened each time a new file lands.

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

    WHAT FLOWS WHERE

    Dropbox to Custom Audience, mapped.

    Each sync hands the customer segments from your Dropbox files to Signals, which hashes and filters every record, then Snapchat's Custom Audiences API logs the match-ready audiences for list sizing on Snapchat.

    Each sync hands the customer segments from your Dropbox files to Signals, which hashes and filters every record, then Snapchat's Custom Audiences API logs 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 Dropbox folders and shared exports.

    Teams dropping exports in Dropbox who need Snapchat audiences that stay in step as the segment rebuilds out of Dropbox files.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Read-only OAuth access to the Dropbox folder you name, mapped to Snapchat's Custom Audiences API and tuned for list sizing on Snapchat.

    2. Map

      Columns from your Dropbox 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 Dropbox 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 Dropbox files, delivered each time a new file lands.

    Audiences that rebuild as the segment does out of your Dropbox 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 Dropbox files.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /audience_match source=dropbox.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. external_audience_id "aud_56415"
    5. id_list_size 18,948 · matched 14,400
    6. ✓ accepted match=76%
    FAQ

    Asked on almost every call.

    How often does the Dropbox Snap Custom Audience sync run?

    Delivery tracks Dropbox, run by teams dropping exports in Dropbox: a near-real-time or scheduled sync of your Dropbox files feeds Snapchat on that cadence. Each run processes only the newly dropped file, so audiences that rebuild as the segment does holds up on list sizing on Snapchat. The live debugger confirms every delivery inline.

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

    Coverage of hashed identifiers across your Dropbox files decides it, and teams dropping exports in Dropbox own that inside Dropbox. A live email or phone matches into Snapchat; neither, and it will not. First-run feedback flags list sizing on Snapchat, which teams dropping exports in Dropbox then raise inside your Dropbox files.

    NEXT STEP

    Dropbox to Snap Custom Audience, in production this week.