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

    CONNECTIONS / Website / Website to Pinterest CAPI

    From Website events to Pinterest's Conversions API.

    Connect Website and point Signals at your website events; it credits store sales back to the Pinterest discovery that inspired them as each event fires, hashed and consent-checked for Pinterest.

    Talk to our team Explore the setup

    website -> pinterest-capi :: live

    1. ● website → pinterest.capi :: live
    2. > read web_orders rows=40,298
    3. hash sha256(email,phone) consent=filtered
    4. route pinterest deliver
    5. ✓ delivered · 33,850 matched

    WHAT THIS ENABLES

    Website to Pinterest Conversions API

    Website to Pinterest Conversions API: your website events, hashed and consent-checked, feed Pinterest as Signals credits store sales back to the Pinterest discovery that inspired them as each event fires.

    • On-site purchase and checkout events from your website events 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 website events by web teams instrumenting the site.

    WHAT FLOWS WHERE

    Website to Pinterest CAPI, mapped.

    Signals receives the on-site purchase and checkout events from your website events; Signals hashes and consent-screens each record before Pinterest's Conversions API accepts the web conversions for upper-funnel attribution.

    Signals receives the on-site purchase and checkout events from your website events; Signals hashes and consent-screens each record before Pinterest's Conversions API accepts the web conversions for upper-funnel attribution.

    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 on-site pixel and tag events.

    Web teams instrumenting the site activating Pinterest's Conversions API straight from website events.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A Signals tag or pixel on your site to feed Pinterest's Conversions API, sized for upper-funnel attribution.

    2. Map

      Signals receives your website events, 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 website events, credits store sales back to the Pinterest discovery that inspired them, and forwards each event as it arrives, 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 website events and forwards each event as it arrives.

    Checkout sales tied to Pinterest discovery from your website events, with event volume steady because Signals forwards each event as it arrives.

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

    ON THE WIRE

    What Pinterest CAPI actually receives.

    signals :: website.pinterest-capi :: wire

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

    Adjacent moves on the same stack.

    from Website

    Website to Meta CAPI

    Website to Meta Conversions API: your website events, hashed and consent-checked, feed Meta…

    Learn more

    from Website

    Website to Meta CTM

    Website to Meta Click-to-Message: your website events, hashed and consent-checked, feed…

    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 Website Pinterest CAPI sync run?

    You set the cadence, from near-real-time to a nightly Website sync of your website events into Pinterest. Since Signals forwards each event as it arrives, purchase signal linking Pinterest discovery to checkout keeps pace and web teams instrumenting the site watch upper-funnel attribution. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Website-sourced Pinterest CAPI batch expect?

    In Website, match rate tracks the email and phone quality your website events carry. Clean identifiers land for Pinterest; blank ones never will. The first Conversions API report shows web teams instrumenting the site where upper-funnel attribution needs work, a data-quality task handled in Website.

    NEXT STEP

    Website to Pinterest CAPI, in production this week.

    Talk to our team All Website use cases