Pinterest Conversions API
Server-side event delivery to Pinterest's Conversions API for enhanced conversion tracking, bypassing browser limitations for improved data quality and privacy compliance.
Pinterest Conversions API is a server destination in the walkerOS flow:
Sends events server-side to Pinterest's Conversions API via raw HTTP (POST https://api.pinterest.com/v5/ad_accounts/{adAccountId}/events), hashing 12 user_data fields with SHA-256 before transmission. Supports deduplication with the web Pinterest Tag via event_id + event_name.
Installation
Setup
- Integrated
- Bundled
Configuration reference
| Property | Type | Description | More |
|---|---|---|---|
accessToken | string | Pinterest conversion access token for Bearer authentication | |
adAccountId | string | Pinterest ad account ID from Ads Manager | |
action_source | Source of the event (web, app_android, app_ios, offline) | ||
doNotHash | Array<string> | Array of user_data fields that should not be hashed | |
test | boolean | Enable test mode by appending ?test=true to the API URL | |
url | string | Custom URL for Pinterest Conversions API endpoint | |
user_data | Record<string, string> | Mapping configuration for user data fields | |
partner_name | string | Third-party partner name for attribution |
Docker Deployment
Step 1: Create flow configuration
Use the $env.NAME syntax in your flow configuration to reference environment variables at runtime:
Step 2: Bundle the flow
Bundle your flow configuration before running in Docker:
Step 3: Run with Docker
Docker Compose example
Never commit access tokens to version control. Use environment variables or a secrets manager to inject credentials at runtime.