Pinterest Conversions API, sent from your server
ROASaurus posts conversions to Pinterest's v5 Conversions API for your ad account, with the epik click id and hashed customer data. Add your Tag ID and it loads the Pinterest Tag, with the same event ids and event names as the server events.
| Pinterest at a glance | |
|---|---|
| Connection | Conversions API v5 per ad account; Pinterest Tag in the browser when a Tag ID is set |
| Events | page_visit, view_content, add_to_cart, initiate_checkout, checkout (purchase) |
| Customer data | Email, phone, first and last name, city, state, zip and country hashed with SHA-256, external_id, IP, user agent |
| Click ids | epik |
| Credentials | Ad account ID and a conversion access token; Tag ID for the browser tag |
| Spend sync | Yes: campaign spend, impressions and clicks per day, after you connect the ad account under Setup › Ad spend |
What ROASaurus sends to Pinterest
Events go to the Conversions API endpoint of your ad account. A purchase is sent as Pinterest's checkout event; the others map to page visit, view content, add to cart and initiate checkout. Each event has the event id, the page URL, the IP address, the user agent and the epik click id when the visitor came from a Pinterest ad.
Known shoppers add their email, phone, first and last name, city, state, zip and country, hashed with SHA-256, and a hashed customer or visitor id. Commerce events carry currency, value, order id, content ids, quantities and prices. ROASaurus skips events with no email and not both an IP address and a user agent.
Pinterest can answer HTTP 200 while one event in the batch failed. ROASaurus checks each event's status, so those failures show in the Event log.
How to connect
- In Pinterest Ads Manager › Conversions, create a conversion access token.
- In ROASaurus, go to Tracking & platforms, click Add pixel on the Pinterest card and enter the ad account ID and the token.
- For browser deduplication, add your Pinterest Tag ID and keep Also load the browser tag on. The Tag and the server events then use the same event ids and matching event names, so Pinterest keeps one copy of each.
- Optional: switch on test mode while you check. Events then show under Test events (max 20).
Limits
- Browser deduplication needs the Tag ID in addition to the ad account id. Without it, ROASaurus sends server events only and does not load the tag.
- Pinterest campaign spend syncs after you connect the ad account under Setup › Ad spend, so you see ROAS and profit after ads.
- If another app or theme snippet also loads the Pinterest Tag, its events have other ids and Pinterest may count purchases twice.
Related
Questions, answered
Why does ROASaurus ask for both an ad account ID and a Tag ID?
The Conversions API sends server events to the ad account. The Tag ID is only for the browser tag. With both set, browser and server events share ids and Pinterest keeps one copy.
Which event is a purchase on Pinterest?
Pinterest calls a completed order "checkout". ROASaurus sends every purchase under that name, with the order id, value and items.
How do I test the setup?
Tick test mode on the Pinterest pixel. Events then appear under Test events in Pinterest instead of in your reporting. Switch it off when you are done.
Every sale, traced to the ad that earned it
Server-side tracking, profit and lifetime value in one app. 14-day free trial, no credit card.
Start your free trial →