MTU Billing
SegOps bills on **monthly tracked users (MTU)**. An MTU is a profile you can act on — not bots, not one-time bounces. The rule is one sentence:
An MTU is a resolvable, engaged, human profile.
The three gates#
A profile counts as an MTU for the period only if it passes all three, computed on its canonical (alias-resolved) id:
| Gate | Rule |
|---|---|
| Identified | Has a real user_id → always counts (an identified user is activatable even with one event). |
| Engaged anonymous | An anonymous-only profile counts only after ≥ N events in the period. N is set per plan, default 3. |
| Human | bot_class is human. Bots and crawlers never count. |
Because counting runs on the resolved canonical id, a visitor who browses anonymously and then logs in is one MTU, not two — the anonymous activity collapses onto their user. See Identity Resolution.
What does not cost an MTU#
- A one-page anonymous bounce (under the engagement threshold).
- Search and AI crawlers (
known_bot) — Googlebot, GPTBot, ClaudeBot, etc. These stay visible in Discovery Intelligence but are never billed. - AI agents acting on a user's behalf (
ai_agent) are metered to their own SKU, free today.
Threshold configuration#
The engaged-anonymous threshold N is a per-PlanVersion setting
(mtu_event_threshold, default 3). Raising it bills fewer low-intent anonymous
profiles; lowering it counts more.
How it's metered#
The MTU is computed each sync over your billing period and reconciled into
the meter that drives billing (monotonically — a mid-period identity merge never
un-bills a user already counted). The computed figure is also exposed on the
usage record's mtu_computed field so you can audit it directly.
BILLING_MTU_COMPUTED controls the meter (on by default). Setting it to false
reverts to the legacy first-touch meter — useful for re-running a shadow
comparison.
See also#
- How we count MTU — plain-language explainer
- Identity Resolution
- Plans & Billing