---
slug: events-abgelehnt
title: "Why are my events rejected?"
category: datenqualitaet
locale: en
updated: 2026-10-12
keywords: ["rejected","discarded","error","batch"]
questions: ["The collector does not accept events. How do I find the cause?","Rejected events","Events not arriving","Why is my event discarded?","Does Metrunio store rejected events?","What is kept in the error log?","Which field contains the email address?"]
url: https://bench.metrunio.com/en/help/events-abgelehnt
---

# Why are my events rejected?

**The collector does not accept events. How do I find the cause?**

The collector response states a status per event and, on failure, the reason. Check that response first; “Data status” in the portal additionally summarises the reasons over the period.

```json
{
  "received": 3,
  "accepted": 1,
  "duplicates": 1,
  "rejected": 1,
  "blocked": 0,
  "results": [
    { "eventId": "a", "status": "accepted" },
    { "eventId": "b", "status": "duplicate" },
    { "eventId": "c", "status": "rejected", "code": "SCHEMA_INVALID" }
  ]
}
```

| Counter | Meaning |
| --- | --- |
| accepted | stored and queued for processing |
| duplicates | the event ID was already known; not counted twice |
| rejected | formally or substantively invalid; the code names the reason |
| blocked | nothing stored because consent is missing or withdrawn, the person is on the suppression list, the quota is used up or there were too many requests; the code names the reason |

> **Note:** One invalid event never discards the whole batch. Always check the individual results, not just the HTTP status.

In the portal, rejections appear under “Data status → Data content”: as a count for the period (“Invalid format”) and as one finding per reason with its error code. They are something different from events that were accepted and only failed during processing. Those are listed under “Processing”.

We do not store the content of a rejected event. We keep the reason, time, source, website, event type and the affected fields with the type and length of the value, but never the value itself. The finding in the portal names these fields, for example “page_url” or “metadata.contact”. What exactly you sent appears only in the collector’s response to your system.

> **Note:** For PII_DETECTED this applies without exception: the email address or phone number that caused the rejection ends up neither in the raw data nor in the error log. If a key in metadata itself looks like an address, it shows as “[masked]”.

## Also asked

- Rejected events
- Events not arriving
- Why is my event discarded?
- Does Metrunio store rejected events?
- What is kept in the error log?
- Which field contains the email address?

## Related

- https://bench.metrunio.com/en/help/error-codes
- https://bench.metrunio.com/en/help/welche-events-gibt-es
- https://bench.metrunio.com/en/help/was-wird-gespeichert
- https://bench.metrunio.com/en/help/verarbeitungsrueckstand