Jump to a popular page, or start typing.

    CONNECTIONS / WordPress / WordPress to Snap Custom Audience

    Your WordPress orders, wired to Snapchat audience matching.

    Connect WordPress and point Signals at your WordPress orders; it matches your segments into Snapchat for targeting and customer suppression as orders complete, hashed and consent-checked for Snapchat.

    wordpress -> snap-custom-audience :: live

    1. ● wordpress → snap.audience :: live
    2. > read segments rows=57,975
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 45,800 matched

    WHAT THIS ENABLES

    WordPress to Snapchat Custom Audience

    WordPress to Snapchat Custom Audience: Signals reads your WordPress orders and matches your segments into Snapchat for targeting and customer suppression, hashed and consent-checked as orders complete.

    • Customer segments from your WordPress orders 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 WordPress orders by content-led merchants on WordPress.

    WHAT FLOWS WHERE

    WordPress to Custom Audience, mapped.

    Signals reads the customer segments from your WordPress orders as orders complete, 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 WordPress orders as orders complete, 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 WordPress orders, users, and form entries.

    Content-led merchants on WordPress activating Snapchat audience matching straight from WordPress orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped API access to WordPress, reading only your WordPress orders to feed Snapchat's Custom Audiences API, sized for list sizing on Snapchat.

    2. Map

      Signals reads your WordPress orders, 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 WordPress orders, matches your segments into Snapchat for targeting and customer suppression, and sends only the orders that changed, 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 WordPress orders and sends only the orders that changed.

    Audiences that rebuild as the segment does from your WordPress orders, with API call volume steady because Signals sends only the orders that changed.

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

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /audience_match source=wordpress.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. external_audience_id "aud_70212"
    5. id_list_size 57,975 · matched 45,800
    6. ✓ accepted match=79%
    FAQ

    Asked on almost every call.

    How often does the WordPress Snap Custom Audience sync run?

    Delivery tracks WordPress, run by content-led merchants on WordPress: a near-real-time or scheduled sync of your WordPress orders feeds Snapchat on that cadence. Each run sends only the orders that changed, 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 WordPress-sourced Snap Custom Audience batch expect?

    Match rate follows identifier coverage in your WordPress orders, which content-led merchants on WordPress control, not WordPress 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 content-led merchants on WordPress tune against.

    NEXT STEP

    WordPress to Snap Custom Audience, in production this week.