Skip to content

mixpanel_event_drop_filter (Resource)

Manages a Mixpanel event drop filter — a rule that blocks ingestion of events matching a specific event name. Useful for filtering out debug events, test data, or deprecated events at the ingestion layer.

Warning

Workspace routing. When the project has workspaces, the provider issues drop-filter requests through the workspace-scoped mount (/api/app/workspaces/{workspace_id}/data-definitions/...) — the same route the Mixpanel web UI uses — targeting the project's canonical workspace (the global "All Project Data" workspace, else the default, else the first). Both the workspace and project mounts address the same project-keyed drop filters, so no data divergence occurs either way; if the credential is not a member of the canonical workspace (the workspace mount rejects non-members with a 404 before any change is made), the provider transparently falls back to the project-scoped mount. Projects without workspaces always use the project mount.

Example Usage

resource "mixpanel_event_drop_filter" "drop_debug" {
  project_id = 1234567

  event_name = "debug_ping"
  active     = true
}

Schema

Optional

  • active (Boolean) Whether the drop filter is active (blocking ingestion).
  • event_name (String) The event name to drop.
  • id (String) The drop filter id.
  • project_id (Number) The project ID (defaults to the provider project). Changing it forces a new resource.

Read-Only

  • created (String) ISO 8601 timestamp when the filter was created.
  • deleted (String) ISO 8601 timestamp when the filter was deleted, if applicable.
  • display_name (String) Display name of the event (from Lexicon).
  • legacy (Boolean) Whether this is a legacy drop filter.

Import

terraform import mixpanel_event_drop_filter.drop_debug '1234567:filter_abc123'

Format: PROJECT_ID:FILTER_ID.