Published by Patientdesk AI, Inc.

← Conversions for Pinterest

Setup guide

  1. Install Conversions for Pinterest in your CRM account. Open Pinterest Conversions from its menu, then Open setup dashboard.
  2. In Pinterest Ads Manager → Conversions → Set up API, generate a conversion access token for your own ad account. Save the numeric ad account ID and token on the Connection tab. Saving alone does not verify delivery.
  3. Add Send Pinterest Conversion in the normal workflow picker. Select an event type and web or offline source. Map a stable Conversion ID and email, or both customer IP and user agent.
  4. Enable Test mode and send a synthetic event. Check the processed receipt and Pinterest Ads Manager → Conversions → Test events.
  5. Disable Test mode for live workflows. Keep Conversion ID unchanged for retries and corresponding browser tag events. Confirmed duplicates are suppressed for 48 hours, separately for test and live sends.

Matching and mapping

Email is trimmed and lowercased before SHA-256 hashing; dots and plus suffixes are preserved. Phone is normalized to digits with country code, without leading zeros, then hashed. External IDs are hashed. Existing SHA-256 values are preserved. Pinterest Click ID (_epik cookie or epik URL parameter) is sent unchanged. Phone, click ID and external ID alone do not meet Pinterest’s matching requirement.

Original event time accepts ISO format, Unix seconds or milliseconds within seven days; the API receives integer seconds. Value and currency must be supplied together. Page URL applies to web events. This release supports web and offline conversions. For custom events enter a distinct name of 1–100 letters, digits, underscores or hyphens. Pinterest supports at most 15 custom event types per ad account; configure their event mapping in Pinterest if needed.

Privacy controls

Map Opt out and Limited data processing (LDP) as appropriate. These controls do not replace advertising consent or your obligation to exclude prohibited data. Do not map medical details or sensitive information into event names, IDs, URLs or values.

Receipts and retries

Success requires Pinterest to confirm exactly one received and processed event with processed status. API acceptance does not guarantee attribution. Transport failures, rate limits and server errors are retryable. Configure workflow retries with the same Conversion ID; there is no background retry queue. Provider warnings are indicated without exposing raw messages that may contain customer data.

Permissions and disconnect

oauth.readonly identifies installed accounts; workflows.readonly enables workflow actions. No contact or messaging access is requested. Disconnect removes the saved Pinterest token and receipts. Revoke tokens in Pinterest and cancel Marketplace subscriptions separately.

Pinterest API for Conversions · Official integration guide