What operators see in the Loxley AI dashboard: customer funnel and traffic analytics, bot fleet management, API keys, earnings and revenue accounting, branding controls, billing lifecycle and admin audit trails.
The operator dashboard is where a branded bot stops being a chatbot and becomes measurable infrastructure. This document describes the analytics and controls available to Loxley AI operators.
The funnel view tracks the human journey end to end: page views on your white-label site, referral-attributed clicks (partner codes via /r/<code> links), checkout intents, and completed conversions reconciled against billing webhooks. Traffic measurement distinguishes real users from scrapers (bot-pattern filtering on user-agents plus server-side guards), so conversion math reflects intent, not crawlers.
Operator panels list members and their lifecycle state, bot-token fleet status (up to 7 tokens in the sharded model), and per-bot health. API keys for integrations live behind the same session security, with encrypted storage for any secrets the operator supplies.
The earnings view answers three questions without CSV archaeology: what was attributed, what is unpaid, what is paid. Commission and revenue-share events are keyed to actual trades and subscription webhooks; payout batches carry references so books reconcile externally. The model definitions are public in the fee engine documentation — the dashboard implements exactly what the docs describe.
Name, logo, links, support contact — the brand surface of the member-facing bot — are operator-editable. Changes propagate across the fleet without redeploy, keeping the member experience continuous while the operator iterates on positioning.
Subscription state is Stripe-reconciled: checkout completion, renewal success/failure, cancellation, and portal-driven plan changes all converge to one server-side truth (webhook reconciler included). Double-checkout prevention and session reuse rules keep the funnel honest; forgotten-password and auth forms are rate-limited; admin actions are audit-logged.
CSRF protection on state-changing forms, role-scoped admin views, encrypted secret handling, and no member-key visibility anywhere (custody docs). The dashboard is designed so the most damaging thing an attacker can reach is metric data — never keys, never funds.
Open the operator path → All docs
Built for operators, not slippage goblins. Talk to us →