> 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/data-overview.md).

# Data Overview

Kit exposes a broad set of entities through its API, covering your audience, campaigns, automations, and commerce data. Here's what each entity contains and how you can use it.

## Entities summary

| Entity               | What it contains                                            |
| -------------------- | ----------------------------------------------------------- |
| Subscribers          | Subscriber profiles, status, tags, and signup dates         |
| Broadcasts           | Campaign metadata, send dates, and subject lines            |
| Sequences            | Sequence names, IDs, and creation dates                     |
| Forms                | Form names, types, embed codes, and creation dates          |
| Tags                 | Tag names and IDs                                           |
| Form subscribers     | Subscriber-to-form associations                             |
| Sequence subscribers | Subscriber-to-sequence associations                         |
| Tag subscribers      | Subscriber-to-tag associations                              |
| Purchases            | Transaction IDs, product names, amounts, and subscriber IDs |
| Segments             | Segment names, IDs, and creation dates                      |
| Custom fields        | Field keys, labels, and creation dates                      |
| Email templates      | Template names, IDs, and creation dates                     |
| Current account      | Account name, plan, and primary email                       |

## Subscribers

#### Subscriber fields

| Field          | Description                                  |
| -------------- | -------------------------------------------- |
| id             | Unique subscriber ID                         |
| first\_name    | Subscriber's first name                      |
| email\_address | Email address                                |
| state          | Subscription status (active, inactive, etc.) |
| created\_at    | Date the subscriber was added                |
| fields         | Custom field values for this subscriber      |
| tags           | Tags assigned to the subscriber              |

## Broadcasts

#### Broadcast fields

| Field         | Description                                  |
| ------------- | -------------------------------------------- |
| id            | Unique broadcast ID                          |
| created\_at   | Date the broadcast was created               |
| subject       | Email subject line                           |
| description   | Internal description or label                |
| content       | Email body content                           |
| public        | Whether the broadcast is publicly accessible |
| published\_at | Date the broadcast was sent                  |

## Purchases

#### Purchase fields

| Field           | Description                            |
| --------------- | -------------------------------------- |
| id              | Unique purchase ID                     |
| subscriber\_id  | ID of the purchasing subscriber        |
| product\_id     | ID of the purchased product            |
| product\_name   | Name of the product                    |
| purchase\_total | Total transaction amount               |
| currency        | Transaction currency                   |
| status          | Purchase status (paid, refunded, etc.) |
| created\_at     | Date of the transaction                |

## Forms

#### Form fields

| Field       | Description                           |
| ----------- | ------------------------------------- |
| id          | Unique form ID                        |
| name        | Form name                             |
| type        | Form type (embed, landing page, etc.) |
| format      | Visual format of the form             |
| embed\_js   | JavaScript embed code                 |
| created\_at | Date the form was created             |

## Tags and segments

#### Tag fields

| Field       | Description              |
| ----------- | ------------------------ |
| id          | Unique tag ID            |
| name        | Tag name                 |
| created\_at | Date the tag was created |

#### Segment fields

| Field       | Description                  |
| ----------- | ---------------------------- |
| id          | Unique segment ID            |
| name        | Segment name                 |
| created\_at | Date the segment was created |

## Common data combinations

* **Subscribers + Tag subscribers** — Join these to see which tags each subscriber holds, useful for segmentation audits
* **Subscribers + Purchases** — Join on subscriber ID to build a revenue-per-subscriber view
* **Form subscribers + Forms** — Join to analyze which forms drive the most signups
* **Broadcasts + Subscribers** — Combine to track campaign reach over time

## Use cases by role

{% tabs %}
{% tab title="Content creators" %}

* Track subscriber growth over time by exporting the Subscribers entity regularly
* Monitor which opt-in forms convert best by combining Forms and Form subscribers
* Review broadcast history to see which subject lines you've used and when campaigns went out
  {% endtab %}

{% tab title="Finance teams" %}

* Export Purchases data to Google Sheets or BigQuery to track product revenue and refund rates
* Join Purchases with Subscribers to identify your highest-value audience segments
* Use Aggregate transformations to sum purchase totals by product or time period
  {% endtab %}

{% tab title="Marketing analysts" %}

* Combine Tag subscribers with Subscribers to analyze segment sizes and overlap
* Export Sequences data to map out automation coverage across your audience
* Feed subscriber and broadcast data into AI tools like ChatGPT or Claude for audience insights
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* The **start\_date** parameter controls how far back Coupler.io fetches data — use the date picker to avoid pulling years of historical records unnecessarily
* The **Form subscribers**, **Sequence subscribers**, and **Tag subscribers** entities return association records, not full subscriber profiles — join them with the **Subscribers** entity for enriched data
* **Custom fields** returns field definitions (keys and labels), not the values — subscriber-level custom field values appear inside the **Subscribers** entity under the `fields` object
* Kit's API does not return per-broadcast engagement metrics (opens, clicks) — those must be viewed inside the Kit dashboard


---

# 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/data-overview.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.