They are treated differently depending on which “auto” events you mean:
1. Session Replay checkpoint event
- The event $mp_session_record (Session Recording Checkpoint) that’s created when a replay starts is explicitly excluded from:
- Monthly Events billing [Pricing]
- MTU calculations [MTU billing]
- So this replay-specific “auto” event does not count toward your total billable events.
2. Autocapture events (e.g. [Auto] Page View, [Auto] Element Click, rage/dead clicks via Autocapture)
- When you enable Autocapture in the JS SDK, it automatically tracks page views, clicks, form interactions, dead clicks, rage clicks, etc., as real events (names start with $mp_ and show as [Auto] ... in the UI). [Autocapture overview]
- These Autocapture events are normal, billable events and do count toward your total events. [Autocapture heatmap alt]
3. Heatmap / rage / dead click events from record_heatmap_data (Session Replay option)
- When enabled via record_heatmap_data, click, rage click ($mp_rage_click), dead click ($mp_dead_click), and page leave events are:
- Only captured during a recording session
- Explicitly exempt from your plan data allowance (i.e., they do not count toward billable events). [Replay heatmaps]
So:
- Replay checkpoint + replay heatmap events → excluded from billable event counts.
- Autocapture “[Auto] …” events → included in billable event counts by default.
