Keitaro Pinterest Integration: Tracker Postbacks Into the Conversions API
Keitaro Pinterest integration is the wiring that turns tracker postbacks into Pinterest Conversions API events: Keitaro records the conversion and keeps the click identity, while a delivery layer formats the v5 payload Pinterest accepts. Pinterest's deduplication and quality scoring make identity discipline the whole game - an event without a stable event_id or usable user_data degrades silently.
Register Pinterest as a Traffic Source
Keitaro's traffic source mechanism parses declared URL parameters from the landing URL and stores them against the click. Pinterest does not append a dedicated click ID parameter the way ad platforms with their own click identifiers do, so the identity that matters for Pinterest is the one your funnel controls: the sub IDs and transaction identifiers Keitaro assigns, plus any landing parameters your funnels use. Declaring them in a custom Pinterest source makes the stored click record complete - the source registration flow is documented in Keitaro's guide to adding a traffic source.
The S2S Postback: Identity Out of the Tracker
Conversions leave Keitaro through the S2S postback mechanism: a URL template fired per conversion, with macros substituted at send time - sub_id, transaction ID, payout, status. For the Pinterest pipeline the postback's job is to hand the delivery layer a stable conversion identity: the tracker's transaction identifier becomes the event_id Pinterest deduplicates on, and the payout maps into the event's value fields. Both values must be identical to what the Pinterest tag computed on the browser side - that symmetry is the entire deduplication mechanism.
Delivering the v5 Payload
| Pinterest v5 field | Source from the Keitaro pipeline |
|---|---|
event_name | Mapped from the postback status: sale to checkout, lead to lead |
event_id | The tracker's transaction identifier - stable per conversion |
user_data.em | Hashed email if the funnel captured one, SHA-256 after normalization |
event_time | Send time, inside Pinterest's under-one-hour delivery target |
| Endpoint auth | The ad account ID in the path, the token from Ads Manager in the header |
The endpoint is POST /v5/ad_accounts/{ad_account_id}/events; the payload rules and responses are documented in Pinterest conversion events and Pinterest Conversions API error codes. The same division of labor for the Meta side is documented in the Keitaro Facebook CAPI integration; letting an automation own the payload for all networks is what MOST does, and single manual tests run through Pixel Activator. The cluster overview is 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.