Match every event_type to a real billable metric or the event vanishes with no error. POST a bare array to /v1/ingest, never an object wrapper. Batch up to 100 events and use deterministic transaction_id values so retries are safe. Backfill with correct timestamps, and size your grace period around your pipeline's max latency.

Context: Official docs (Metronome events reference, metronome-industries org): documents that events whose event_type has no matching billable metric are silently ignored, that /v1/ingest expects a bare JSON array (an object wrapper returns an unclear 400), that the max batch is 100 events, that transaction_id is the dedupe key (deterministic IDs make retries safe), that billing period comes from the event timestamp not arrival time, that events past the grace period do not count toward the closed period, and that ingest aliases map multiple source IDs to one customer.