- 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 Skio event reaches Pinterest. Captured on the server, resolved to a person, then sent.
01 Capture
Captured from Skio
Capture Skio subscription events server-side, with the first charge distinguished from every renewal that follows it.
See the Skio integration →
SkioWhat it sends subscription_idthe Skio subscription, stable across chargesemail / phonesubscriber contactcharge_typefirst charge, renewal, swap or skipline_itemsproducts on this chargetotal / intervalcharge amount and billing cadence
02 Understand
Resolved to one person before it leaves
Every Skio 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.
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 matchingclick IDattribute saves and clicks that convert laterevent_iddedupevaluevalue optimization
The catch
A first charge is an acquisition and a renewal is not, but both arrive as purchases.
Sending renewals as conversions is the single most common way a subscription brand teaches Meta to re-buy its existing subscribers.
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 Skio feeds Pinterest. Two gains on the Pinterest side, two on the Skio 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.
Skio
Every event, server-side
Storefront and checkout events are captured from Skio on the server, independent of the browser.
Skio
One setup, every destination
Connect Skio 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
Skio Data source Connected
Pinterest Destination Healthy
Read the full Pinterest setup guide → -
01
Connect Skio
Capture Skio subscription events server-side, with the first charge distinguished from every renewal that follows it.
-
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 Skio 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 Skio 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 Skio to Pinterest?
Most brands are live in under 20 minutes. Once Skio is connected, every destination receives the same resolved events, Pinterest included.