Set Up Conversions API (CAPI) Token

Set up Conversions API (CAPI) to enable accurate server-side event tracking with Ego Pixel.

From this guide, you will:

• Generate an Access Token to allow Ego Pixel to send server-side events to Meta.

• Generate a Test Event Code to verify that CAPI events are received correctly before going live.

• Use both values to complete your Conversions API configuration in Ego Pixel.

Step 1: Open Event Manager in your Meta Business account

1. Go to Meta Business Manager and Navigate to Event Manager. https://business.facebook.com/events_manager2

2. Select Datasets in the left menu.

3. Choose the dataset (Pixel) you want to use.

4. Open the Settings tab.

Step 2: Generate the access token

1. Scroll down to the Set up direct integration section.

2. Click Generate access token.

3. Copy the generated Access Token.

Step 3: Add the token to the app

1. Return to your app’s CAPI configuration page.

2. Paste the Access Token into the Access Token field.

3. Click Save to complete the setup.

Step 1: Open Meta Events Manager

1. Log in to your Meta Business account, then go to Events Manager. https://business.facebook.com/events_manager2

2. Select the Pixel (Dataset) that you want to test.

Step 2: Open the Test Events Tab

In the Pixel dashboard, click the Test events tab.

=> This section allows you to test events coming from your browser or server.

Step 3: Copy the Test Event Code

1. Scroll down to the Confirm your server’s events are set up correctly

2. Click Copy next to the Test Event Code.

Step 4: Paste the Code into the App

Go back to your app dashboard and paste the Test Event Code into the Test Event Code field.

=> Once the code is added, all events sent from the server will appear in the Test Events section in Meta Events Manager, allowing you to verify that your Conversions API integration is working correctly.

* Important: After completing the test, make sure to remove the Test Event Code from the app. If the code remains active, Meta will treat all incoming events as test events, and they will not be recorded in your production event data.