Pinterest Conversions API: Complete Setup Guide for E-Commerce

What is Pinterest Conversions API?

Pinterest Conversions API (CAPI) is a server-side tracking interface that lets you send conversion events directly from your server to Pinterest — bypassing the browser entirely. It's Pinterest's equivalent of Meta's Conversions API, Google's Enhanced Conversions, and TikTok's Events API, designed to solve the same core problem: browser-based tracking is losing data at an accelerating rate.

When you run Pinterest ads, the standard Pinterest Tag (a JavaScript snippet in the browser) tracks user actions like page views, add-to-carts, and checkouts. But that tag is increasingly unreliable — and for e-commerce brands investing in Pinterest Shopping campaigns, the data loss translates directly into wasted ad spend and missed optimization opportunities.

Why the Pinterest Tag alone isn't enough

The result: Your Pinterest Ads Manager is likely missing 20-40% of actual conversions. That incomplete data weakens Pinterest's ad optimization algorithm — leading to higher CPAs, poor Shopping campaign performance, and budget misallocation across campaigns.

Conversions API fixes this by sending conversion data from your server, where none of these browser-side issues apply.

---

How Pinterest Conversions API Works

Standard tracking (tag-only)

User clicks Pinterest ad → lands on your site → Pinterest Tag fires (JavaScript)
→ User converts → Tag sends event to Pinterest → Conversion recorded

Problem: If the tag is blocked, doesn't load, or the user switches devices — the conversion is lost. Pinterest never learns that this user converted, and the ad that drove the sale gets no credit.

Conversions API (server-side)

User clicks Pinterest ad → lands on your site → Your server captures the visit
→ User converts → Your server sends event to Pinterest via HTTPS
→ Pinterest matches hashed user data to the original ad click
→ Conversion recorded — regardless of ad blockers, cookies, or devices

Result: Your server communicates directly with Pinterest's servers. Ad blockers, browser restrictions, and device switching don't affect the data flow. Pinterest's algorithm receives complete conversion data and can optimize delivery effectively.

What data gets sent?

Conversions API sends two types of data with each event:

Event data:

• Event name (e.g., checkout, add_to_cart, page_visit, search, lead)
• Event ID (for deduplication with the Pinterest Tag)
• Timestamp
• Page URL
• Content details (product IDs, prices, quantities, categories)
• Order value and currency

User data (hashed for privacy):

Important: Email and phone are SHA-256 hashed before sending. Pinterest never receives raw personal data — only irreversible hashes used for matching. This makes Conversions API fully compatible with GDPR compliance requirements when implemented correctly.

---

Pinterest Conversions API vs. Other Platform APIs

If you're already using Meta CAPI or Google Enhanced Conversions, the concept is identical. Here's how Pinterest's implementation compares:

Key difference: Pinterest's Conversions API is particularly valuable for e-commerce because Pinterest is inherently a product discovery platform. Users browse with purchase intent — 85% of weekly Pinners have bought something based on Pins they've seen. When your conversion data is incomplete, you're losing optimization signals on the highest-intent audience on any social platform.

---

Why Pinterest Conversions API Matters for E-Commerce

Pinterest's unique position in the purchase funnel

Pinterest isn't like other ad platforms. Users come to Pinterest to discover products, plan purchases, and find inspiration — not to scroll past content. This creates a uniquely valuable advertising environment:

• 85% of weekly Pinners have made a purchase based on Pinterest content
• Average order value from Pinterest traffic is 2x higher than other social platforms
• Purchase intent is built into the platform — users are actively searching for products to buy
• Longer consideration cycles — users save Pins and return days or weeks later to purchase

The data loss problem is amplified on Pinterest

These longer consideration cycles make Pinterest particularly vulnerable to tracking loss:

1. User sees your product Pin on Monday → Pinterest Tag records the view
2. User saves the Pin → comes back Thursday on a different device
3. User clicks through and purchases → ad blocker blocks the tag, or cookie expired
4. Pinterest never sees the conversion → the ad that initiated the journey gets zero credit

With Conversions API, your server captures step 4 regardless of browser conditions and sends it to Pinterest with hashed user data. Pinterest matches it back to the original Pin view — and your campaign gets proper attribution.

Impact on Pinterest Shopping campaigns

Pinterest Shopping campaigns rely heavily on conversion data to optimize product catalog performance. When Conversions API is active:

---

How to Set Up Pinterest Conversions API

There are two paths: manual implementation (for developers) and automated setup (using a tool like SignalBridge).

Option A: Manual setup

Step 1: Create a Pinterest Business account

If you don't already have one, convert your Pinterest account to a Business account at business.pinterest.com. You need:

• A verified website domain
• An active Pinterest Ads account
• Admin access to the account

Step 2: Generate an API access token

1. Navigate to your Pinterest Ads Manager
2. Go to Conversions → Conversions API
3. Click Set up or Generate Token
4. Copy and securely store the access token — you'll need this for API calls
5. Note your Ad Account ID (visible in your Ads Manager URL)

Token management: Pinterest access tokens are long-lived, but you should implement secure storage and rotation procedures. Never expose tokens in client-side code.

Step 3: Implement server-side event sending

Your server needs to send HTTPS POST requests to Pinterest's Conversions API endpoint for each conversion event:

POST https://api.pinterest.com/v5/ad_accounts/{ad_account_id}/events

Each request includes:

• Headers: Authorization bearer token, Content-Type application/json
• Body: Array of event objects with event data and user data

Required event fields:

• event_name — The conversion event type (e.g., checkout, add_to_cart, page_visit)
• action_source — Where the event occurred (web, app_android, app_ios)
• event_time — Unix timestamp of the event
• event_id — Unique ID for deduplication with the Pinterest Tag
• user_data — Hashed user identifiers for matching

Step 4: Hash user data correctly

All personal data must be SHA-256 hashed before sending:

1. Normalize: Lowercase email, remove spaces, format phone numbers to E.164
2. Hash: Apply SHA-256 to the normalized value
3. Send: Include the hashed value in the user_data object

Common hashing mistakes:

• Hashing before normalizing (uppercase emails produce different hashes)
• Including spaces or special characters
• Double-hashing (hashing an already-hashed value)
• Sending raw (unhashed) data — this violates Pinterest's terms and privacy requirements

Step 5: Implement event deduplication

When running both the Pinterest Tag and Conversions API (recommended), you must deduplicate events:

1. Generate a unique event_id for each conversion
2. Pass the same event_id to both the Pinterest Tag (browser-side) and Conversions API (server-side)
3. Pinterest uses this ID to identify and merge duplicate events within a 48-hour window

Without deduplication, conversions get counted twice — inflating your numbers and corrupting campaign optimization.

Step 6: Verify your implementation

After sending test events:

1. Go to Pinterest Ads Manager → Conversions → Event History
2. Check that your server-side events appear with the correct event names
3. Verify match rates — aim for 70%+ matched events
4. Monitor for deduplication status — ensure Tag and CAPI events are being merged
5. Check for error responses in your server logs

---

Option B: Automated setup with SignalBridge

Manual implementation works but requires ongoing maintenance: token management, hashing logic, error handling, retry logic, schema changes, and deduplication coordination.

SignalBridge automates the entire Pinterest Conversions API integration:

1. Connect your Pinterest account — One-click OAuth authorization
2. Select events to track — Choose from standard e-commerce events (page view, add to cart, checkout, purchase)
3. Automatic data enrichment — SignalBridge captures and hashes user data parameters automatically, maximizing match rates
4. Built-in deduplication — Event IDs are synchronized between browser and server automatically
5. Real-time monitoring — Track event delivery status, match rates, and errors from one dashboard

What SignalBridge adds beyond basic CAPI:

• Bot filtering — Removes non-human events before they reach Pinterest, keeping conversion data clean
• Event deduplication — Automatic dedup across browser and server events
• Multi-platform delivery — Same integration sends events to Meta CAPI, Google Enhanced Conversions, and TikTok Events API simultaneously
• EMQ optimization — Maximizes match quality by including all available user parameters
• Error handling and retries — Failed events are automatically retried with exponential backoff

Setup time: Under 5 minutes, no code required.

---

Pinterest Conversions API Events Reference

Standard e-commerce events

Event priority for optimization

Not all events carry equal weight in Pinterest's optimization algorithm:

1. Checkout (highest value) — Primary optimization event for Shopping campaigns
2. Add to cart — Strong purchase intent signal
3. Search — Active product discovery behavior
4. Page visit — Awareness and engagement signal
5. Lead / Signup — Valuable for lead generation campaigns

Best practice: Always send checkout events via Conversions API. This is the event Pinterest's algorithm optimizes against most heavily for Shopping and conversion campaigns. Missing checkout events means your campaigns are optimizing on incomplete data.

---

Troubleshooting Pinterest Conversions API

Events not appearing in Pinterest

Cause: Authentication failure or malformed request. Fix:

1. Verify your access token is valid and not expired
2. Check that the ad_account_id in the endpoint URL matches your account
3. Validate JSON payload format against Pinterest's API documentation
4. Check server logs for HTTP error responses (401 = auth issue, 400 = bad request)

Low match rate

Cause: Missing user identifiers or incorrect hashing. Fix:

1. Always capture and forward the Pinterest click ID (epik URL parameter) when available — this provides the highest match quality
2. Hash email with SHA-256 after normalizing (lowercase, trim whitespace)
3. Include IP address and user agent from the original request
4. Send events in real-time rather than batching hours later — fresher data matches better

Duplicate events in reporting

Cause: Both Tag and Conversions API sending the same event without deduplication. Fix: Use the same event_id value in both the browser Tag call and the server API call. Pinterest deduplicates within a 48-hour window. If you see inflated conversion counts, check that event_id is consistent across both channels.

Events sent but not attributed to campaigns

Cause: Event timing or user data mismatch. Fix:

1. Send events within 7 days of the ad interaction (Pinterest's attribution window)
2. Ensure hashed email/phone matches the user's Pinterest account data
3. Include the epik click parameter when the user arrived via a Pinterest ad click
4. Verify your attribution settings in Pinterest Ads Manager

---

Best Practices for Pinterest Conversions API

1. Run Tag + CAPI together

Pinterest recommends running both the browser Tag and Conversions API simultaneously. The Tag provides real-time signals for audience building and dynamic retargeting. CAPI recovers the events the Tag misses. Together with deduplication, you get the most complete picture.

2. Prioritize high-value events

Focus your CAPI implementation on events that directly impact campaign optimization: checkout, add_to_cart, and lead. Page views are helpful but less critical for ROAS optimization.

3. Maximize user data parameters

The more user data parameters you send (properly hashed), the higher your match rate. At minimum, always include:

• Hashed email address
• Click ID (epik) when available
• IP address and user agent

4. Send events in real-time

Pinterest's matching accuracy decreases with event delay. Send conversion events within seconds of the action occurring, not in hourly or daily batches.

5. Monitor match rates

Check your event match rates in Pinterest Ads Manager weekly. A healthy match rate is 70%+. If it drops below 50%, investigate missing user data parameters or hashing errors.

6. Filter bot traffic

Sending bot conversions to Pinterest through CAPI is worse than missing conversions — it actively corrupts your campaign optimization. Use server-side bot filtering to remove non-human events before they reach Pinterest.

---

FAQ

Do I still need the Pinterest Tag if I use Conversions API?

Yes, Pinterest recommends running both together. The browser Tag provides real-time signals for dynamic retargeting ads and audience building, while Conversions API catches the 20-40% of events the Tag misses due to ad blockers, iOS restrictions, and cookie limitations. Together with event deduplication, you get maximum data quality.

How is Pinterest Conversions API different from Meta CAPI?

They solve the same problem — server-side conversion tracking — but differ in implementation details. Pinterest uses long-lived access tokens while Meta uses ~60-day tokens. Both accept SHA-256 hashed user data. The key difference is Pinterest's click identifier (epik) versus Meta's (fbclid). If you use a tool like SignalBridge, it handles the differences across all platforms automatically.

Does Pinterest Conversions API work with Shopify?

Yes. Shopify stores can implement Pinterest CAPI either through manual API integration, Pinterest's own Shopify app (which has limited server-side capabilities), or through a third-party tool like SignalBridge that connects your Shopify store to Pinterest's Conversions API with full server-side tracking and bot filtering.

How much does it cost to use Pinterest Conversions API?

The Conversions API itself is free — Pinterest doesn't charge for receiving server-side events. Your costs are infrastructure (server to send events) and development time (building and maintaining the integration). Tools like SignalBridge start at $29/month and handle all the infrastructure across Pinterest, Meta, Google, and TikTok simultaneously.

Will Pinterest Conversions API help my Shopping campaigns?

Significantly. Shopping campaigns rely on conversion data to rank products in your catalog and optimize delivery to likely buyers. When CAPI sends complete conversion data, Pinterest's algorithm learns which products convert best, which audiences buy, and which creative drives purchases — leading to lower CPAs and higher ROAS on Shopping campaigns.

Is Pinterest Conversions API GDPR-compliant?

Yes, when implemented correctly. All personal data is SHA-256 hashed before transmission — Pinterest never receives raw personal information. However, you must still have a legal basis for processing (typically legitimate interest for first-party conversion tracking) and disclose server-side tracking in your privacy policy. See our GDPR compliance guide for detailed requirements.

---

Related Reading

• TikTok Events API: Complete Setup Guide — TikTok's equivalent server-side tracking solution
• What is Facebook Conversions API (CAPI)? — Meta's server-side tracking implementation
• How to Set Up Google Enhanced Conversions — Google's server-side tracking approach
• What is Server-Side Tracking? — the broader concept behind all platform-specific APIs
• Complete Guide to Event Match Quality — maximizing data quality for better ad optimization
• How Bot Traffic Wastes Your Ad Spend — why bot filtering matters for CAPI data quality

---

Ready to Set Up Pinterest Conversions API?

Skip the manual tokens, API code, and maintenance headaches. SignalBridge sets up Pinterest Conversions API, Meta CAPI, Google Enhanced Conversions, and TikTok Events API with a single integration. Recover lost conversions, improve ad optimization, and see your true ROAS — all from one dashboard.

Start your 14-day free trial today. No credit card required.