Customer feedback and usage analytics
Understand customer feedback and AI usage across your Incele workspace, with searchable, filtered, paginated reports.
Customer feedback
Customers can submit a message of up to 500 characters from a hosted website or your external customer application. Every feedback record belongs to one workspace. Signed-in submissions include the customer user ID; guests have no user ID.
A visitor session can submit once every 30 minutes, with three submissions per UTC calendar day. The server applies both checks atomically, including concurrent requests. A rejected submission returns HTTP 429. Creating a new browser session is not a way to identify a real person: session limits are not a global per-person limit.
Guest clients must bootstrap first, retain the returned signed guest token and a stable guest-device ID, then send both headers with feedback. Signed-in customer clients send their separate tenant visitor credential. Never substitute the integration owner's key for a customer session.
POST /v1/workspaces/{workspaceId}/experience/feedback
Authorization: Bearer YOUR_SERVER_INTEGRATION_KEY
X-Guest-Device-Id: YOUR_STABLE_VISITOR_DEVICE_ID
X-Guest-Token: SIGNED_TOKEN_FROM_BOOTSTRAP
Content-Type: application/json
{"message":"The product guidance helped me compare these two options."}
The integration needs visitors:write. Feedback collection still respects the workspace's site access policy.
Review feedback
Open Feedbacks in the workspace dashboard. Search message content, filter signed-in customers or guests, set a date range, and sort by received date. Pagination and Refresh update the report without navigating away.
Account integrations can use GET /v1/workspaces/{workspaceId}/feedbacks with workspace:read. Supported query parameters are page, pageSize (1–100), search, visitor (ALL, GUEST, USER), userId, from, to, and sortDirection. Dates use YYYY-MM-DD and UTC boundaries.
Workspace members can only read the selected workspace's feedback. The Incele support team can also review submissions to support the platform. Internal visitor/session keys are never returned in the report.
Usage by user
Open Analytics → Overview → Usage by user. The default period is the last 30 days. Select dates and actor type, search a customer by name, email or ID, and sort or paginate the results.
The report separates customers, guests, staff and kiosks. It shows recorded activity, AI requests and credits consumed, product and routine AI requests, face analyses, Comprehensive requests, product views, visits and last activity. Totals use all matching rows, not just the current page.
Use GET /v1/workspaces/{workspaceId}/usage-report with workspace:read for the same report. Query parameters include page, pageSize, search, actorType, userId, from, to, sortBy (credits, requests, lastUsedAt, name) and sortDirection (asc, desc).
Use Activity details to browse individual recorded events, optionally filtered by user ID. The paginated endpoint is GET /v1/workspaces/{workspaceId}/usage-report/events, with the same date, user and actor filters and workspace:read. It omits internal session identifiers, IP addresses and request metadata.
Only recorded events appear. Blocked or cancelled AI calls do not become successful AI usage. The credit ledger remains the source of truth for purchases, grants, refunds and balances; analytics credit totals describe successful AI consumption in the chosen period.