Tracking and Customers

Tracking connects product behavior to the same signed customer identity used by chat, feedback, surveys, tours, highlights, and automation.

Track Product Activity

The widget can automatically record clicks, form submissions, search terms, input focus, and input changes. Sensitive fields such as passwords, tokens, API keys, payment-card fields, and file inputs are excluded from value capture.

Send named product events when you need stable business actions such as created_project, invited_teammate, or published_release. Named events can trigger surveys and AI Automation.

Use the Tracking section to review analytics or switch to the event stream for individual activity rows. Filter by event details and time range to investigate adoption or confirm that an integration is sending the expected data.

Customer Profiles

The Customers section lists the external users known to a site. Search for a customer to review identity, metadata, activity, feedback, and conversations together.

Generate signed user tokens only on your server. A stable user ID lets Managani update one customer profile across sessions instead of creating disconnected visitors. See Widget and Portal for installation and identity setup.

Verify Identity and Events Before Automation

Choose event names that describe completed product actions rather than the position of a button. A stable name such as invited_teammate remains useful when the interface changes. Record the agreed event names with the team so surveys and lifecycle rules use the same spelling and meaning as the application.

Perform a known action with a test customer, then locate it in the event stream. Confirm the site, customer identity, timestamp, and event details before building a trigger around it. If activity appears under multiple profiles, review how your application supplies the stable signed user ID.

Automatic browser activity and named business events serve different purposes. Browser interactions help explain how someone moved through the interface; named events confirm milestones used by campaigns and rules. Review the information your application sends and keep private values out of custom event details as well as ordinary form capture.