Destination Forwarding Errors

If your destination health card shows a red dot with an error count, events are being received by PixelsCleared but failing to forward. Here is how to diagnose and fix the most common causes.

Check Error Counts

Go to Gateway > Overview and look at the destination health cards. A red dot with a count (for example, "7 errors today") means forwarding is failing. The count resets daily.

Invalid Credentials

The most common cause of forwarding errors is incorrect or outdated credentials.

Meta CAPI:

• Verify the Pixel ID is a numeric value (no letters or hyphens).
• Verify the Access Token starts with EAAB and has not expired. Meta access tokens can be revoked or expire depending on how they were generated.
• Generate a new access token in Meta Events Manager > Settings > Conversions API.

GA4 Measurement Protocol:

• Verify the Measurement ID matches the format G-XXXXXXXXXX.
• Verify the API Secret was generated for the correct data stream. Each stream has its own secret.
• Check that the data stream is active in Google Analytics > Admin > Data Streams.

Webhook:

• Verify the Webhook URL is accessible and returns a 2xx status.
• If you set a webhook secret, verify it matches on both sides.

To update credentials:

1. Go to Gateway > Destinations.
2. Find the destination with errors and click Edit.
3. Update the credentials and click Save.
4. Trigger a test event from your website to verify forwarding resumes.

Expired Access Tokens

Meta CAPI access tokens can expire or be revoked. If your destination was working and suddenly stopped:

1. Open Meta Events Manager and check the token status.
2. Generate a new access token if the old one has expired.
3. Update the token in PixelsCleared at Gateway > Destinations > Edit.

PixelsCleared does not automatically detect token expiration. The error will persist until you update the token.

Event Format Mismatches

Destination platforms expect events in specific formats. If your event payload does not match the expected schema, forwarding will fail.

Common mismatches:

• Missing required fields -- Meta CAPI requires event_name and at least one user identifier. GA4 requires a valid measurement ID in the payload.
• Invalid event names -- Some platforms reject event names with special characters or spaces.
• Invalid currency codes -- Purchase events must use a valid ISO 4217 currency code.

Check the recent events table on the Insights page to see what event names and payloads are being sent. Compare them against the destination platform's documentation.

Rate Limits

Destination platforms enforce rate limits on their APIs. If you are sending a high volume of events, you may hit these limits:

• Meta CAPI -- Allows approximately 1,000 events per second per pixel. Rate limit errors are temporary and self-resolve.
• GA4 -- Allows approximately 25 events per second per measurement ID.
• Webhooks -- Depends on the receiving server's capacity.

Rate limit errors appear as temporary failures in the error count. They resolve on their own as the rate limit window resets. If you consistently hit rate limits, consider batching events or contacting support about higher limits.

Verifying the Fix

After making changes:

1. Open your website and trigger an event (page view, form submit, or other tracked action).
2. Return to Gateway > Overview and check the destination health card.
3. The error count should stop increasing and the dot should turn green as successful forwards resume.

If errors continue after correcting credentials and verifying event formats, contact support at pixelscleared.com/contact with your tenant subdomain and the destination type that is failing.