- Unknown — Upstack hasn’t received a delivery result for this destination yet.
- Inactive — the destination is turned off.
- Go to Destinations → click the affected destination.
- Check that every credential field is filled in with values from the correct account — for Meta, the Pixel ID and Conversions API access token; for other destinations, the token or API key their setup guide describes.
- If a token or key expired or was revoked, generate a new one in the destination platform:
- Meta: How to update your Facebook (Meta) Conversion API key
- Reddit: How to update your Reddit Conversions API token
- Other destinations: follow that destination’s “How to generate…” guide — for example TikTok, Snapchat, Pinterest, Klaviyo, or Omnisend.
- Paste the new value into the destination’s credential field and save.
- Confirm the destination status changes to Healthy.
- Trigger a test event on your store and check the Real-Time Events feed (System → Events Manager) to verify the destination receives it.
- For Meta specifically: if you manage multiple Business Managers, generate the token from the account that owns the target Pixel — a token from a different account will cause a permissions error.
Google Ads is the only destination that uses OAuth. To reconnect it, open the destination, click Connect Google Ads, and complete the Google consent screen, granting all requested permissions, including offline access. Pop-up blockers can silently prevent the OAuth window from opening — if clicking Connect Google Ads does nothing, allow pop-ups for
app.upstackdata.com.Still stuck? Contact support@upstackdata.com with your Pixel ID and a description of the issue. We typically respond within a few hours.
Related guides
Connect a destination
Connect Meta CAPI as your first server-side destination with Upstack Signal.
Why integrations disconnect
Why connections break and how to prevent future disconnections.