Pinterest recently released a beta version of Pinterest Conversion API. Implementing Pinterest CAPI is an excellent way to increase the accuracy of conversion tracking and, as a result, get a better return on investment for paid advertising.
This blog post will explain the possibilities of Pinterest CAPI and how stape Pinterest conversion API tag for server GTM works. Click this link to read Pinterest CAPI documentation.
1. Pinterest recommends using both browser and server tracking.
2. Supports event deduplication. To deduplicate matching events sent from web and server, Pinterest uses event ID.
3. Pinterest CAPI supports standard and custom events. The list of standard events:
4. Pinterest CAPI supports real-time server event testing. When you add ?test=true, events are marked as tests; they will not be recorded.
5. Like FB CAPI, Pinterest asks to send user data in a lowercase hashed format. These are user data that Pinterest supports:
6. Pinterest CAPI does not require Access Token. You should use only Pinterest advertiser ID.
7. Together with the event, you can send event and product data

Comments