> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/destinations/advertising/openai-ads.md).

# OpenAI Ads

OpenAI Ads (ChatGPT Ads) measures conversions from your OpenAI campaigns. Chord sends your events to OpenAI from the browser and from the server. Use both where you can.

## What each version does

* [**OpenAI Ads Pixel**](/activate/event-streaming/destinations/advertising/openai-ads/openai-ads-pixel.md) runs in the shopper's browser. It reports page views, product views, add-to-cart and purchases. It also captures OpenAI's `oppref` click identifier, which links a conversion back to the ad that produced it.
* [**OpenAI Ads Conversions API**](/activate/event-streaming/destinations/advertising/openai-ads/openai-ads-conversions-api.md) runs on Chord's servers. It still reports conversions when a shopper has an ad blocker, a browser that limits tracking, or an expired cookie.

## Why use both

The browser version captures the click identifier that the server version needs but cannot collect for itself. The server version survives ad blockers and closed tabs. Together they give OpenAI the most complete view of each conversion.

## How they deduplicate

Both versions send the Chord message ID as the event ID. OpenAI counts a conversion once when the pixel ID, event name and event ID match. Use the same Pixel ID and the same Custom Event Mapping on both destinations. A different Pixel ID makes OpenAI count one purchase twice.

The same applies to events you send to OpenAI outside Chord. Reuse the Chord message ID as your event ID and OpenAI merges them instead of counting twice.

Deduplication by event ID only works when both copies come from the same Chord event. The storefront and a server-side source, such as the Shopify order webhook, send separate Chord events with different message IDs, so those copies do not share an event ID.

## Set up

* [OpenAI Ads Pixel](/activate/event-streaming/destinations/advertising/openai-ads/openai-ads-pixel.md)
* [OpenAI Ads Conversions API](/activate/event-streaming/destinations/advertising/openai-ads/openai-ads-conversions-api.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/activate/event-streaming/destinations/advertising/openai-ads.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.