CONNECTIONS / Shopify / Shopify to Pinterest CAPI
Shopify sales, credited back to Pinterest discovery.
Pinterest sends shoppers who research before they buy, which is exactly the traffic browser tracking loses along the way. Signals delivers the same storefront checkout events server-side to Pinterest, deduped against the Tag.
- ● shopify → pinterest.capi :: live
- > event Checkout completed value=176.00 AED
- hash sha256(email) dedupe=tag+server
- route pinterest.capi match 64%
- ✓ delivered · event accepted
WHAT THIS ENABLES
Shopify to Pinterest Conversions API
Shopify to Pinterest Conversions API delivers checkout and purchase events from the storefront server-side to Pinterest, deduped against the Pinterest Tag and enriched with hashed advanced matching, so Pinterest's discovery-driven traffic gets credited all the way to the sale.
- Purchases credited to Pinterest even when the shopper's research-to-buy path spans multiple sessions.
- Checkout events reaching Pinterest server-side where the browser Tag alone would drop them.
- Higher match rates on home, fashion, and beauty verticals where Pinterest drives discovery.
WHAT FLOWS WHERE
Shopify to Pinterest CAPI, mapped.
A Shopify checkout completed event is hashed by Signals and posted to Pinterest's Conversions API under the event identifier the Tag already carries, so Pinterest keeps a single copy of the sale.
A Shopify checkout completed event is hashed by Signals and posted to Pinterest's Conversions API under the event identifier the Tag already carries, so Pinterest keeps a single copy of the sale.
Built for the teams that own the number.
Teams seeing Pinterest Tag events lost to browser tracking prevention.
From kickoff to verified events.
-
Install
Web Pixel extension configured alongside app-scoped access to checkout webhooks.
-
Map
Storefront events matched to Pinterest's event taxonomy, including page visit, add to cart, and checkout.
-
Deliver
Server-side delivery to Pinterest's Conversions API, deduped against the Tag and verified in Pinterest Ads Manager.
What ships with this use case.
Deduped Tag-plus-server coverage on every key storefront event.
Higher match rates from hashed advanced matching layered onto browser-only tracking.
Stronger optimization signal for Pinterest campaigns running on discovery traffic.
What Pinterest CAPI actually receives.
- ● signals :: event payload
- > POST /events source=shopify.checkout
- event_name "checkout" · action_source "web" · event_time 1784518020
- em sha256 "7bd403…"
- value 176.00 · currency AED
- ✓ accepted match=64%
Adjacent moves on the same stack.
from Shopify
Shopify to every ad platform
Shopify to every ad platform is a single install that maps Shopify's order and checkout…
Learn morefrom Shopify
Shopify to Meta Click-to-Message
Shopify to Meta Click-to-Message Conversions ties a Shopify order back to the…
Learn more
same use case
BigCommerce to Pinterest CAPI
Pinterest Conversions API for BigCommerce: Signals credits store sales back to the…
Learn moregeneric
Pinterest CAPI
Datahash implements Pinterest Conversions API with dedupe against the Pinterest Tag and…
Learn moreAsked on almost every call.
Do we keep the Pinterest Tag Shopify's native channel already installed?
Yes. The Tag and the Conversions API run together on a shared event identifier, so Pinterest drops the duplicate instead of counting the sale twice. The Tag also keeps contributing browser-side signal for events the server path doesn't need to repeat.
How does advanced matching improve results here?
Hashed email from the Shopify checkout is attached to every server event, which Pinterest matches against its own signed-in users. Raw customer data never reaches Pinterest; only the hash does, and match quality rises as more identifiers are available per order, particularly on repeat customers with an established Pinterest account.
NEXT STEP