> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/marketing/chameleon/faq.md).

# FAQ

<details>

<summary>Where do I find my Chameleon API key?</summary>

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.

</details>

<details>

<summary>Can I pull data from multiple Chameleon workspaces?</summary>

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.

</details>

<details>

<summary>What's the difference between Surveys and Survey responses?</summary>

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.

</details>

<details>

<summary>Why does the filter parameter only have three options?</summary>

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.

</details>

<details>

<summary>Can I use Chameleon data with AI tools?</summary>

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.

</details>

<details>

<summary>How do I get more than 50 records per sync?</summary>

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.

</details>

<details>

<summary>Can I track changes to a specific tour or tooltip over time?</summary>

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`.

</details>

{% hint style="info" %}
For a full breakdown of available fields per entity, see [Data Overview](/sources/category/marketing/chameleon/data-overview.md). If you're running into sync errors or missing records, check [Common Issues](/sources/category/marketing/chameleon/common-issues.md). For tips on structuring your data flows, visit [Best Practices](/sources/category/marketing/chameleon/best-practices.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/marketing/chameleon/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.