Skip to main content
  1. Home
  2. Connectors
  3. WooCommerce - Pinterest
WooCommerce Pinterest

Send every WooCommerce event to Pinterest, server-side

Each event is resolved to a person against a 750M+ device graph before it reaches Pinterest, with restored click IDs, deduplicated conversions and delivery you can audit.

US device IDs in the graph
750M+
Match rate on events
90%+
Identity window, per customer
Lifetime
Most brands are live
<20 min

How it flows

How a WooCommerce event reaches Pinterest. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from WooCommerce

Capture WooCommerce orders and customer events server-side and forward them to every platform you buy on.

See the WooCommerce integration
WooCommerceWhat it sends
  • order_idWooCommerce order number
  • billing_email / phonecheckout contact fields
  • customer_idWordPress user, when logged in
  • line_itemsproducts and quantities
  • order_totalorder value after discount

02 Understand

Resolved to one person before it leaves

Every WooCommerce event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works
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.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

03 Activate

Delivered to Pinterest

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

See the Pinterest integration
PinterestWhat it receives
  • em / ph (hashed)Conversions API matching
  • click IDattribute saves and clicks that convert later
  • event_iddedupe
  • valuevalue optimization

The catch

WooCommerce sites vary enormously in how checkout is built, and browser-side conversion tags break on custom checkouts more often than on hosted platforms.

Capturing on the server sidesteps the theme entirely.

Where to check in PinterestDelivery you can audit

Pinterest Ads Conversions Event history

which shows server events separately from tag events.

What changes

What changes when WooCommerce feeds Pinterest. Two gains on the Pinterest side, two on the WooCommerce side.

Pinterest

Server-side delivery

By default Upstack sends events to Pinterest from its servers as well as through the Pinterest tag, so an event an ad blocker or browser privacy setting stops in the browser still arrives from the server.

Pinterest

Identity-resolved events

Events sent to Pinterest carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

WooCommerce

Every event, server-side

Storefront and checkout events are captured from WooCommerce on the server, independent of the browser.

WooCommerce

One setup, every destination

Connect WooCommerce once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

You need admin access to your Pinterest Business account.

Upstack dashboardExample
WooCommerce Data source Connected
Pinterest Destination Healthy
Read the full Pinterest setup guide
  1. 01

    Connect WooCommerce

    Capture WooCommerce orders and customer events server-side and forward them to every platform you buy on.

  2. 02

    Add the Pinterest destination

    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_.

  3. 03

    Check events in 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.

FAQ

Questions about WooCommerce and Pinterest.

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.

Which customer parameters are sent to Pinterest?

Events carry hashed email and phone plus the epik click ID when available.

How do I check that WooCommerce 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.

How long does it take to connect WooCommerce to Pinterest?

Most brands are live in under 20 minutes. Once WooCommerce is connected, every destination receives the same resolved events, Pinterest included.

Related connectors

See all 408 connectors

Get WooCommerce talking to Pinterest.

A 15-minute walkthrough of this connector on your own account.

21-day free trial, no card. Month to month.