Capture control
Every event has an off switch that works in both directions: dropped at ingestion, and the SDK stops sending it at all.
Flip an event off in the dictionary and two things happen:
The pipeline drops it at ingestion.
Any copy still arriving — from old builds, from your server — is discarded before it's stored. When a batch consists entirely of disabled events, the ingest response says dropped with the count; a mixed batch answers normally, with only the live events kept.
Devices stop sending it.
The event name joins the disabled_events list in the SDK config. On the next config refresh — launch, foreground, or within about five minutes — installed apps stop emitting it entirely, saving the network traffic too.
The kill list is also readable directly at GET /api/v1/events/config with your x-api-key — useful if your backend batches events and wants to skip disabled ones at the source. Fictura's side caches the list for about 30 seconds, so a toggle bites at ingestion almost immediately; devices pick it up with their next config refresh (up to five minutes).
Declaring works from the same table: name an event before the code that sends it ships, give it a description, and the row sits in awaiting data until the first occurrence lands — which is also a cheap way to catch a typo'd event name on day one.