Event-based tracking
Tracking event
Choose an event that is fired whenever a user interacts with your feature.
Example: Sent message or Read message
Optionally, filter the event by certain event attributes.
Example: location is "modal"
Name
Provide a name that's a good internal reference for the feature.
Example: "Messaging"
Configuration
Once you've started tracking a new feature, you can also configure the feature's target audience and adoption state KPIs.
Target audience lets you define which companies are relevant for your feature. For example, some feature are only accessible to paying customers. Learn more here
Adoption state KPIs can be configured to match your feature's desired usage pattern.
For example, for some features, users should interact with a feature multiple times to go from "Tried it" to "Using it". For other features, a single interaction is enough.
Some features are meant to be used frequently and others just once (onboarding, data import, etc.). For single-use features, you might want to disable the "Stopped"-KPI entirely. Learn more here.
Attribute-based tracking
Adoption criteria
Chose company attribute(s) that indicates active feature usage.
Example: has_slack_integration = true
Name
Provide a name that's a good internal reference for the feature.
Example: "Slack integration"
Configuration
Once you've started tracking a new feature, you can also configure the feature's target audience.
Target audience lets you define which companies are relevant for your feature. For example, some feature are only accessible to paying customers. Learn more here