CONNECTIONS / Pinterest
Pinterest CAPI, live in your ad account.
Datahash works directly with Pinterest to implement the Pinterest Conversions API, with dedupe against the Pinterest Tag and hashed advanced matching.
- > event pinterest.sync status=ok
- hash sha256(email,phone) pii=cleared
- route every Pinterest destination
- ✓ Pinterest connected · live
The full Pinterest stack, page by page.
Every source, one path into Pinterest.
Signals hashes and dedupes each event once, then routes it to every Pinterest destination on this page. No separate pipeline per offering.
Brands running Pinterest on Signals.
Questions your team will ask.
Which events can we send to Pinterest?
The full Pinterest event set, including checkout, add to cart, page visit, signup, search, lead, and custom events. Datahash maps your source events to Pinterest's schema, applies hashed advanced matching to each one, and validates the full set against Pinterest's Conversions API before go-live so nothing breaks in production.
What is advanced matching?
Advanced matching sends hashed identifiers such as email and mobile advertiser ID alongside each event. Pinterest matches them against its own hashed records, which lifts attribution coverage and improves audience quality even when cookies are blocked. Datahash hashes every identifier with SHA-256 at source, so raw personal data never leaves your systems.
Does CAPI replace the Pinterest Tag?
No. Running the Pinterest Tag and CAPI together, deduplicated on a shared event ID, is the recommended setup. The tag covers browser-side signals while CAPI recovers conversions lost to ad blockers and cookie limits. Datahash generates and matches the event IDs across both sources, so Pinterest keeps one copy of each event and reporting never doubles up.
NEXT STEP
Book a Pinterest stack working session.
We map your source data against every integration on this page and propose a sequence.