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

    CONNECTIONS / WordPress / WordPress to Pinterest CAPI

    Your WordPress orders, wired to Pinterest's Conversions API.

    Connect WordPress and point Signals at your WordPress orders; it credits store sales back to the Pinterest discovery that inspired them as orders complete, hashed and consent-checked for Pinterest.

    Talk to our team Explore the setup

    wordpress -> pinterest-capi :: live

    1. ● wordpress → pinterest.capi :: live
    2. > read web_orders rows=54,834
    3. hash sha256(email,phone) consent=filtered
    4. route pinterest deliver
    5. ✓ delivered · 48,254 matched

    WHAT THIS ENABLES

    WordPress to Pinterest Conversions API

    WordPress to Pinterest Conversions API: Signals reads your WordPress orders and credits store sales back to the Pinterest discovery that inspired them, hashed and consent-checked as orders complete.

    • On-site purchase and checkout events from your WordPress orders activated for Pinterest, as Signals credits store sales back to the Pinterest discovery that inspired them.
    • Purchase signal linking Pinterest discovery to checkout, drawn from your WordPress orders by content-led merchants on WordPress.

    WHAT FLOWS WHERE

    WordPress to Pinterest CAPI, mapped.

    Signals reads the on-site purchase and checkout events from your WordPress orders as orders complete, hashes and screens each record, and posts the web conversions to Pinterest's Conversions API, keeping upper-funnel attribution in view.

    Signals reads the on-site purchase and checkout events from your WordPress orders as orders complete, hashes and screens each record, and posts the web conversions to Pinterest's Conversions API, keeping upper-funnel attribution in view.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Brands whose buyers discover on Pinterest and buy later, with the records already in WordPress orders, users, and form entries.

    Content-led merchants on WordPress activating Pinterest's Conversions API 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 Pinterest's Conversions API, sized for upper-funnel attribution.

    2. Map

      Signals reads your WordPress orders, and its columns map to Pinterest's Conversions API in the visual mapper, hashed and checked for upper-funnel attribution.

    3. Deliver

      On each run, Signals pulls your WordPress orders, credits store sales back to the Pinterest discovery that inspired them, and sends only the orders that changed, with upper-funnel attribution in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Purchase signal linking Pinterest discovery to checkout on every run, as Signals reads your WordPress orders and sends only the orders that changed.

    Checkout sales tied to Pinterest discovery from your WordPress orders, with API call volume steady because Signals sends only the orders that changed.

    A per-run match report from Pinterest's Conversions API on upper-funnel attribution, straight out of your WordPress orders.

    ON THE WIRE

    What Pinterest CAPI actually receives.

    signals :: wordpress.pinterest-capi :: wire

    1. ● signals :: event payload
    2. > POST /events source=wordpress.web_orders
    3. event_name "checkout" · action_source "web" · event_time 1784327227
    4. em sha256 "7bd403…"
    5. value 1221.00 · currency SAR
    6. ✓ accepted match=88%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from WordPress

    WordPress to Meta CAPI

    WordPress to Meta Conversions API: Signals reads your WordPress orders and sends every…

    Learn more

    from WordPress

    WordPress to Meta CTM

    WordPress to Meta Click-to-Message: Signals reads your WordPress orders and credits orders…

    Learn more

    same use case

    BigCommerce to Pinterest CAPI

    Pinterest Conversions API for BigCommerce: Signals credits store sales back to the…

    Learn more

    generic

    Pinterest CAPI

    Datahash implements Pinterest Conversions API with dedupe against the Pinterest Tag and…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the WordPress Pinterest CAPI sync run?

    Delivery tracks WordPress, run by content-led merchants on WordPress: a near-real-time or scheduled sync of your WordPress orders feeds Pinterest on that cadence. Each run sends only the orders that changed, so checkout sales tied to Pinterest discovery holds up on upper-funnel attribution. The live debugger confirms every delivery inline.

    What match rate should a WordPress-sourced Pinterest CAPI 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 Pinterest; one missing both cannot. First-run feedback from Conversions API pinpoints upper-funnel attribution, the number content-led merchants on WordPress tune against.

    NEXT STEP

    WordPress to Pinterest CAPI, in production this week.

    Talk to our team All WordPress use cases