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.

Custom events generated dynamically by EdgeTag are server-side only.

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.