Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / MySQL / MySQL to Snap Custom Audience

    From MySQL tables to Snapchat audience matching.

    Signals reads your MySQL tables through a read-only database user scoped to the MySQL tables you name, then matches your segments into Snapchat for targeting and customer suppression so Snapchat sees match-ready audiences without an export.

    Talk to our team Explore the setup

    mysql -> snap-custom-audience :: live

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

    WHAT THIS ENABLES

    MySQL to Snapchat Custom Audience

    MySQL to Snapchat Custom Audience: Signals reads your MySQL tables and matches your segments into Snapchat for targeting and customer suppression, hashed and consent-checked each time the read runs.

    • Signals matches your segments into Snapchat for targeting and customer suppression, reading your MySQL tables each time the read runs.
    • Audiences that rebuild as the segment does, with no export step out of your MySQL tables.

    WHAT FLOWS WHERE

    MySQL to Custom Audience, mapped.

    Signals reads the customer segments from your MySQL tables each time the read runs, 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 MySQL tables each time the read runs, 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, working out of MySQL tables and views.

    Application teams on MySQL who need Snapchat audiences that stay in step as the segment rebuilds out of MySQL tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the MySQL tables you name, mapped to Snapchat's Custom Audiences API and tuned for list sizing on Snapchat.

    2. Map

      Columns from your MySQL tables align to Snapchat's Custom Audiences API in the visual mapper, hashed as the read runs and checked for list sizing on Snapchat.

    3. Deliver

      Each time the read runs, Signals reads your MySQL tables and matches your segments into Snapchat for targeting and customer suppression, reads only the records changed since the last run, 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 MySQL tables, delivered each time the read runs.

    Audiences that rebuild as the segment does out of your MySQL tables, delivered each time the read runs without read load on the database climbing.

    Match feedback on list sizing on Snapchat from Snapchat's Custom Audiences API each run, tied back to your MySQL tables.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /audience_match source=mysql.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. external_audience_id "aud_52999"
    5. id_list_size 18,932 · matched 14,767
    6. ✓ accepted match=78%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MySQL

    MySQL to Meta Custom Audience

    MySQL to Meta Custom Audience: Signals reads your MySQL tables and keeps Meta audiences…

    Learn more

    from MySQL

    MySQL to Google Customer Match

    MySQL to Google Customer Match: Signals reads your MySQL tables and projects your segments…

    Learn more

    same use case

    ActiveCampaign to Snap Custom Audience

    ActiveCampaign to Snapchat Custom Audience: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Snap Custom Audience

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

    Learn more
    FAQ

    Asked on almost every call.

    How often does the MySQL Snap Custom Audience sync run?

    Delivery tracks MySQL, run by application teams on MySQL: a near-real-time or scheduled sync of your MySQL tables feeds Snapchat on that cadence. Each run reads only the records changed since the last run, 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 MySQL-sourced Snap Custom Audience batch expect?

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

    NEXT STEP

    MySQL to Snap Custom Audience, in production this week.

    Talk to our team All MySQL use cases