# Onboarding

The Trybe integration uses both the browser pixel and the server-side Attribution API. The pixel handles visitor identification and browser event tracking; the server sends the Purchase with the captured click ID for attribution. This guide walks you through finding the required values in Trybe and activating the channel in EdgeTag.

### Video Guide

#### Step 1: Get Your API Key

1. Log in to your [Trybe Dashboard](https://jointrybe.com)
2. Navigate to **Settings → API**
3. Copy your **API Key**

{% hint style="warning" %}
Keep your API key secret. It authenticates all server-side attribution requests sent from the EdgeTag edge to Trybe.
{% endhint %}

#### Step 2: Get Your Store ID

1. In the Trybe Dashboard, navigate to **Store Settings**
2. Copy your **Store ID** — this is the identifier used to match the `ugc_vid_{storeId}` visitor cookie set by the Trybe pixel

#### Step 3: Get Your Pixel Code and Pixel Domain

EdgeTag uses the Trybe pixel to initialise `window._trybe` on the browser and capture the visitor ID (`vid`) required for attribution.

1. In the Trybe Dashboard, navigate to **Pixel Settings**
2. Copy your **Pixel Code** — it looks like `px_6524bd646578`
3. Copy your custom **Pixel CDN Domain** — e.g. `https://tracks.yourstore.com`

{% hint style="info" %}
If the Trybe pixel is already installed on your storefront via a theme script or tag manager, EdgeTag will detect `window._trybe` on the page and skip auto-injection. In that case, Pixel Code and Pixel Domain are not required in EdgeTag, but the pixel must still be present for browser-side tracking and visitor identification to work.
{% endhint %}

#### Step 4: Add the Channel in EdgeTag

1. Log in to your [EdgeTag Dashboard](https://app.edgetag.io)
2. Navigate to **Channels** and click **Add Channel**
3. Search for **Trybe** and select it
4. Enter a name for this channel

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2FmfZ83Dl2zjIBJ9KRBP4W%2Fimage.png?alt=media&#x26;token=8f6e115d-7b06-4cc7-89a1-2502d617211a" alt=""><figcaption></figcaption></figure>

#### Step 5: Enter Your Credentials

Fill in the required fields:

| Field            | Value                                                                   |
| ---------------- | ----------------------------------------------------------------------- |
| **API Key**      | The API key from Step 1                                                 |
| **Store ID**     | The store identifier from Step 2                                        |
| **Pixel Code**   | Your Trybe pixel code from Step 3 (e.g. `px_6524bd646578`)              |
| **Pixel Domain** | Your pixel CDN domain from Step 3 (e.g. `https://tracks.yourstore.com`) |

#### Step 6: Configure Excluded Events (Optional)

Use the **Excluded Events** selector to suppress specific EdgeTag events from being sent to Trybe.

{% hint style="info" %}
Excluded events are suppressed on both the browser side (no `window._trybe.track*` call) and on the server side. Since server-side attribution only fires for `Purchase`, excluding other events only affects browser pixel calls.
{% endhint %}

#### Step 7: Affiliate Link Setup

No additional configuration is required for affiliate link tracking. EdgeTag automatically captures the `?trybe=` query parameter from your Trybe affiliate URLs.

Ensure your affiliate links include the `trybe` query parameter:

```
https://yourstore.com/products/example?trybe=CLICK_ID
```

When a visitor lands on your site via this link, EdgeTag captures and persists the click ID at the edge. This click ID is then attached to the server-side `Purchase` event as the visitor ID (`vid`) for attribution.

{% hint style="warning" %}
The click ID is mandatory for server-side attribution. Without it, EdgeTag falls back to the `ugc_vid_{storeId}` cookie set by the pixel. If neither is available when a purchase fires, the attribution call is skipped.
{% endhint %}

Click **Save & Deploy** to activate the channel.