> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/data-activation/connectors/meta/pixel-setup-in-meta-business-manager.md).

# Pixel Setup in Meta Business Manager

Before you can configure the Meta Conversion API (CAPI) with JENTIS, you need to prepare your Pixel in **Meta Business Manager**. This setup defines which data source JENTIS will send events to.

### Create a New Pixel (Optional but Recommended)

If you want to compare your **legacy tracking setup** with the new JENTIS architecture, create a **second pixel**:

1. Log in to [Meta Business Manager](https://business.facebook.com/).
2. Navigate to **Events Manager → Connect Data Sources → Web**.
3. Select **Conversions API + Web Pixel**.
4. Give your pixel a descriptive name (e.g., *JENTIS Test Pixel*).

You will now receive a **new Pixel ID**. This allows you to:

* Keep legacy tracking untouched.
* Send new events via JENTIS to a clean data source.
* Compare results side by side.

### Use an Existing Pixel

Alternatively, you can connect JENTIS to an **existing Pixel**:

* JENTIS can send **both frontend (Pixel)** and **server-side (CAPI)** events into the same data source.
* Events from JENTIS will appear alongside existing events.
* To avoid **duplicate events**, either:
  * Disable the legacy tracking when you go live with JENTIS, or
  * Use Meta's deduplication parameters.

### Parallel Tracking Options

* **New Pixel** → Clean separation between legacy and JENTIS events. Useful for testing.
* **Existing Pixel** → Direct continuation of tracking within the same data source. Requires deduplication.

👉 Once your Pixel (new or existing) is set up, copy the **Pixel ID**. You will need this value when configuring your JENTIS Tool later.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jentis.com/data-activation/connectors/meta/pixel-setup-in-meta-business-manager.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.