Why does Chameleon need both the right page and the right person?

Install the browser script where guidance should appear and pass a stable user ID. Set which environments and audiences can receive the experience. A different or newly added domain may need to be enabled in Chameleon.

For example, show a hint on a new reports screen only to people who can run a report. Keep permissions in the app and verify that the guide can find the button after a layout change.

Can someone count without opening your app?

Yes. Chameleon counts distinct identified user IDs from the prior 30 days. Profiles sent through integrations, imports or its API can count even if those people never saw the guide. Its billing guide says the maximum tracked-user count in the billing period is used.

The public pricing page lists Startup at 2,000 tracked users and up to 10 live experiences. Pro starts at 5,000 tracked users and up to 20 live experiences. Confirm the price and terms for your volume before connecting a large customer list.

What should you check before showing a translated tour?

Chameleon can use a supplied language field, with browser language as a fallback if the field is missing. The current pricing table lists language allowances for Pro, Growth and Enterprise. The translation help page still says Enterprise, so confirm the allowance for your plan before committing.

Chameleon documents focus moving into a displayed experience and returning to the page when it closes. Escape behavior depends on the experience. Check where focus actually goes and whether someone can still use the app control.

How would you rehearse a report hint without opening an integration?

Draw a reports page, an account that can generate a report and one that cannot. Keep the plan on paper. Leave the browser script, any data import and all production settings alone.

Choose the page and audience
Point to the Run report button only for someone who can use it. Draw where the user lands when dismissing a tooltip.
Estimate tracked people
Count made-up IDs sent by the app and by an import. Count the same ID once for the example. Mark which people never saw a tour but still entered the estimate.
Make a handoff
Export experience activity when authorized and save the wording, page anchors and audience rules in your own files. Remove the browser and data connections separately when switching.