# META Conversion API (CAPI) Activation

Once your Pixel is set up in Meta Business Manager, the next step is to activate the **Conversion API (CAPI)**. This ensures that JENTIS can send **server-side events** directly to Meta.

### 1. Access the Conversion API Setup

1. In [Meta Business Manager](https://business.facebook.com/), go to **Events Manager**.
2. Select your **Pixel ID** (new or existing).
3. Navigate to **Settings → Conversion API**.
4. Click **Set Up Conversions API**.

### 2. Generate an Access Token

* Meta requires an **Access Token** to authorize server-to-server communication.
* In the setup flow, choose **Generate Access Token**.
* Copy and save the token securely.

{% hint style="warning" %}

* Meta will not store the token for you.
* If it is lost, you must generate a new one (which invalidates the old one).
  {% endhint %}

### 3. Optional: Test Event Code

For testing your JENTIS implementation, Meta provides a **Test Event Code**:

1. In the Pixel’s **Test Events** tab, copy the test code (e.g., `TEST123...`).
2. Use this code in your JENTIS Tool configuration during testing.
3. Events will then appear in **real-time** inside Meta Events Manager under **Test Events**.

### 4. When to Activate

You can choose whether to:

* **Activate CAPI immediately** → Recommended if you are ready to implement with JENTIS.
* **Activate later** → Possible if you first want to define events and parameters in detail.

{% hint style="success" %}
At this point, your **Pixel ID**, **Access Token**, and optional **Test Event Code** are ready.
{% 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.jentis.com/data-activation/connectors/meta/meta-conversion-api-capi-activation.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.