> 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/email/convertkit/faq.md).

# FAQ

<details>

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

Log in to Kit and go to **Settings → Advanced → API**. You'll see both a public API key and an API Secret. Use the **API Secret** when setting up your Coupler.io data flow — it's the longer string and provides the access level needed for data exports.

</details>

<details>

<summary>Can I sync data from multiple Kit accounts?</summary>

Yes. Create a separate data flow for each Kit account using that account's API key. If you want to combine subscriber data from both accounts into one destination, add them as multiple sources in the same data flow and use the **Append** transformation to stack the records.

</details>

<details>

<summary>What does the start date parameter actually control?</summary>

The start date tells Coupler.io where to begin fetching records. For example, if you set it to six months ago, only subscribers, purchases, and broadcasts created or updated from that point forward will be included. Use the date picker to set this — it's especially useful for large accounts where pulling all historical data would be slow.

</details>

<details>

<summary>Can I get broadcast open rates and click rates from Kit?</summary>

Not through Coupler.io — Kit's API doesn't expose per-broadcast engagement metrics like open rates or click-through rates. You can pull broadcast metadata (subject line, send date, content), but performance data is only available inside the Kit dashboard itself.

</details>

<details>

<summary>Why do the Form subscribers, Sequence subscribers, and Tag subscribers entities look different from Subscribers?</summary>

These association entities return relationship records — essentially a list of subscriber IDs linked to a form, sequence, or tag. They don't include full subscriber profiles. To enrich them with names and email addresses, add the **Subscribers** entity as a second source and use a **Join** transformation on the subscriber ID field.

</details>

<details>

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

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route your subscriber or broadcast data directly to these tools — useful for tasks like summarizing audience trends, drafting reports, or generating segmentation recommendations.

</details>

<details>

<summary>Is there a way to track subscriber revenue in Coupler.io?</summary>

Yes — export the **Purchases** entity and join it with **Subscribers** using the `subscriber_id` field. This gives you a combined view of purchase amounts, product names, and subscriber details. From there you can use Coupler.io's **Aggregate** transformation to calculate total revenue per subscriber or per product.

</details>

{% hint style="info" %}
For a full breakdown of fields available in each entity, see the [Data Overview](/sources/category/email/convertkit/data-overview.md) article. If your sync isn't returning the data you expect, check the [Common Issues](/sources/category/email/convertkit/common-issues.md) article for troubleshooting steps.
{% 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/email/convertkit/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.