Skip to content
bucker

Ingest outcomes and drop reasons

Every item an SDK sends is answered with one of seven outcomes, and an outcome that is not accepted carries a reason: one string that says why, with a sentence the dashboard and the explainDrop helper render. The outcomes never grow. A new reason is a string filed under an existing outcome, so a client that reads only the outcome keeps working.

The reasons below are the ones the product-analytics, survey, flag and pipeline lanes write. The older reasons (rate limits, scrubbing, inbound filters, attachments, metric caps) are explained in ingest-protocol.md and in the Usage page of the dashboard, which reads the same table.

Reasons added for the analytics lanes

Reason Outcome What it means, and whether to resend
product_event_duplicate invalid The event's uuid was already seen in the last 48 hours. Nothing to resend: the first copy was kept.
product_event_overflow rate_limited A hot key's events went to the overflow lane. They are stored and weighed; this is not the key's rate limit, and there is nothing to resend.
illegal_distinct_id invalid The distinct id is not one the door will accept as a person (PA-04, through PA-03).
reserved_event_name invalid The event name is in the reserved namespace the SDK owns.
property_cap_exceeded invalid More than 500 keys, a key over 200 characters, a string over 1 KiB or an event over 64 KiB.
consent_required invalid The project requires consent and the event carried none.
personless_identify invalid An identify on a personless event.
future_timestamp invalid The timestamp is more than 23 hours in the future.
survey_closed invalid A response to a survey that is closed.
survey_duplicate_response invalid A second response from a respondent the survey allows only one from.
exposure_not_sampled sampled An exposure outside the experiment's sampled share.
interaction_rate_capped rate_limited Interaction actions past the per-page rate cap.
ingestion_filter_blocked invalid An ingestion filter in reject mode matched; the event is never stored and cannot be recovered.
ingestion_filter_quarantined accepted An ingestion filter quarantined the event. This is a receipt, like a block rule: it is counted beside the accepted tally, never added to it.
field_not_in_manifest invalid A field the project's data manifest does not declare.
server_key_required invalid A server-only event was sent with a public key (see server-ingest-key.md).
origin_policy_refused invalid The origin is outside the key's allowed origins.

Item types that carry no weight yet

Three envelope item types are in the protocol's list of known types and are queued in the weights register at weight 0: flag_exposures (counted inside the product category), survey_response (inside feedback) and assertion_counters (inside internal). The accept edge refuses each one for that item alone, under unsupported_item_type, until the server consumes it; the event beside it is unaffected.

The drop reason block_rule comes from block rules.