> 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/sales/churnkey/faq.md).

# FAQ

<details>

<summary>What's the difference between Sessions and Session aggregations?</summary>

Sessions gives you one row per individual churn prevention interaction — every time a customer went through your cancel flow. Session aggregations are pre-computed summaries that roll up counts, save rates, and revenue figures across those sessions. Use Sessions for detailed analysis or customer-level investigation; use Session aggregations for dashboards and trend reporting.

</details>

<details>

<summary>Can I pull data from multiple Churnkey accounts into one destination?</summary>

Yes. Add each Churnkey account as a separate source in your data flow using its own API key, then use Coupler.io's Append transformation to combine the data into a single table. This is useful if you manage separate Churnkey workspaces for different products or brands.

</details>

<details>

<summary>How far back does Churnkey's API return data?</summary>

Churnkey's API returns historical session data from when your account was created. There's no hard cutoff documented for the API, but very large historical pulls may be slower. If you're doing a first-time sync of a long-running account, expect the initial run to take longer than subsequent refreshes.

</details>

<details>

<summary>Can I use Churnkey data with AI tools through Coupler.io?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route Churnkey session data — especially cancel reasons and outcomes — directly to these tools for automated analysis, summaries, or retention strategy recommendations.

</details>

<details>

<summary>Why do my session counts in Coupler.io differ from the Churnkey dashboard?</summary>

The Churnkey dashboard often applies default date filters and may exclude incomplete or test sessions. The API used by Coupler.io may return a broader dataset. Check what filters are active in your Churnkey dashboard and compare against the raw session data to identify the difference. See the [Common Issues](/sources/category/sales/churnkey/common-issues.md) page for more detail.

</details>

<details>

<summary>Is Churnkey data available in real time?</summary>

Coupler.io syncs on demand or on a schedule — it's not a streaming connection. For most retention reporting use cases, a daily or hourly scheduled refresh is more than sufficient. You can always trigger a manual run if you need the latest data immediately.

</details>

<details>

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

Log in to Churnkey and navigate to your account or developer settings. The API key is usually listed there under an "API" or "Integrations" section. Copy the full key and paste it into the source settings when setting up your Coupler.io data flow.

</details>

{% hint style="info" %}
For a full list of available fields and metric definitions, see the [Data Overview](/sources/category/sales/churnkey/data-overview.md) page. For connection errors or missing data, visit [Common Issues](/sources/category/sales/churnkey/common-issues.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/sales/churnkey/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.