Skip to main content
  1. Home
  2. Integrations
  3. Pinterest
Upstack Data

Pinterest integration: identity-resolved conversions, sent server-side

Server-side conversions to the Pinterest Conversions API, resolved and deduplicated.

Role
Destination
Category
Ad platforms
Pre-built connectors
12 sources
Plans
All plans

What Upstack sends

Every conversion reaches Pinterest with the identifiers it matches on. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources
  • order_idShopify order and checkout token
  • email / phonecustomer contact from checkout
  • customer_idShopify customer record, if they have one
  • line_itemsproducts, variants and quantities
  • total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

Upstack DataResolved before it is sent
  • IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
  • customer_typeNew or returning, resolved before send.
  • DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
  • Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Out: to PinterestOn every event
  • em / ph (hashed)Conversions API matching
  • click IDattribute saves and clicks that convert later
  • event_iddedupe
  • valuevalue optimization

Conversions API, deduplicated server-side.

About Pinterest

Pinterest’s long consideration window is exactly where browser identifiers expire.

Upstack resolves each conversion against a device graph whose matches persist for months rather than days, so a purchase that happens three weeks after the save is still attributable. Events are sent server-side and deduplicated against the tag.

What Pinterest is

Pinterest sits between discovery and intent, and performs for brands in home, apparel, beauty and anything with a strong visual consideration phase.

Its Conversions API accepts server-side events so that purchases completed days after the original save or click still get attributed.

How Pinterest works

Pinterest sits earlier in the consideration cycle than most paid channels: people save a pin and buy days or weeks later. Its Conversions API accepts server-side events with hashed email and phone plus a click identifier, so a purchase that completes long after the original session can still be attributed. Events sent through the API and events from the tag are deduplicated on a shared event ID.

What you can do with it

Three jobs this connector does inside Pinterest.

01

Send complete conversions

Conversions reach Pinterest through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

02

Optimize on the customer you want

Map any order attribute to the conversion Pinterest receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

03

Attribution that survives the gap

Pinterest purchases often complete days after the original save. Server-side conversions with durable identifiers keep that attribution intact.

Pre-built connectors

12 sources connect to Pinterest. Whichever of these you run, Pinterest is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Pinterest as a destination, next to the Pinterest developer docs.

FAQ

Pinterest integration questions.

What does Upstack send to Pinterest?

Server-side conversions to the Pinterest Conversions API, resolved and deduplicated.

How do I connect Pinterest to Upstack?

Under Destinations, add Pinterest with your Pixel Tag ID (a 13 digit number), your Advertiser ID (a 12 digit number) and a Conversion API key generated in Pinterest Business, which starts with pina_. You need admin access to your Pinterest Business account.

How do I check that events are reaching Pinterest?

Upstack marks the destination Healthy, and Conversions, Pinterest tag in Pinterest Business shows events from your Conversions API integration. Match quality and conversion attribution build over the following 24 to 48 hours.

Which plans include the Pinterest integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

What’s the difference between the Pixel Tag ID and the Advertiser ID?

The Pixel Tag ID identifies a specific tracking pixel inside your Pinterest account, and the Advertiser ID identifies the ad account that owns it. Upstack needs both: the Pixel Tag ID to attribute events to the right pixel, and the Advertiser ID to send them on behalf of the right ad account.

Do I still need the Pinterest browser pixel?

Server-side delivery works on its own, but running both gives Pinterest the strongest signal. As long as the Pixel Tag ID matches between your browser pixel and the Upstack destination, Pinterest’s deduplication prevents double counting.

Similar integrations

Other Ad platforms integrations.

See all integrations

Get Pinterest tracking right.

A 15-minute walkthrough tailored to your stack and channels.