Skip to main content

​
Overview

If you’ve seen warnings like “My Conversions API is not getting any events” or received an email that your Meta Pixel is unhealthy, it means your CAPI token needs to be refreshed. This guide walks you through updating your Meta CAPI token in Upstack Data so events flow correctly, attribution stays accurate, and your pixel remains healthy.
  • Sign in to Upstack Data at app.upstackdata.com and open Event Destinations.
  • Click your Meta destination to edit it.
  • Paste a fresh CAPI token (starts with EAA) into the Conversions API token field.
  • Click Update Configuration and verify the destination shows Healthy.

​
Prerequisites

Before you start, you need:

​
Configuration steps

1

Sign in to Upstack Data

Sign in to Upstack Data at app.upstackdata.com.In the Upstack dashboard, navigate to Event Destinations.Upstack dashboard Event Destinations page
2

Open your Meta destination

In the Event Destinations list, click your Meta destination to edit it.Meta destination card in Event Destinations listConfirm the Check to enable sending events via Facebook Conversions API checkbox is selected, then paste your new CAPI token into the Conversions API token field. Replace the existing value entirely.Meta destination edit form with CAPI token field
The CAPI token starts with EAA and is approximately 190 characters long. Leave the Pixel ID unchanged (15–16 digit number, no prefix).
Need help finding these?
3

Save the updated configuration

Click Update Configuration to save the change.Update Configuration button to save Meta destination changes
4

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 still shows Unhealthy:
  • Confirm the new CAPI token starts with EAA and was pasted in full (no truncation or whitespace).
  • Confirm the user who generated the token has admin access to the Meta Business Manager that owns the pixel.
  • See Why is my Meta EMQ panel showing zeros? for token-permission troubleshooting.