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

# Campayn

Pull Campayn contacts, lists, forms, and email reports into Google Sheets or BigQuery via Coupler.io for unified marketing analytics.

Campayn is an email marketing platform that helps you build subscriber lists, design campaigns, and track engagement. With Coupler.io, you can pull your Campayn data — contacts, lists, forms, emails, and reports — into your preferred destination for analysis and reporting.

## Why connect Campayn to Coupler.io?

* **Centralize your email data** by combining Campayn reports with data from other marketing tools in one place
* **Automate reporting** so your dashboards always reflect the latest campaign performance without manual exports
* **Analyze with AI** by sending your Campayn data to ChatGPT, Claude, Gemini, or other AI destinations for instant insights
* **Join and aggregate** your contacts, lists, and reports to get a fuller picture of audience engagement

## Prerequisites

* An active Campayn account
* Your Campayn API key (available in your Campayn account settings under the API section)
* A Coupler.io account (free plan available)

## Quick start

{% hint style="success" %}
Start with the **Reports** entity if your primary goal is campaign performance analysis — it contains the engagement metrics you'll use most.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io, go to the Data Flows section, and click **Add data flow**.
{% endstep %}

{% step %}
**Select Campayn as your source.** Search for "Campayn" in the source catalog and select it.
{% endstep %}

{% step %}
**Enter your API key.** Open your Campayn account, navigate to account settings, and copy your API key. Paste it into the API key field in Coupler.io.
{% endstep %}

{% step %}
**Choose an entity.** Select the data entity you want to import — Lists, Forms, Contacts, Emails, or Reports.
{% endstep %}

{% step %}
**Choose a destination.** Connect to Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, Cursor, Gemini, Perplexity, or OpenClaw.
{% endstep %}

{% step %}
**Run your data flow.** Click **Run** to execute a manual run and confirm your data loads correctly.
{% endstep %}
{% endstepper %}

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

## Campayn common issues

### Connection issues

<details>

<summary>My API key is not being accepted</summary>

Double-check that you copied the full API key from your Campayn account settings without any extra spaces. API keys are case-sensitive. If the key still fails, try regenerating it in Campayn and entering the new one in Coupler.io.

</details>

<details>

<summary>The data flow fails immediately after I run it</summary>

This usually means the API key is invalid or the Campayn account doesn't have API access enabled. Confirm your Campayn plan includes API access — some lower-tier plans may restrict it. Check Campayn's account settings to verify.

</details>

### Missing data

<details>

<summary>Some contacts are not showing up in the Contacts entity</summary>

Campayn's API may only return contacts with an active subscription status by default. Contacts who have bounced or unsubscribed might appear in a filtered or reduced state. Check the subscription status field in your results to confirm whether inactive contacts are included.

</details>

<details>

<summary>My Reports entity returns no data</summary>

Reports only contain data for campaigns that have been sent. If you have only draft or scheduled emails in your Campayn account, the Reports entity will return empty. Make sure at least one campaign has been sent and delivered before pulling Reports.

</details>

<details>

<summary>Forms data appears empty</summary>

If you haven't created any sign-up forms in Campayn, the Forms entity will return no rows. Verify that forms exist in your Campayn account before pulling this entity.

</details>

### Permission errors

<details>

<summary>I get a "permission denied" or "unauthorized" error</summary>

This typically means the API key belongs to a user role that doesn't have full account access. Make sure the API key is generated from an account owner or admin role in Campayn, not a restricted user.

</details>

### Data discrepancies

<details>

<summary>The open and click counts in Coupler.io don't match what I see in Campayn's dashboard</summary>

Campayn's dashboard may display real-time or updated metrics, while the API returns data as of the moment the data flow ran. Run the data flow again to get the latest figures. For live dashboards, set up a scheduled refresh to keep numbers current.

</details>

<details>

<summary>Subscriber counts in Lists don't match the Contacts entity</summary>

The Lists entity shows the count of active subscribers per list. The Contacts entity includes all contacts regardless of list membership or status. These counts are intentionally different — use the subscription status field in Contacts to filter for active subscribers if you need to reconcile the numbers.

</details>

### Rate limits

<details>

<summary>My data flow is slow or times out on large contact lists</summary>

Campayn's API has rate limits that slow down large requests. If you have tens of thousands of contacts, the data flow may take longer than expected. Try running the data flow during off-peak hours and avoid triggering multiple runs at the same time.

</details>

## Campayn FAQ

<details>

<summary>What authentication method does Campayn use?</summary>

Campayn uses API key authentication. You'll find your API key in your Campayn account settings. There is no OAuth flow — you paste the key directly into Coupler.io when setting up your data flow.

</details>

<details>

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

Yes. Add multiple Campayn sources to the same data flow and use the Append transformation to combine the data. This is useful if your organization manages separate Campayn accounts for different brands or regions.

</details>

<details>

<summary>Does Coupler.io pull individual recipient-level engagement data?</summary>

No. Campayn's API provides campaign-level report data, not per-recipient data. You'll see total opens, unique opens, clicks, bounces, and unsubscribes per campaign — but not which specific contact opened or clicked.

</details>

<details>

<summary>Which entity should I start with for campaign performance reporting?</summary>

Start with **Reports** for the engagement metrics, then add **Emails** as a second source in the same data flow and join them on campaign ID. This gives you subject lines and send dates alongside your open and click rates in one clean table.

</details>

<details>

<summary>Can I send Campayn data to an AI tool for analysis?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route your Reports or Contacts data directly to these tools to generate campaign summaries, spot trends, or draft insights.

</details>

<details>

<summary>Why does my Contacts entity have more rows than my Lists subscriber count?</summary>

The Contacts entity includes all contacts in your Campayn account regardless of their subscription status — active, unsubscribed, or bounced. The Lists entity shows only the count of active subscribers per list. Filter the Contacts entity by subscription status if you want to compare like-for-like.

</details>

<details>

<summary>How often should I refresh my Campayn data?</summary>

It depends on your send cadence. For weekly senders, a daily refresh is plenty. For daily senders, a refresh every few hours keeps your dashboards current. Keep in mind that engagement data (opens, clicks) continues to accumulate for 24–48 hours after a send, so don't judge a campaign too early.

</details>

<details>

<summary>What destinations can I send Campayn data to?</summary>

Coupler.io supports Google Sheets, Microsoft Excel, BigQuery, Looker Studio, and AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. Choose based on how you plan to use the data — dashboards, spreadsheets, data warehouses, or AI analysis.

</details>

{% hint style="info" %}
For a full breakdown of available fields per entity, see [Data Overview](#campayn-data-overview). If something isn't working as expected, check [Common Issues](#campayn-common-issues). For tips on getting the most out of your setup, visit [Best Practices](https://docs.coupler.io/sources/category/email/campayn/best-practices.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/email/campayn.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
