Send server-side conversion events to Pinterest via the Conversions API
domain: developers.pinterest.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm you have a Pinterest Business Account and generate a Conversions API access token from the Conversions page in Ads Manager.
POST conversion events to Pinterest's send-conversions endpoint with event type, event time, and hashed customer identifiers (email, phone, etc.) as applicable.
Assign a matching event_id to any corresponding Pinterest Tag (client-side) event so Pinterest deduplicates the pair rather than double-counting the conversion.
Optionally define custom event types beyond Pinterest's standard set if your business tracks non-standard conversion actions.
Validate delivery and match quality in Ads Manager's Conversions section before relying on the data for campaign optimization.
Known gotchas
Conversions API events and Pixel/Tag events for the same action must share the same event_id or Pinterest counts them as two separate conversions.
All customer identifiers sent for matching (email, phone, etc.) must be hashed per Pinterest's normalization rules — sending raw PII is rejected or reduces match quality.
The access token is generated per ad account from Ads Manager rather than through a general developer-app OAuth flow — losing or regenerating it breaks the existing server integration.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?