Walityk sends your events to the Pinterest Conversions API (v5), server-side, with event_id deduplication against the Pinterest browser tag.
Takes 5 minutes.
Prerequisites
- A Pinterest Business account with an ad account.
1. Get the identifiers
- Ad Account ID: Pinterest Business Hub → your ad account — the numeric ID appears in the URL and in the account settings.
- Access Token: an OAuth token with the
ads:writescope (Pinterest Business → developer settings / Conversions API token generator). - Optional — Tag ID: the identifier of your Pinterest browser tag (Tag Manager).
⚠ Tag ID ≠ Ad Account ID. These are two distinct identifiers. The Ad Account ID is for the Conversions API (server-side); the Tag ID is only for the browser pixel. Don’t put one in the other’s field.
2. Configure the destination
- Walityk dashboard → Destinations → your site → Pinterest Conversions API card.
- Paste the Ad Account ID and Access Token.
- Optional: fill in the Tag ID (browser pixel). If it’s set and “Pixel deduplication” is enabled on the site, the Walityk tag automatically initializes the Pinterest pixel on your pages — no more need for your own
pintrk('load', …)snippet. - Save.
3. Deduplication with the browser pixel
- Pixel deduplication enabled + Tag ID set: Walityk manages the pixel and re-fires events with the same
event_idas the server copy. Remove your manualpintrk('track', …)calls. - Without a Tag ID, only the server-side Conversions API runs — enough for campaign tracking.
4. Verify
- Destinations → your site → Pinterest: delivery log.
- On the Pinterest side: Ads Manager → Conversions → the API event history.
Common errors
- HTTP 401/403: token missing the
ads:writescope, or expired → regenerate it. - HTTP 404: Ad Account ID not found — check the numeric ID (and that it isn’t the Tag ID).
- The Pinterest click (
epik) is captured automatically from landing URLs: no tag-side configuration.
Next steps
Need help? hi@walityk.com.