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

# Data Overview

Coupler.io pulls five types of data from Campayn, covering your audience structure, campaign content, and engagement performance. Here's a breakdown of what each entity contains and how to use it.

## Available entities

| Entity   | Best used for                                                         |
| -------- | --------------------------------------------------------------------- |
| Lists    | Auditing list sizes, growth, and segmentation structure               |
| Forms    | Tracking which sign-up forms are active and collecting subscribers    |
| Contacts | Building a full contact database with subscription status and details |
| Emails   | Reviewing all campaigns sent, including subject lines and send dates  |
| Reports  | Analyzing opens, clicks, bounces, and unsubscribes per campaign       |

## Lists

#### Key fields

| Field            | Description                              |
| ---------------- | ---------------------------------------- |
| List ID          | Unique identifier for the list           |
| List name        | The display name of the subscriber list  |
| Subscriber count | Number of active subscribers in the list |
| Created date     | When the list was created                |
| Status           | Whether the list is active or archived   |

## Forms

#### Key fields

| Field           | Description                                     |
| --------------- | ----------------------------------------------- |
| Form ID         | Unique identifier for the form                  |
| Form name       | Display name of the sign-up form                |
| Associated list | The list subscribers are added to on submission |
| Status          | Whether the form is active or inactive          |
| Created date    | When the form was created                       |

## Contacts

#### Key fields

| Field                  | Description                        |
| ---------------------- | ---------------------------------- |
| Contact ID             | Unique identifier for the contact  |
| Email address          | The subscriber's email address     |
| First name / Last name | Subscriber name fields             |
| Subscription status    | Active, unsubscribed, or bounced   |
| List memberships       | Which lists the contact belongs to |
| Created date           | When the contact was added         |

## Emails

#### Key fields

| Field                  | Description                        |
| ---------------------- | ---------------------------------- |
| Email ID               | Unique identifier for the campaign |
| Subject line           | The subject of the sent email      |
| From name / From email | Sender details                     |
| Send date              | When the campaign was sent         |
| Status                 | Draft, scheduled, or sent          |

## Reports

#### Key fields

| Field         | Description                                    |
| ------------- | ---------------------------------------------- |
| Campaign ID   | Links report data back to a specific email     |
| Recipients    | Total number of contacts the email was sent to |
| Opens         | Number of times the email was opened           |
| Unique opens  | Distinct subscribers who opened the email      |
| Clicks        | Total link clicks within the email             |
| Unique clicks | Distinct subscribers who clicked a link        |
| Bounces       | Emails that failed to deliver                  |
| Unsubscribes  | Contacts who opted out after this campaign     |
| Open rate     | Percentage of recipients who opened            |
| Click rate    | Percentage of recipients who clicked           |

## Common metric combinations

* **Reports + Emails** (Join on campaign ID) — Attach subject lines and send dates to your performance metrics for readable reporting
* **Contacts + Lists** (Join on list membership) — See which lists each contact belongs to alongside their personal details
* **Reports across multiple campaigns** (Append) — Stack data from several campaigns to compare performance over time
* **Contacts aggregated by status** (Aggregate) — Count active, unsubscribed, and bounced contacts to monitor list health

## Use cases by role

{% tabs %}
{% tab title="Email marketers" %}

* Monitor open rates and click rates per campaign to identify what content resonates
* Track unsubscribe spikes after specific sends to catch messaging issues early
* Join Reports with Emails to create a campaign performance log with subject lines and send dates in one table
  {% endtab %}

{% tab title="Marketing ops" %}

* Audit all active subscriber lists and form connections to keep list hygiene in check
* Aggregate contact subscription statuses to measure overall list health across segments
* Schedule automated data flows into BigQuery or Google Sheets for recurring stakeholder reports
  {% endtab %}

{% tab title="Growth teams" %}

* Track which sign-up forms are driving the most new contacts by joining Forms and Contacts data
* Monitor subscriber list growth over time by pulling Lists data on a regular schedule
* Feed Reports data into ChatGPT or Claude to get AI-generated summaries of campaign performance trends
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Campayn's API uses an API key for authentication — there is no OAuth flow. Keep your API key secure and rotate it if it's ever exposed.
* Report data is campaign-level, not individual recipient-level, so you won't see per-contact open or click records in the Reports entity.
* Contact data includes list memberships, which you can use to filter or segment in your destination after import.


---

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