Jump to a popular page, or start typing.

    Pinterest CAPI

    Pinterest CAPI, live in your ad account.

    Datahash implements Pinterest Conversions API with dedupe against the Pinterest Tag and hashed advanced matching.

    pinterest.capi :: live

    1. ● pinterest.capi :: live
    2. > event checkout value=214.00 AED
    3. hash sha256(em,ph) click_id=captured
    4. dedupe event_id vs tag matched
    5. ✓ delivered · num_events_received 1
    WHO THIS IS FOR

    Built for the teams that own the number.

    Retail, home, fashion, and beauty brands where Pinterest drives discovery.

    Teams losing Pinterest Tag events to browser tracking prevention.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Audit

      Pinterest Tag coverage, event map, and match parameter baseline.

    2. Configure

      Server-side Conversions API with dedupe against the Tag and hashed identifiers.

    3. Verify

      Events confirmed in Pinterest Ads Manager before go-live.

    WHAT FLOWS WHERE

    One use case, every source.

    A checkout fires on your website, Signals hashes the identifiers and deduplicates on the shared event ID, then posts the event to Pinterest's Conversions API server-side.

    A checkout fires on your website, Signals hashes the identifiers and deduplicates on the shared event ID, then posts the event to Pinterest's Conversions API server-side.

    WHAT YOU GET

    What ships with this offering.

    Deduped Tag plus CAPI on every key event.

    Higher match rates from hashed advanced matching.

    Stronger optimization signal for Pinterest campaigns.

    ON THE WIRE

    What the platform actually receives.

    Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.

    signals :: pinterest-capi :: wire

    1. ● signals :: event payload
    2. > POST /v5/ad_accounts/{id}/events action_source=web
    3. event_name "checkout" · event_id "e2f9c1…"
    4. user_data em "9b1a4d…" · ph "7c3e88…" · click_id "epik.1…"
    5. custom_data value 214 · currency AED
    6. ✓ num_events_received 1 · processed
    SUPPORTED PLATFORMS

    Bring it from where the data lives.

    Every source that supports this use case. Pick a platform to see the exact setup.

    FAQ

    Questions your team will ask.

    Which events are supported?

    Pinterest supports its standard set of web events, including page visit, add to cart, checkout, signup, and lead, alongside custom events specific to your site. During setup, Datahash maps your existing event taxonomy to Pinterest's schema so nothing is renamed or dropped, and both the Tag and the Conversions API report the same event names.

    How does advanced matching work?

    Identifiers such as email are hashed on our side and attached to each server event before it reaches Pinterest. Pinterest then matches those hashed values against its own signed-in user records, which raises attribution coverage beyond what the Pinterest Tag captures alone. Raw PII never reaches Pinterest at any point in the process.

    Do we keep the Pinterest Tag?

    Yes. The Pinterest Tag keeps running in the browser exactly as it does today, and the Conversions API runs alongside it rather than replacing it. Datahash dedupes both on a shared event identifier, so each conversion counts once in Pinterest Ads Manager while overall coverage improves, including events lost to browser tracking prevention.

    NEXT STEP

    Live in fifteen minutes. Measurable in a week.

    Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.