Pinterest Conversions API Setup: Token, Deduplication, and Event Quality
What Pinterest's Conversions API Covers
The Pinterest Conversions API is the platform's server-side intake: conversions travel from your server directly to Pinterest, and Pinterest states that these server events behave like the ones coming from the Pinterest tag or a mobile measurement partner. For affiliate funnels that matters in a specific way - the conversion usually happens on an offer page you do not control, so the server event is the only copy of it Pinterest can see. All three conversion kinds are supported: web, in-app, and in-store/offline, which makes the API the single delivery channel across mixed funnel types. The general mechanics of such channels are in conversions API.
Pinterest keeps the entry requirements deliberately light. Any Pinterest business account can use the Conversions API, and - unlike broader Pinterest API products - it does not require creating an application or a valid app ID. You need the business account and a token generated through the Conversions page in Ads Manager, and then the POST send conversions endpoint is available.
Generate the Access Token in Ads Manager
Pinterest's getting-started guide gives the exact path: log in to the business account, open the hamburger menu at the top left, select Conversions in the Manage business column, then choose the Set Up API page in the left navigation and click Generate new token. Copy the new access token together with your account ID - both values go into the delivery configuration, the token for authentication and the account ID for addressing the right ad account.
Two operational notes from the same guide deserve attention. If you need access to an account you do not own, Business Access has to be set up first, or the owner generates and shares the token - and Pinterest explicitly recommends against sharing tokens unless there is a secure channel for it. A conversion token pasted into a group chat is a credential leak with your ad spend attached; store it server-side the same way you would store an access token for any other CAPI integration.
Choose the Integration Path: Direct or Partner
Direct integration is Pinterest's recommended path for maximum control, and Pinterest is explicit that it requires developer involvement: payload formatting, parameter completeness, and error handling are yours. Full parameter lists per event - required and recommended - live in Pinterest's developer documentation, and the same docs cover the technical protocol details.
The partner path delegates that work to a third-party platform. For a tracker-based funnel there is a third shape that is neither: a delivery tool that accepts your tracker's postback and formats the platform payload for you - MOST delivers to Pinterest alongside Meta, TikTok, Reddit, Snapchat, and OpenAI, and the free Pixel Activator covers Pinterest delivery for a single landing with a manual workflow. Either way, the setup checklist from Pinterest stays the same: correct parameters, near-real-time delivery, deduplication, and validation.
Deduplicate Tag and API Events with event_id
Dual integration is Pinterest's own recommendation: send the same events through the Conversions API that you already send through the Pinterest tag or a mobile measurement partner, because the combination maximizes conversion visibility. Running both without preparation costs double-counting, and the fix is the event_id parameter - Pinterest's help center instructs advertisers using the tag or an MMP together with the API to deduplicate by passing event_id, the same shared-key discipline as pixel and CAPI deduplication in Meta's ecosystem. The mechanics of the shared key are in event ID deduplication.
In a tracker funnel the event_id needs a deterministic source: the transaction or click identifier that both the browser side and the server side can compute for the same conversion. An event_id that only one side can generate silently disables deduplication - both copies count, and the discrepancy shows up later as inflated numbers in Ads Manager.
For offline conversions without development resources, Pinterest offers a fallback that needs no API at all: upload an offline conversions file into Ads Manager and Pinterest attributes those conversions to campaigns from the file.
Delivery Requirements, Privacy, and Event Quality
Timing is a stated requirement, not a nicety: Pinterest asks for event delivery as close to real-time as possible - under one hour - so that optimization, attribution, and bidding react to current data. A delivery pipeline that batches once a day feeds Pinterest stale signals, and the visible symptom is campaigns optimizing on yesterday's conversions.
For compliance, Pinterest provides a Limited Data Processing flag to satisfy state privacy laws - the same category of control as consent-related parameters in other networks' CAPIs, and the payload rules behind such flags follow the cross-platform discipline described in CAPI user data hashing and normalization.
Validation closes the loop, and Pinterest names three checkpoints in Events Manager. Test events let the developer see the response codes returned for each request as conversions fire. The deduplication page on the Events Overview shows post-deduplicated conversions - the place to confirm that tag and API copies are collapsing into one instead of doubling. And Event Quality Score grades the payload: Pinterest's guidance is to pass data in a way that sets the integration up for a Good EQS, which is the platform's version of the match-quality signals covered in event match quality scoring. The validation habit is the same across networks - test events before scaling.