Pinterest Conversions API
Pinterest's take on the same server-side pattern
Pinterest's Conversions API (branded within Pinterest's Business documentation simply as the Conversions API, often implemented alongside the Pinterest Tag) mirrors the Meta/TikTok/Snap model closely: server-side event delivery direct to Pinterest, designed to supplement rather than replace the browser Pinterest Tag, with deduplication and enhanced-match identity signals working on the same underlying principles. Pinterest's own ad platform is smaller than Meta or TikTok's, but for ecommerce and home/lifestyle verticals it often carries disproportionately high purchase intent, making accurate conversion signal especially valuable relative to spend.
Identity fields and Pinterest's click identifier
Pinterest's click ID equivalent is captured via the epik URL parameter on ad-driven landing page visits. As with every other platform in this family, it must be captured client-side at landing and persisted through to whatever system later fires the server-side conversion event — commonly via a first-party cookie bridging the gap between initial click and eventual checkout completion. Pinterest also accepts hashed email, hashed phone, and the Pinterest Tag's own click/visitor identifiers as additional matching signals under its advanced matching parameters.
{
"data": [
{
"event_name": "checkout",
"action_source": "web",
"event_time": 1735689600,
"event_id": "order_4821",
"user_data": {
"em": ["f660ab912ec121d1b1e928a0bb4bc61b15f5ad44d5efdc4e1c92a25e99b8e44"],
"click_id": "epik_1a2b3c4d",
"client_ip_address": "203.0.113.42",
"client_user_agent": "Mozilla/5.0 ..."
},
"custom_data": {
"currency": "USD",
"value": "149.50",
"order_id": "4821"
}
}
]
}event_id deduplication, once more, the same contract
event_id across both — the fifth platform in a row following this exact pattern. Once this concept is understood for one platform, implementing it correctly for the rest becomes a mapping exercise rather than new learning.Diagnostics via Events Manager
Pinterest's Ads Manager includes an Events Manager / Conversion Diagnostics view showing per-event match rate, recent event volume by source (Tag vs. API), and validation errors for malformed payloads — directly analogous to Meta's Events Manager and TikTok's Test Events tool. Checking match rate specifically here (not just whether events appear at all) surfaces silent quality issues: events arriving successfully but with so few matchable identity fields that they contribute little to attribution or optimization.
Cross-platform conversions API field summary
| Field purpose | Meta | TikTok | Snapchat | |
|---|---|---|---|---|
| Click ID parameter | fbclid → fbc | ttclid | ScCid | epik |
| Dedup key | event_id | event_id | event_tag | event_id |
| Hashed email field | user_data.em | user.email | hashed_email | user_data.em |
Smaller platforms mean smaller support surface for debugging
What's Next?
LinkedIn's Conversions API closes out the major social ad platform set, with one meaningful difference from the consumer platforms covered so far: B2B matching signals (company domain, job title) that have no real analog in consumer advertising.
I build these systems professionally.
Whether it's a RAG pipeline, analytics migration, or AI workflow — let's talk.