Pinterest Conversion Tracking: Tag Events, Enhanced Match, and CAPI in 2026

Updated July 22, 2026.

Pinterest conversion tracking can use the Pinterest tag, enhanced match, Conversions API and offline conversion uploads. Pinterest’s current Business help lists 20 event types. For dynamic retargeting, the event/product metadata must align with the product catalog.

Verification boundary. This guide was checked against official Pinterest Business advertiser help, developer documentation, and release notes available on July 22, 2026. It does not rely on agency blogs, community posts, or third-party tutorials. Interface labels can differ during account-level rollouts. Where the official documentation describes a pilot, gradual rollout, regional limit, or incomplete availability, the guide says so rather than assuming access.

Current Pinterest events

PageVisit, ViewCategory, Search, AddToCart, Checkout, WatchVideo, Signup, Lead, Custom, AddPaymentInfo, AddToWishlist, InitiateCheckout, Subscribe, ViewContent, Contact, CustomizeProduct, FindLocation, Schedule, StartTrial, SubmitApplication

Step 1: Install the Pinterest tag base code

1. Open Pinterest Ads Manager and Conversions/Events Manager.
2. Create or select the Pinterest tag.
3. Choose direct code, Google Tag Manager or an official partner integration.
4. Install the base code on every intended page using the code generated by Pinterest.
5. Verify it with the Pinterest Tag Helper and Events Manager.

Do not install both partner and manual base tags without checking duplicate PageVisit events.

Step 2: Add event codes

Use Pinterest’s event-code generator/current documentation to add the event after the action succeeds. For dynamic pages, map values from the application or data layer.

// Illustrative Pinterest event syntax. Use the current generated code.
pintrk('track', 'checkout', {
  value: ORDER_VALUE,
  currency: 'USD',
  order_id: ORDER_ID
});

Event names can appear in documentation with display capitalization while JavaScript examples use lowercase tokens. Copy the exact event token from the current Pinterest generator or official example rather than inferring case.

Step 3: Use Google Tag Manager

1. Install or verify the site’s GTM container.
2. Add the official Pinterest tag template or current custom setup described by Pinterest.
3. Enter the tag ID from Ads Manager.
4. Create the base PageVisit tag and event tags.
5. Map value, currency, order ID, product ID, quantity and other supported fields from the data layer.
6. Attach triggers to confirmed success events.
7. Preview, test and publish.

Step 4: Configure enhanced match

Enhanced match uses consented first-party identifiers such as hashed email and external ID to improve matching. Pinterest also offers automatic enhanced match in eligible setups and says it is enabled by default for many new advertisers.

1. Review the current enhanced-match setting in Ads Manager; do not assume the default.
2. Confirm notice, consent and policy basis.
3. Choose automatic or manual enhanced match based on implementation control.
4. For manual setup, normalize and hash fields exactly as Pinterest requires.
5. Use a stable external ID that does not expose raw personal information.
6. Verify match diagnostics with Pinterest’s official tools.

Step 5: Configure Conversions API

Pinterest’s API for Conversions supports web, app and offline events. It can run with the tag; use a shared event ID to deduplicate duplicate copies.

1. Create/select the Pinterest tag/data source and obtain a token through the current authorized flow.
2. Choose direct API or approved partner integration.
3. Send event name, event time, source URL/context, value/currency, product/order data and permitted match fields required by the current schema.
4. Send events as close to real time as possible. Pinterest’s official help recommends generally within one hour.
5. When tag and API report the same event, send the same event ID for deduplication.
6. Inspect Events Manager and API responses for warnings and rejected fields.

Step 6: Meet dynamic retargeting requirements

Pinterest’s official event-code guidance requires product-aware events for dynamic retargeting. Implement PageVisit/ViewContent as applicable, AddToCart and Checkout with exact product IDs that match the catalog. Send value and currency where required.

Step 7: Offline conversions

Pinterest supports offline conversion measurement through Ads Manager CSV upload and LiveRamp, alongside API options.

1. Create the offline conversion source/workflow shown in Ads Manager.
2. Download the current template.
3. Map event time, event name, value/currency and permitted customer identifiers.
4. Upload a controlled test file and resolve errors.
5. Automate or schedule the official supported workflow at a useful cadence.
6. Reconcile matched events with POS or CRM records.

Step 8: Select campaign conversion events

Use the event that reflects the campaign objective and is eligible in the current account. For commerce, Checkout should represent a completed order, not merely the beginning of checkout. For lead generation, Lead should fire after the lead is accepted. Keep PageVisit and ViewContent as supporting signals.

QA checklist

• The Pinterest base tag fires once.
• Event token/case is copied from the current official generator.
• Checkout represents completed order under the published event definition.
• Value, currency, order ID and product IDs match source data.
• Catalog and event product IDs are identical for dynamic retargeting.
• Enhanced-match setting and consent behavior are documented.
• Raw personal information is not exposed in external IDs, URLs or unhashed fields.
• Tag and API duplicates share event ID.
• API events arrive near real time and within current timing guidance.
• Pinterest totals reconcile with orders, leads or offline records.

Common failures

Implementation blueprints

Commerce and dynamic retargeting

Do not read “Checkout” as “checkout started.” Under the measurement definition used here it represents the completed transaction; use InitiateCheckout for the beginning of the flow when that separate event is useful.

Lead and service business

Enhanced-match decision

Inspect whether automatic enhanced match is enabled rather than assuming the default. Decide whether automatic or manual mapping offers appropriate control. Use only consented permitted identifiers, normalize/hash as Pinterest requires and keep raw personal data out of URLs and external IDs.

Release acceptance criteria

• Base tag fires once.
• Event code token/case comes from the current official generator.
• Catalog and event product IDs match.
• Checkout count reconciles with completed orders.
• Enhanced-match coverage and consent behavior are reviewed.
• Tag/API copies share event ID and API delivery is near real time.

Verification record

Technically verified: July 22, 2026

Official-source rule: Every platform-specific instruction and feature statement in this article is grounded in an official Pinterest Business source. The implementation recommendations are editorial guidance from The Ad Spend and are labeled as such.

Known limits at publication

• Automatic enhanced match defaults can vary; inspect the current setting.
• Event token capitalization should be copied from the current generator/schema.
• Catalog, shopping and dynamic retargeting eligibility can vary by market and account.
• Conversions API schemas and tokens must be checked against current developer/help pages at implementation.

Official sources consulted

• Track conversions with Pinterest tag
• Add event codes
• Install base code
• Google Tag Manager and Pinterest tag
• Enhanced match
• Automatic enhanced match
• Pinterest API for Conversions
• Get started with Conversions API
• Measure offline conversions
• Verify Pinterest tag

Related conversion tracking references

• conversion tracking library
• website pixels
• conversion value