Adoption & Engagement

How actively lender teams use the product — write-actions from the API audit log, by feature and by customer

snapshot

Range

Activity over time

Write-actions per day (bars) and daily active users (line, right axis)

What people actually do

Actions bucketed into endpoint families · the mix tells you which workflows carry the product

Engagement by customer

Package-scoped actions attributed via the package's tenant · sorted by actions in the selected range · Δ compares to the prior equal-length window

Methodology. One row per mutating API request in audit_log (the log captures writes — POST/PATCH — not reads, so this measures doing, not viewing). Internal /admin actions are excluded. Endpoints are normalized to families (package public IDs and numeric/uuid segments stripped) and bucketed by keyword: File uploads, Overrides, Income modeling, Package settings, Package management, Session & prefs, Onboarding & legal, Other — raw endpoint paths are never inlined (they can embed package identifiers). Customer attribution uses the action's package → tenant; actions with no package (sessions, legal) count in the totals but not the per-customer table. Internal/test tenants excluded (same list as the Revenue Report); weekends (Sat/Sun, Eastern) excluded; lines smoothed with a centered moving average (3-day at 30d, 5-day at 90/180d; none at 7d) while KPIs and tables stay raw. "Daily active users" = distinct profiles acting that day (averaged over weekdays for KPIs — distinct users across a multi-day window is not derivable from daily data). Rolling 180 days · laminr-prod.