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

# Onboarding

The Outbrain channel offers a simple onboarding experience using a **Query Key** and **event mapping** to seamlessly connect your Outbrain account with EdgeTag. Once configured, this integration allows your website to send conversion events to Outbrain, enabling accurate campaign attribution and improved optimization.

Let’s walk through the setup steps.

### Video Guide

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

### Add Channel

<figure><img src="/files/LJftNxdpKSMzQRlBJwFE" alt=""><figcaption></figcaption></figure>

To add a channel, start by entering the **channel name**. We recommend using a clear, descriptive name to make it easier to identify and debug issues later. After naming the channel, **configure click ID tracking** and map your conversion events to complete the setup.

### Set Up Click ID Tracking

Navigate to the Campaigns tab in your Outbrain dashboard and select the campaign you wish to track with EdgeTag.

<figure><img src="/files/OEFciwlqrzqhF8vSzXmb" alt=""><figcaption></figcaption></figure>

Once the campaign is selected, scroll down to the Tracking section. Add the following parameter to capture click IDs:

```
obclid={{ob_click_id}}
```

This parameter enables EdgeTag to associate conversions with specific Outbrain clicks, ensuring accurate attribution

<figure><img src="/files/dvEhiqRRx1oU3WngmsHm" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Make sure the click ID parameter is added to all campaigns you want to track.
{% endhint %}

You may use any parameter name you prefer (for example, `custom_click_id` or `out_click`). However, ensure that the exact same parameter name is entered in EdgeTag’s Query Key field. Matching these values is required for proper click ID tracking and accurate attribution.

<figure><img src="/files/qLkXd09pw1kaufEN8pkK" alt=""><figcaption></figcaption></figure>

### Create Conversion Events in Outbrain

<figure><img src="/files/TDou6t22eNT83fuDRzGJ" alt=""><figcaption></figcaption></figure>

Configure your conversion event using the following settings:

**Event Type**: Select **Event**

For the Event Name field, you'll need to copy the exact event name from EdgeTag. Navigate to your EdgeTag event mapping section, add the appropriate event mapping, and copy the exact Outbrain Event Name.

<figure><img src="/files/bqoyNmCFJVDQGB4mjUlH" alt=""><figcaption></figcaption></figure>

**Name**: Use a clear, descriptive name like blotout\_purchase to make the event easy to identify and manage.

<figure><img src="/files/g56ASqV1oCOEjaShw02A" alt=""><figcaption></figcaption></figure>

Once these settings are configured, click on Create Conversion.


---

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