> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/open-ai-ads/onboarding.md).

# Onboarding

Open AI Ads channels use a **Pixel ID** and **Conversions API key**. This connects your Open AI Ads pixel to EdgeTag and enables server-side conversion tracking. You can also enable the browser pixel.

### Video guide

{% embed url="<https://www.loom.com/share/3ef1ff4545d5418dbc40f8bcab5be77a>" %}

### Open the channel form

Open the EdgeTag app in Shopify or go to **app.edgetag.io**.

Then go to **Site** → **Channels** → **Add Channel** → **Open AI Ads**.

### Name the integration

Start by entering a clear channel name.

Use a name like **OpenAI Ads** or **Blotout OpenAI Ads**.

This makes the connection easier to recognize later.

<figure><img src="/files/gRNhebFLXb6tRylDmGT9" alt=""><figcaption><p>Name the integration, then enter the Pixel ID and Conversions API key.</p></figcaption></figure>

### Get the Pixel ID

Open **<https://ads.openai.com>**.

Then go to **Conversions** → **Data Source**.

If you do not already have a data source, click **Create** → **Data Source** first.

<figure><img src="/files/y1ujeQUx4Xu1c7eKC53L" alt=""><figcaption><p>Open the Conversions area in Open AI Ads.</p></figcaption></figure>

<figure><img src="/files/rqSBx6YIkF1m6PUPwteE" alt=""><figcaption><p>Create a new data source if you do not already have one.</p></figcaption></figure>

Copy the Pixel ID from the data source.

The Pixel ID looks similar to `YY9Prc2zSyaMNEmXZD76eU`.

Use this value in the **Pixel ID** field in EdgeTag.

### Get the Conversions API key

In **<https://ads.openai.com>**, go to **Conversions**.

Open **Conversion keys** and create a new key if needed.

Copy the generated key.

Paste that value into the **Conversions API Key** field in EdgeTag.

<figure><img src="/files/uagCP6HFjjUAKEbMu9ID" alt=""><figcaption><p>Open Conversion keys and create a new key.</p></figcaption></figure>

{% hint style="info" %}
Store the Conversions API key securely. It authenticates server-side requests to Open AI Ads.
{% endhint %}

### Optional browser tracking

Enable **Browser Pixel** if you want EdgeTag to send events from the browser too.

When enabled, EdgeTag sends browser and server events together.

When both flows are active, both requests share the same event ID. Open AI Ads then deduplicates them.

{% hint style="info" %}
The browser pixel is optional and disabled by default. If you leave it off, EdgeTag still sends events server-side when both required credentials are configured.
{% endhint %}

### Save the channel

Once the fields are complete, click **Save & Deploy**.

If you are editing an existing channel, click **Update**.

If both the **Pixel ID** and **Conversions API key** are present, EdgeTag sends server-side events to the Open AI Ads Conversions API.

If only the **Pixel ID** is present and **Browser Pixel** is enabled, EdgeTag sends browser events only.

### Create conversion events in Open AI Ads

Create the conversion events you want to use in campaigns before you start optimizing against them.

In Open AI Ads, go to **Conversions** → **Conversion Events**.

Click **Create** → **Conversion Event**.

Use the event names that match your campaign setup.

<figure><img src="/files/5HXbUh6KCPZ99tjMFPmv" alt=""><figcaption><p>Create conversion events in Open AI Ads before using them in campaigns.</p></figcaption></figure>

### Attribution

Open AI click attribution uses the `oppref` value.

EdgeTag resolves `oppref` from the `__oppref` cookie first. If that cookie is not present, it uses the `?oppref=` URL parameter.

That value is included with each event.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.edgetag.io/channels/open-ai-ads/onboarding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.