Skip to content
Pixel Relay

Failed events

See which events Meta refused and why, fix the cause, and clear the failures once they are handled.

1 min read Updated 8 Oct 2026

When Meta refuses an event, the relay keeps it with Meta's reason. The dashboard's Failed to deliver tile counts them, and clicking it opens the Failed to deliver page.

Walkthrough Find out why Meta refused events 1 / 5
Step 1: On the dashboard, click Failed to deliver. Step 2: Errors groups the failures by the message Meta sent back, most frequent first. Step 3: Click an error to see only the events it affected. Step 4: Each row shows the website, the event and Meta's answer. An access token error means the token needs replacing. Step 5: Once it is fixed, Clear this error takes these events off the list and the dashboard count.

On the dashboard, click Failed to deliver.

Errors groups the failures by the message Meta sent back, most frequent first.

Click an error to see only the events it affected.

Each row shows the website, the event and Meta's answer. An access token error means the token needs replacing.

Once it is fixed, Clear this error takes these events off the list and the dashboard count.

  1. Step 1: On the dashboard, click Failed to deliver.
  2. Step 2: Errors groups the failures by the message Meta sent back, most frequent first.
  3. Step 3: Click an error to see only the events it affected.
  4. Step 4: Each row shows the website, the event and Meta's answer. An access token error means the token needs replacing.
  5. Step 5: Once it is fixed, Clear this error takes these events off the list and the dashboard count.

Reading the page

  • Errors groups the failures by Meta's message, with how many there are and when one was last seen. Click an error to show only its events, and Show all errors to go back.
  • Events lists each failed event: when, which website, which event, and Meta's error. Open Meta's response for Meta's full answer.
  • Filter by Website and by period at the top.

Common errors

Meta says What to do
Invalid OAuth access token, or Session has expired The access token was revoked or expired. Generate a new one and save it in the website's settings.
Unsupported post request, or Object with ID does not exist The Pixel ID is wrong, or the token belongs to a different pixel. Check both.
Permissions error The token's user has lost access to the pixel. Generate a new token with an admin of the pixel.
Invalid parameter Usually a value or currency Meta cannot read. Check what your site sends with the event.

After fixing the cause, use Send test event on the website's settings page to confirm, see Send a test event. Events that already failed are not sent again.

Clearing failures

Failures stay on the list until staff clear them, so a fixed problem still shows until then. Let your account team know once it is fixed.

Related articles

Events are missing in Meta Work out where events stop between your site, Pixel Relay and Meta, and fix the most common causes. Create a Conversions API access token Generate the access token that lets Pixel Relay send server events to your Meta pixel.

Still stuck?

Tell us what you are trying to do and we will help you set it up.

Contact us