Your Feature list is how Chameleon knows what your product actually does, and every Agent reads from it. Compass uses it to describe what a user did in terms you recognize and to attribute friction to the right place. Copilot uses it to suggest relevant Experiences instead of generic ones. Prism reads each user's Compass summary, which describes their activity in these same Feature names, when it writes follow-up questions. Features also unlock a set of targeting filters and user properties you get without any setup.

Chameleon builds your Feature list by researching your product (your website, docs, and pricing page), and your Features go to work straight away. Everything downstream repeats these names back to you, and these show up in session summaries and Copilot's suggestions as written. You can edit these on the Features page if something isn't quite right.

🔓 Available on all plans

🧑‍💼 Admin and Engineer roles can edit and add Features

📍 Covers your whole product

⚙️ Features in the left navigation

Every Feature lives in one table, sorted alphabetically, with two columns: Name and Description. Hover a row and two actions appear on the right:

Click the row itself to open the Feature in detail.

If you want to delete a Feature, you'll see a confirmation that Chameleon will stop tracking data for that Feature, and it will no longer appear in menus. Deleting also untags the sessions and Experiences attached to it. If the Feature has sub-Features, they continue to be tracked on their own; deleting a parent doesn't delete its sub-Features.

There's nothing to confirm. Every Feature Chameleon detects counts from the moment it appears. The list is never a backlog you've fallen behind on, but a description of your product that you correct when it's wrong.

Add New covers what detection can't see: a Feature behind a flag, something only some users can reach, or a capability that isn't visually obvious. Add a name and a description, and optionally a URL.

Everything Chameleon has gathered about a Feature sits behind the row; click it to open the detail view:

From here, you can also Edit Feature, Add Sub-Feature, Remove Feature, Find linked Experiences, and, on the Research tab, Summarize Research.

You can go from "this is one of our Features" to "here's who uses it, who's struggling with it, and what we've shipped for it" without leaving the page.

A large Feature can hold smaller ones underneath it, Dashboards with Filters, Sharing, and Exports, for example. Sub-features let you keep targeting and friction attribution at the level your team actually works at, rather than lumping everything into one name.

To add one, choose Add New, switch the toggle from Feature to Sub-Feature, and pick its parent. Where a Feature already has sub-Features, its detail view offers View Sub-Features.

Feature names show up across the Dashboard, and if you notice one is wrong, you can adjust it straight away. Wherever a Feature is referenced, there's a Review features link straight back to this page:

With Compass Sessions Summaries on, every Feature is available in segmentation. Add a Product Features filter, choose is or is not, pick the Feature, and pick a usage pattern. Compass looks at each user's visits from the last 30 days and updates these labels once a week.

👉 Lapsed User and Experienced friction are the two most people reach for first: one finds users you're losing on a Feature, the other finds users who want it and can't get it to work.

Combine a Feature filter with any other Segment condition to get specific: power users of your reporting Feature, on a Startup plan.

With Compass Sessions Summaries on, every user is automatically assigned three properties based on their session activity. There's nothing else to set up.

These update on their own: someone who was Established and stops logging in moves to At Risk within a few weeks, then to Dormant after six months without a visit, with nothing from you.

In segmentation, these appear with the names above. In API and webhook payloads, they're prefixed: chameleon_session_frequency, chameleon_feature_engagement_level and chameleon_lifecycle_stage.