> 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/configuration.md).

# Configuration

Now that the basic onboarding is complete, let's review the fields in the form.

### Pixel ID

This field is required.

Use your Open AI Ads **Pixel ID** to identify the destination for browser and server events.

EdgeTag uses the same value to initialize the browser pixel and send Conversions API events.

### Conversions API key

This field is required for server-side delivery.

Use this secret bearer token to authenticate requests to the Open AI Ads Conversions API.

Store it securely.

### Enable browser pixel

This field is optional and is **disabled by default**.

When enabled, EdgeTag loads the Open AI Ads browser pixel and sends events from the browser in addition to the server-side stream.

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

{% hint style="info" %}
Custom events generated dynamically by EdgeTag are server-side only.
{% endhint %}

### Configuration fields

| Field                | Required | Description                                                                     |
| -------------------- | -------- | ------------------------------------------------------------------------------- |
| Pixel ID             | Yes      | Used for browser pixel initialization and server-side Conversions API delivery. |
| Conversions API key  | Yes      | Bearer token used to authenticate server-side Conversions API requests.         |
| Enable browser pixel | No       | Loads the Open AI Ads browser pixel and sends browser events.                   |

### Delivery behavior

* **Pixel ID + Conversions API key** — server-side delivery is enabled.
* **Pixel ID + Conversions API key + Browser Pixel enabled** — browser and server delivery are both enabled.
* **Pixel ID only + Browser Pixel enabled** — browser-only delivery is enabled.

If the **Conversions API key** is missing, EdgeTag cannot send server-side events.


---

# 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/configuration.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.