> 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.md).

# Churnkey

Churnkey is a churn prevention platform that helps subscription businesses retain customers through personalized cancel flows, pause offers, and win-back campaigns. It tracks every customer interaction during the cancellation journey so you can understand why people leave — and what keeps them.

Connecting Churnkey to Coupler.io lets you move that retention data into the tools where you actually do analysis.

**Why connect Churnkey to Coupler.io?**

* Pull raw session data and aggregated metrics into Google Sheets, Excel, BigQuery, or Looker Studio without writing any code
* Send churn signals to AI tools like ChatGPT, Claude, or Gemini for automated retention analysis and recommendations
* Combine Churnkey data with CRM or billing sources using Join or Append transformations for a fuller picture of customer health
* Schedule automatic refreshes so your dashboards and reports always reflect the latest retention activity

**Prerequisites**

* A Churnkey account with at least one active cancel flow
* Your Churnkey API key (found in your Churnkey account settings under API/Developer options)

## Quick start

{% hint style="success" %}
Start with the **Session aggregations** entity if you want a high-level view of retention performance. Switch to **Sessions** when you need row-level detail on individual customer interactions.
{% endhint %}

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io, click **Add data flow**, and select **Churnkey** as your source.
{% endstep %}

{% step %}
**Enter your Churnkey API key.** In the source settings, paste your API key into the designated field. You can find this key in Churnkey under your account or developer settings.
{% endstep %}

{% step %}
**Select an entity.** Choose either **Sessions** for individual interaction records or **Session aggregations** for summarized metrics. You can add more entities to the same data flow later.
{% endstep %}

{% step %}
**Choose a destination.** Pick where you want your data to land — Google Sheets, BigQuery, Excel, Looker Studio, or an AI destination like ChatGPT or Claude.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual sync. Once it completes successfully, your Churnkey data will appear in your chosen destination.
{% endstep %}
{% endstepper %}

## Available entities

| Entity               | Description                                                                                            |
| -------------------- | ------------------------------------------------------------------------------------------------------ |
| Sessions             | Individual churn prevention session records including engagement data, timing, and interaction details |
| Session aggregations | Summarized metrics rolled up across multiple sessions for trend and performance analysis               |


---

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