> ## Documentation Index
> Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pinterest Ads

> Send conversion events to Pinterest's Conversions API for ad campaign optimization, audience building, and attribution.

<Note>
  **Data direction:** This is a **destination** — Upstack sends event and conversion data **out** to this platform via server-side APIs.
</Note>

Pinterest's Conversions API is the server-side counterpart to the Pinterest Pixel. Upstack sends purchases, add-to-carts, and other conversion events directly to Pinterest from your account, bypassing browser ad blockers and giving Pinterest's algorithm stronger signal for ad optimization.

Server-side delivery consistently achieves higher event match rates than browser-only tracking. Combined with the Pinterest browser pixel, the two work together — Pinterest's deduplication logic keeps only one conversion when the same event arrives from both sources.

## How It Works

When a visitor takes an action on your store, Upstack:

1. Captures the event through the Upstack Pixel and matches it to a known visitor profile.
2. Enriches the event with hashed PII (email, phone) and click IDs (`epik`) when available.
3. Sends the enriched event to Pinterest's Conversions API using your Pinterest Pixel Tag ID and Conversions API access token.
4. Logs the response so you can monitor delivery and match rates from the Upstack dashboard.

## Set Up Pinterest

Follow the onboarding guide for the full end-to-end setup, or jump to a specific step.

<CardGroup cols={2}>
  <Card title="Onboarding guide" icon="book" href="/guides/pinterest-ads/complete-how-to-guide-for-onboarding-pinterest-in-upstack-data">
    Complete step-by-step walkthrough for connecting Pinterest to Upstack.
  </Card>

  <Card title="Configure destination" icon="sliders" href="/guides/pinterest-ads/how-to-configure-pinterest-destination-in-upstack-data">
    Add and configure the Pinterest destination inside the Upstack dashboard.
  </Card>

  <Card title="Find Pixel Tag ID" icon="magnifying-glass" href="/guides/pinterest-ads/how-to-find-pinterest-pixel-tag-id">
    Locate an existing Pinterest Pixel Tag ID in your Pinterest Ads account.
  </Card>

  <Card title="Create Pixel Tag ID" icon="plus" href="/guides/pinterest-ads/how-to-create-a-new-pinterest-pixel-tag-id">
    Create a new Pinterest Pixel Tag if you don't already have one.
  </Card>

  <Card title="Find Advertiser ID" icon="id-card" href="/guides/pinterest-ads/how-to-find-pinterest-advertiser-id">
    Locate the Pinterest Advertiser ID required to identify your ad account.
  </Card>

  <Card title="Generate API access token" icon="key" href="/guides/pinterest-ads/how-to-generate-pinterest-conversion-api-key-access-token">
    Generate the Conversions API access token Upstack uses to send events.
  </Card>

  <Card title="Disable Shopify data sharing" icon="ban" href="/guides/pinterest-ads/how-to-disable-pinterest-data-sharing-in-shopify">
    Turn off Shopify's native Pinterest data sharing to prevent duplicate events.
  </Card>
</CardGroup>

## FAQ

<AccordionGroup>
  <Accordion title="Do I still need the Pinterest browser pixel?">
    You don't need the browser pixel for Upstack to send events — server-side delivery works on its own. However, running both gives Pinterest the strongest signal. As long as the Pinterest Pixel Tag ID matches between your browser pixel and the Upstack destination, Pinterest's deduplication logic prevents double-counting.
  </Accordion>

  <Accordion title="Why disable Shopify's native Pinterest data sharing?">
    Shopify's built-in Pinterest integration also forwards events to Pinterest. If both Shopify and Upstack are sending the same events without coordination, Pinterest can count conversions twice. Disabling Shopify's native sharing lets Upstack handle delivery exclusively, with the browser pixel for real-time signal and the Conversions API for reliability. See [Disable Shopify data sharing](/guides/pinterest-ads/how-to-disable-pinterest-data-sharing-in-shopify).
  </Accordion>

  <Accordion title="What's the difference between the Pixel Tag ID and the Advertiser ID?">
    The **Pixel Tag ID** identifies a specific tracking pixel inside your Pinterest account. The **Advertiser ID** identifies the ad account that owns the pixel. Upstack needs both: the Pixel Tag ID to attribute events to the correct pixel, and the Advertiser ID to send them on behalf of the right ad account.
  </Accordion>

  <Accordion title="How long does it take for events to appear in Pinterest?">
    Once the destination is active, events typically appear in Pinterest's Events Manager within 5-10 minutes. The first events confirm the connection is working — match quality and conversion attribution build over the following 24-48 hours as Pinterest correlates events to ad clicks.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Conversion API Forwarding" icon="lightbulb" href="/concepts/conversion-api-forwarding">
    How Upstack Signal forwards events to ad platforms via server-to-server APIs.
  </Card>

  <Card title="Identity Resolution" icon="fingerprint" href="/concepts/identity-resolution">
    How Upstack ID matches anonymous visitors to known customers for higher match rates.
  </Card>

  <Card title="Destinations Overview" icon="arrow-right-from-bracket" href="/destinations/overview">
    Browse all available destinations and how Upstack delivers data to each.
  </Card>

  <Card title="Events Not Reaching Destination" icon="wrench" href="/troubleshooting/events-not-reaching-destination">
    End-to-end diagnostic guide when events aren't arriving at any destination.
  </Card>
</CardGroup>