Custom dimensions or properties are used for audience segmentation
Why it matters
Without user properties, every analytics report averages free users, paid users, enterprise accounts, and trial signups into a single number that describes no actual cohort. You cannot compare activation between plans, cannot isolate power-user behavior, cannot segment by signup date to measure cohort quality, and cannot feed PLG motion with account-level data. Anonymous event streams produce vanity metrics; identified event streams produce business intelligence.
Severity rationale
Info because segmentation enables advanced analysis but the core event pipeline functions without it.
Remediation
After authentication succeeds, identify the user with stable properties in lib/auth.ts:
analytics.identify(user.id, {
plan: user.plan,
created_at: user.createdAt,
company_size: user.companySize,
})
Use opaque database IDs, never email addresses or names, to stay within PII boundaries. Set properties for plan changes and churn events so cohort reports reflect the current state, not the signup state.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Analytics & Tracking Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from marketing-analytics·automated