# Create a Facebook Pixel (now with Datasets)

### Create a Facebook Pixel (now with Dataset)

{% hint style="info" %}
:owl::owl:This doc explains how to best create a Facebook Pixel ID that works with Omega, following up on the current Facebook shift from [Pixel to Datase](https://www.facebook.com/business/help/750785952855662?id=490360542427371)[ts](https://www.facebook.com/business/help/750785952855662?id=490360542427371)
{% endhint %}

### The new and (somewhat) confusing Facebook Pixel creation flow

Unless you live under a rock, you know that the “Add” button under your Pixel Tab inside Facebook Business Manager **has been grayed out.**

<figure><img src="https://lh7-us.googleusercontent.com/wg_7v-VtvExU5hTBWHTeoAd4ZkgVrPyA8u7RzLajockHTcTax45KpcToonbmbPVEtnPobHZWPk_VhEvqaW3zapTnobrJKJEc4evknNmSPXZSmPhvxGWO3bG_58F8JY-FgLSQX3K-c9bhShAM3H3lvFQ" alt=""><figcaption></figcaption></figure>

:question:Does that mean you can no longer track & optimize your Facebook Ad with event data? Of course not, otherwise the Facebook Ad business would go out of business.

### What’s happened? :eyes:

**Pixel has got a new home - within datasets**

Simply put, a Pixel ID is a box ID that houses all your website data.

:bulb:Now that box moves into an even bigger container, a warehouse aka the dataset. Within this warehouse, your website data can live alongside mobile app data (if you have one), offline data (like in-store purchases), and messaging events. For the record, Omega only sends **web events.**

<figure><img src="https://lh7-us.googleusercontent.com/xBLabJIVOijMgd0Si5Qlf3l_H3p1ofDEhgdMrwhP7JpbyvAx3QFuTjYSSOWP5OrnNpz7CzDo0GhSg1wx2WB-oHJYKg0SrVPorL50sIL0Tf_72gXWUOFUqBueEaJaOuCnqFBKeD4_aniRwZxpGI3a4s8" alt=""><figcaption></figcaption></figure>

:point\_right:The results? All these 4 data sources will live under the same dataset ID, which means, your pixel ID is now the Dataset ID.

### Create a new dataset ID (step-by-step guide) to use with Omega

Step 1: In your business settings, go to **Data sources -> Datasets**

Step 2: Click "**Add**" to create a new dataset that houses your pixel data (website data)

Step 3: Name your dataset, then click **Create**

<figure><img src="https://lh7-us.googleusercontent.com/n00hL0AVVnFsqfW-_59JGK69mXvAYlOVzN5lsrozaWnqlXl6wUT7kJou5j1XkjaCvhMGuusBmipLRuPkQScm9BSCXMV6LEBCUWMdymfuTkiIC8Pm_jwz0FHPltk5Y5ur9qc3Ex9Hyu607A898xREyNw" alt=""><figcaption></figcaption></figure>

Step 4: Copy this **dataset ID** and pass it to Omega as Pixel ID

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

The Omega in-app setup flow remains the same once you get the ID, so you can follow our guide here.

{% content-ref url="/pages/R6WQDsWTbpbJoWH3yzk8" %}
[Get your Pixels ready](/getting-started/get-your-pixels-ready.md)
{% endcontent-ref %}

Step 5: Follow the test events guide (unchanged) to verify if your pixel is working

{% content-ref url="/pages/lAYxLFbNpwqwAReOhNRu" %}
[Monitor what's sent](/getting-started/monitor-whats-sent.md)
{% endcontent-ref %}

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

Once your pixel is ready (with Conversion API enabled), your Overview tab should look something like this:

<figure><img src="https://lh7-us.googleusercontent.com/FDED6PomkWqASE-O1y9T2EYjETsYf2tX21H3vKBg4GsejMGZfkvXXvjZoWWjvXwxgJjHJivMNbibjgcqv_ah_QHF82iN2Lu2xfjySgk4JKfLlhSkz97IGgZrUcvtkS8L5OIX2NhoOXO3etMkHo8ROGI" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
:tada:That's it! Contact us via the in-app chat if you need anything. Our support team is always ready to help!
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.twoowls.io/create-a-facebook-pixel-now-with-datasets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.