Compass is Chameleon's AI agent for understanding your users. It learns what your product is made of, keeps a plain-English summary of every user, and, once session tracking is on, writes up each visit and shows you where people get stuck. It runs on the Chameleon snippet you already have installed, so there's no event tagging, SDK change, or engineering work to do first.
Compass sits alongside Chameleon's other AI agents: Copilot (Experience creation and analysis), Prism (1:1 personalization), and Ranger (account cleanup and optimization). Compass is what the other Agents read when they need to know your product and your users.
Availability & Usage
š Available on Startup, Pro, Growth, and Enterprise
š³ Summaries use AI credits
š§āš¼ Admins control what Compass spends in AI Controls
āļø Find it on the Features page, in user and company profiles, and in Insights
What does Compass do?
Compass works in two layers. The first runs on every Compass account from day one. The second needs Session tracking, which records what users click and where they go, so Compass can write up each visit.
What you get | What it is | What it needs |
Your Features list | A map of the features your product is made of, named the way your users would recognize them. Every Agent reads from it | Nothing. Free |
Profile summaries | A short, plain-English summary of each user: who they are, how often they visit, and what they've told you in surveys | On by default. 1 credit each time a summary is refreshed |
Session recaps | A written account of each visit: what the user was trying to do, which Features they used, and where they hesitated | Session tracking. 2 credits per visit |
Feature-based targeting | Segments built on how people use each Feature (Power User through Lapsed), plus three automatic properties: session frequency, engagement level and lifecycle stage | Session tracking. Free once visits are recapped |
Friction findings | Where users are getting stuck, ranked by how many people it affects | Session tracking, 100+ active users and a week of data. Free |
What can I use straight away?
Your Features list is ready as soon as Compass has researched your product. Open the Features page, check the names and descriptions, and edit anything that isn't quite right. Everything downstream (session recaps, friction, Copilot's suggestions) repeats these names back to you, so a few minutes here pays off everywhere else.
šRead more about Product Features.
Profile summaries start writing automatically. They appear on each user's profile.
Adaptive Microsurveys use them too: Prism reads a user's summary to choose a follow-up question that fits them.
What does session tracking add?
Session tracking is what lets Compass see what users actually do in your product. With it on, you also get:
Session recaps on each user's and company's profile, and in Sessions
Targeting by Feature usage: find Lapsed users of a Feature, or Power Users of another, in any Segment
Three properties on every user: Product Session frequency, Product Engagement level, and Product Lifecycle stage (Onboarding, Ramping, Established, At Risk, Dormant)
Friction findings in Friction
Richer profile summaries, because each summary also draws on the user's recent recaps
How do I turn on session tracking?
Admins can pause or resume session recaps at any time with the Sessions Summaries toggle in AI Controls, on Account ā Credits. Switching it off stops new recaps, and every recap already written stays available.
šSession recaps are the largest use of AI credits, because one is written for every user on every visit. Read What are AI credits? to estimate your usage before you switch it on.
š If you don't see session recaps yet, contact us or ask your CSM, and we'll switch Session tracking on for your account.
How does Compass work?
It learns your product. Compass researches your website, docs, and pricing page to build your Features list, and keeps it in your own product's language.
It summarizes your users. For each user, Compass reads the User Properties and Company Properties you already send Chameleon, how recently and how often they visit, and their recent survey answers. It writes a summary about a day after a user first appears, refreshes it every few days while they're new, then once a month.
With session tracking on, it reads each visit. Compass records clicks and navigation in the background, then writes a recap when the visit ends, tagged to the Features the user touched. Those recaps feed back into the user's profile summary, set the three automatic properties, and are scanned every day for friction across the last 14 days.
ā¹ Friction is reported only when it's clear enough to act on: at least 100 active users over the last 14 days, at least 7 days of data, and at least 5% of your active users hitting the same problem. Compass surfaces up to five findings a day, so the important ones aren't buried. Read how to review them in How can I see the friction users encounter in my product?
Where does Compass intelligence surface?
Where | What you'll find |
Features | Your Features list, and for each Feature, the users, sessions, Experiences, and friction linked to it |
User profile | The user's profile summary and, with session tracking, their session recaps |
Company profile | With session tracking, the company's sessions |
Insights ā Sessions | Every recapped visit, filterable by keyword, Segment, Feature, and date |
Insights ā Friction | Ranked friction findings, each with a Discuss button that opens Copilot, already briefed on it |
Segments | The Product Features filter and the three automatic properties, with session tracking |
Copilot | Everything above, in plain language |
Prism | Adaptive Microsurveys choose follow-up questions using each user's profile summary |
What can I ask Copilot?
Copilot reads your Features list on every account, so you can start asking about your product straight away:
"Which of our product Features don't have an Experience yet?"
"Draft a Tour that introduces [Feature] to new users."
"Which Features that matter for retention have no in-app guidance?"
"Summarize the Features Compass found in our product, and flag any that look wrong."
With Session tracking on, Copilot can also answer questions about what your users actually do:
"What did [user] do in their last session?"
"Which features has [company]'s team adopted, and which are they ignoring?"
"Where are users running into friction in our onboarding flow?"
"Find a feature our users aren't adopting, and draft an Experience to drive discovery of it."
"Build a Segment of users who are At Risk and used to be regular users of Reports."
š” Copilot chooses what to read from how you phrase the question. Questions about what users did, read recent Session recaps; questions about where users struggle, read the friction findings, which cover the last 14 days.
š Hit Discuss on a friction finding and ask Copilot to write it up as an issue for your engineers. If you've connected Linear and have permission to manage integrations, Copilot can file it in Linear for you. Copilot conversations never use credits.
What does Compass cost?
Compass uses AI credits only when it writes a summary:
Action | Credits |
Profile summary, each time it's refreshed | 1 |
Session recap, per visit | 2 |
Features list, friction findings, Copilot | Free |
š New accounts start with 10,000 free credits. If your balance reaches zero, Compass stops writing new summaries, everything already written stays, and it picks up again once your balance is above zero.
What data does Compass collect?
Compass never records what your users type. For text fields, it only notes that something was entered, and password fields are ignored entirely. With Session tracking on, it records what users click, including the visible label of the button, link, or menu option, and the pages they visit, with sensitive details such as tokens removed from web addresses.
Read the full list and how Compass handles personal data inĀ What data does Compass collect?
Data privacy and security
Chameleon doesn't train AI or machine learning models on your data or on your users' data. Compass runs within Chameleon's existing infrastructure, subprocessors, and DPA, under our GDPR, CCPA, and SOC 2 frameworks. Chameleon acts as the data processor, and your organization remains the data controller.
For certifications, the full subprocessor list and downloadable security docs, visit our Trust Center. For the details on storage, retention, and AI processing, read What data does Compass collect?
Subprocessors
Compass uses Chameleon's existing subprocessors, including OpenAI for AI processing. All are listed in our Trust Center and operate under our existing GDPR, CCPA, and SOC 2 compliance frameworks.
AI processing
Behavioral activity (clicks, navigation, and page URLs), user and company profile data are sent to AI models only to write summaries and recaps, and are never used to train AI models.
Data storage
All data is stored within Chameleon's own infrastructure. Profile and session summaries persist as part of your Chameleon account data
Data controller / processor relationship
Chameleon is the data processor; your organization is the data controller and decides what user attributes it sends to Chameleon.
Frequently asked questions
Does enabling Compass require any engineering work?
No. Compass runs on your existing Chameleon installation: no new code, no new Events and no SDK changes.
How long until I see insights after enabling?
Your Features list and first profile summaries usually appear within a few days. Session recaps appear as users visit once session tracking is on. Friction findings need at least 100 active users and 7 days of data, so allow a week or two, and smaller accounts may see none.
Will Compass change what my users see?
No. Compass only observes. It never shows your users anything on its own; Experiences are still yours (or Copilot's) to build.
Will Compass affect my users' experience or product performance?
No. Session tracking runs silently in the background.
Does Compass replace my existing analytics tool?
Not as a general-purpose analytics tool: you can't build charts or funnels with it. Compass is built to understand behavior in the context of adoption, in-app Experiences and friction, so you can act on it inside Chameleon.
Do I need to set up event tracking or custom properties for Compass to work?
No. Compass generates its own signal. Any User Properties you already pass (such as plan, role or lifecycle stage) make its summaries richer.
What if I have data residency or security requirements?
Compass operates within Chameleon's existing data infrastructure and DPA. Reach out to your CSM or email the security team before you turn on session tracking.
I'm not sure Compass will be useful for my use case. How should I evaluate it?
Start with your Features list: check it, fix anything that's off, and see how Compass describes your product. Then think of a question you wish you could answer about your users, like "why do people stall during onboarding?", and ask us about turning on session tracking to answer it.
Key takeaways
Compass maps your product's Features and summarizes every user, with nothing to set up
Session tracking adds visit recaps, Feature-based targeting, and friction findings
Only summaries use credits: 1 per profile summary refresh, 2 per session recap
Compass never records what your users type
Ask Copilot anything Compass knows; conversations are always free