Home
Connectors
Phoenix Technologies - Pinterest

Send every Phoenix Technologies event to Pinterest, server-side

Q: 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.

Q: 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.

Q: Which customer parameters are sent to Pinterest?

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

Q: How do I check that Phoenix Technologies 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.

Q: How long does it take to connect Phoenix Technologies to Pinterest?

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

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.

Request a demo Start free trial

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 Phoenix Technologies event reaches Pinterest. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Phoenix Technologies

Capture Phoenix Technologies orders from the server, including the upsell sequence, so the complete order value reaches every downstream tool.

See the Phoenix Technologies integration

Phoenix TechnologiesWhat it sends

order_idPhoenix order reference
email / phonecontact from the order record
line_itemsinitial purchase and any upsells
total / rebill_amountfirst charge separated from recurring
transaction_stateapproved, declined or rebill

02 Understand

Resolved to one person before it leaves

Every Phoenix Technologies 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

Resolved 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

Rebills look exactly like new orders to an ad platform.

Forwarding them as conversions teaches the algorithm to bid for customers you already have, and inflates acquisition performance by the entire recurring base.

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 Phoenix Technologies feeds Pinterest. Two gains on the Pinterest side, two on the Phoenix Technologies side.

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.

Identity-resolved events

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

Phoenix Technologies

Every event, server-side

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

Phoenix Technologies

One setup, every destination

Connect Phoenix Technologies 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

Phoenix Technologies Data source Connected

Pinterest Destination Healthy

Read the full Pinterest setup guide

01

Connect Phoenix Technologies

Capture Phoenix Technologies orders from the server, including the upsell sequence, so the complete order value reaches every downstream tool.
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_.
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 Phoenix Technologies 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 Phoenix Technologies 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 Phoenix Technologies to Pinterest?

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