Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt

Use this file to discover all available pages before exploring further.

  • In the Upstack dashboard, go to Event Destinations and click + New Destination.
  • Select Facebook Advertising.
  • Enter your Meta Pixel ID (15–16 digit number, no prefix).
  • Enable the Conversions API checkbox and paste your CAPI token (starts with EAA).
  • Click Create Configuration and verify the destination shows Healthy.
What this setup enablesSetting up the Meta Ads Pixel destination in Upstack Data enables dual tracking via browser pixel and server-side Conversions API (CAPI), ensuring accurate conversion data despite iOS restrictions and ad blockers.

​
Prerequisites

Before you start, you need:

​
Configuration steps

1

Sign in to Upstack Data

Sign in to Upstack Data at app.upstackdata.com.
2

Open the destination configuration

In the Upstack dashboard, navigate to Event Destinations.Click + New Destination in the top-right of the page.Add New DestinationIn the Select a Destination popup, click Facebook Advertising, then click Next.Facebook Pixel Configuration
3

Enter your Pixel ID and CAPI token

Fill in the form:
  1. Meta Pixel ID — the 15–16 digit number, no prefix (e.g., 123456789012345). Meta Pixel IDs do not have an AW- prefix; that prefix belongs to Google Ads.
  2. Check the box Check to enable sending events via Facebook Conversions API.
  3. CAPI token — starts with EAA, approximately 190 characters long.
The Conversions API checkbox must be selected for server-side tracking to work.
Need help finding these?
4

Create the configuration

Click the Create Configuration button.You should see a confirmation message and the Meta destination will appear in your Event Destinations list.
5

Verify the destination is healthy

In the Upstack dashboard, the Meta destination card should display Healthy with a green status indicator within 5 minutes.If the status shows Unhealthy:
  • Confirm your Pixel ID is correct (15–16 digits, no leading/trailing spaces, no prefix).
  • Confirm your CAPI token is the full string starting with EAA.
  • Confirm the Conversions API checkbox was selected.
  • See How to update your CAPI token if your token may have expired.