FAQ

Where do I find my Chameleon API key?

Go to your Chameleon dashboard and navigate to Settings → Integrations → API. Copy the Account Secret — that's the key you'll paste into Coupler.io. Don't use the public key; it won't authenticate correctly.

Can I pull data from multiple Chameleon workspaces?

Yes. Create a separate source connection for each workspace using its own API key, then use Coupler.io's Append transformation to combine the data into a single destination. This is useful if you manage Chameleon across multiple products or environments.

What's the difference between Surveys and Survey responses?

The Surveys entity contains the structure and metadata of each survey — its name, questions, and configuration. Survey responses contains the individual answers submitted by users. You'll usually want to join them on survey_id to get a complete picture.

Why does the filter parameter only have three options?

The filter parameter applies specifically to the segment-experience relationship query. Chameleon organizes experiences into three types — tour, survey, and launcher — and the filter scopes which type you're querying. For other entities like Helpbars or Tooltips, the filter doesn't apply.

Can I use Chameleon data with AI tools?

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. Survey responses are particularly well-suited for AI analysis — you can send open-ended answers directly to an AI destination to summarize themes or classify sentiment automatically.

How do I get more than 50 records per sync?

The default record limit is 50 per page. Increase this using the Record limit parameter in the source settings. There's no hard maximum documented, but start with 200–500 and test for rate limit errors before going higher.

Can I track changes to a specific tour or tooltip over time?

Yes — use the Changes entity and filter by experience_id in your destination tool. This gives you a timestamped log of every edit. For full context, join the Changes data with your Tours or Tooltips entity on experience_id.

For a full breakdown of available fields per entity, see Data Overview. If you're running into sync errors or missing records, check Common Issues. For tips on structuring your data flows, visit Best Practices.