Pinterest Conversions API GTM: Server-Side Delivery Through sGTM
Pinterest Conversions API GTM delivery runs through a custom server-side template: server-side Google Tag Manager ships no native Pinterest integration, and the custom template API provides sendHttpRequest - the documented way for a server container to issue outbound POSTs. Pinterest's side is a plain JSON endpoint, POST /v5/ad_accounts/{ad_account_id}/events, authenticated with the Conversions API token. The work is the mapping.
Mapping the sGTM Event Model to Pinterest's Payload
| Pinterest v5 field | Source in the sGTM event model |
|---|---|
event_name | Mapped from the inbound event (purchase to checkout, generate_lead to lead, and so on) |
action_source | Fixed web for browser-originated events |
event_time | The conversion's original timestamp, not the send time |
event_id | A value both the tag and the template can compute for the same conversion |
user_data.em | Hashed email captured at click or form time, SHA-256 after normalization |
event_source_url | The page location the client reported |
Two fields decide whether the setup survives contact with real traffic. The event_id is Pinterest's deduplication key: in the recommended dual delivery the tag and the API both report the same conversion, and only an identical event_id on both sides collapses the copies. The hashed email in user_data is what Pinterest's matching consumes - the same identifiers the Enhanced Match browser feature sends, applied server-side.
Delivery Windows and Queue Discipline
Pinterest states delivery should be as close to real-time as possible - under one hour - so optimization, attribution, and bidding react to current data. A server container that queues events during an outage must flush within that window, not after it: campaigns optimizing on yesterday's conversions are the visible symptom of a batch-heavy template. Responses and their fixes are in Pinterest Conversions API error codes.
A maintained sGTM deployment is real operational work - template versioning, token hygiene, and monitoring the queue age. Teams that would rather own only the postback hand the mapping to an automation: MOST applies these payload rules per network, and Pixel Activator sends single test events without setup. The cluster map is in the complete guide.
Frequently asked questions
Sources
Sources
- Manual testing and validation: Pixel Activator fires free test events while you tune parameters.
- Automated delivery: Most routes conversions from your tracker or CRM continuously, with deduplication and retries handled.