Send your conversion events directly to Pinterest’s Conversions API (CAPI), now at the edge.
Find it on GitHub: /edgee-cloud/pinterest-capi-component
Pinterest Conversions API (CAPI) allows you to send web events directly to Pinterest from your server, ensuring reliable data tracking even with ad blockers or browser limitations. With Edgee’s edge integration, you can now send these events directly from the edge, improving both reliability and performance.
Here’s how Edgee events map to Pinterest CAPI events:
Edgee event | Pinterest CAPI Event |
---|---|
Page | page_visit |
Track | custom |
User | lead |
Pinterest Conversions API requires user identification data for event processing. Each event must include at least one of the following user properties:
Events without any user identification will be ignored by Pinterest.
When you make a user
call, Edgee stores the user’s data (user_id, anonymous_id, and properties) on the device. This enables proper attribution for subsequent page views and events.
To integrate Pinterest CAPI into your Edgee project:
edgee/pinterest-capi
from the list of available components.Pinterest Access Token
: Your Pinterest CAPI access tokenPinterest Ad Account ID
: Your Pinterest Ad Account IDPinterest is Test
(Optional): For testing your implementationTo know how to get your access token and ad Account Id visit the Pinterest API documentation.
When configuring the destination in your Edgee Data Layer or within SDK calls, use pinterest_capi
as the component name:
is_test
flag to true
in the component configurationUse Pinterest test property is_test
to test your implementation without affecting your production data.
For more details on Pinterest Conversions API implementation, refer to the official Pinterest CAPI documentation.