> 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/zoho-campaign.md).

# Zoho Campaign

Connect Zoho Campaigns to Coupler.io to centralize email performance data, subscriber lists, and campaign reports for analysis across your business.

Zoho Campaigns is an email marketing platform that lets you create, send, and track email campaigns to segmented contact lists. It's part of the Zoho ecosystem and works well for teams already using Zoho CRM or other Zoho apps. Connecting it to Coupler.io lets you pull your campaign data into any destination for reporting and analysis.

## Why connect Zoho Campaigns to Coupler.io?

* **Centralize your email performance data** — combine campaign reports, subscriber lists, and delivery stats in one place
* **Build automated dashboards** — send data to Google Sheets, Looker Studio, or BigQuery without manual exports
* **Use AI for campaign analysis** — pipe your campaign data into ChatGPT, Claude, or Gemini to summarize trends or generate insights
* **Combine with other sources** — use Append or Join transformations to merge Zoho Campaigns data with CRM, ad, or web analytics data

## Prerequisites

* An active Zoho Campaigns account
* A Zoho Campaigns API key (available in your account settings)
* At least one mailing list or sent campaign in your account

## Quick start

{% hint style="success" %}
Start with the **Campaign reports** entity — it gives you the most actionable performance data (opens, clicks, bounces) right away.
{% 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**. Search for and select **Zoho Campaigns** as your source.
{% endstep %}

{% step %}
**Enter your Zoho Campaigns API key.** In your Zoho Campaigns account, go to **Settings → Developer Space → API Keys** and copy your API key. Paste it into the API key field in Coupler.io.
{% endstep %}

{% step %}
**Select an entity.** Choose which data you want to pull — for example, **Campaign reports**, **Subscribers**, or **Mailing lists**. You can add more sources to the same data flow to pull multiple entities at once.
{% endstep %}

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

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

## Zoho Campaigns data overview

Zoho Campaigns exposes a range of entities covering your contacts, mailing infrastructure, and campaign performance. Here's a breakdown of what each entity contains and how you can use it.

## Available entities

| Entity                | Best used for                                      |
| --------------------- | -------------------------------------------------- |
| Campaign reports      | Tracking opens, clicks, bounces per campaign       |
| Recent campaigns      | Getting a snapshot of newly created campaigns      |
| Recent sent campaigns | Monitoring delivery status of recently sent emails |
| Campaign details      | Deep-diving into individual campaign configuration |
| Campaign recipients   | Auditing who received a specific campaign          |
| Subscribers           | Analyzing your contact base and profile data       |
| Mailing lists         | Understanding list structure and segmentation      |
| Total contacts        | High-level contact count reporting                 |
| Topics                | Categorizing campaigns by subject matter           |
| All tags              | Reviewing your tagging taxonomy                    |

## Campaign performance metrics

#### Campaign reports

| Field           | Description                            |
| --------------- | -------------------------------------- |
| Campaign name   | Name of the email campaign             |
| Sent count      | Total number of emails sent            |
| Delivered count | Emails successfully delivered          |
| Opens           | Total number of email opens            |
| Unique opens    | Distinct recipients who opened         |
| Clicks          | Total link clicks                      |
| Unique clicks   | Distinct recipients who clicked        |
| Bounces         | Total bounced emails                   |
| Hard bounces    | Permanent delivery failures            |
| Soft bounces    | Temporary delivery failures            |
| Unsubscribes    | Recipients who opted out               |
| Spam complaints | Emails marked as spam                  |
| Open rate       | Percentage of delivered emails opened  |
| Click rate      | Percentage of delivered emails clicked |

#### Campaign details

| Field          | Description                                   |
| -------------- | --------------------------------------------- |
| Campaign ID    | Unique identifier for the campaign            |
| Campaign name  | Display name                                  |
| Subject line   | Email subject                                 |
| From name      | Sender name                                   |
| From email     | Sender email address                          |
| Status         | Draft, scheduled, or sent                     |
| Created time   | When the campaign was created                 |
| Scheduled time | When the campaign was or is scheduled to send |

## Contact and list data

#### Subscribers

| Field         | Description                             |
| ------------- | --------------------------------------- |
| Email address | Subscriber's email                      |
| First name    | Subscriber's first name                 |
| Last name     | Subscriber's last name                  |
| Signup date   | When they subscribed                    |
| Status        | Active, unsubscribed, bounced           |
| Source        | How they were added (import, form, API) |

#### Mailing lists

| Field            | Description                           |
| ---------------- | ------------------------------------- |
| List name        | Name of the mailing list              |
| List ID          | Unique identifier                     |
| Subscriber count | Number of active contacts in the list |
| Created date     | When the list was created             |

#### Campaign recipients

| Field         | Description              |
| ------------- | ------------------------ |
| Email address | Recipient's email        |
| Campaign name | Campaign they received   |
| Delivery time | Timestamp of delivery    |
| Status        | Delivered, bounced, etc. |

## Common metric combinations

* **Campaign reports + Campaign details** — Join on Campaign ID to get performance metrics alongside subject lines and sender info in one table
* **Subscribers + Mailing lists** — Understand which lists your contacts belong to and how lists are growing over time
* **Campaign recipients + Campaign reports** — Correlate individual delivery records with overall campaign-level stats
* **Recent sent campaigns + Campaign reports** — Use Append to build a rolling history of sent campaigns with their performance data

## Use cases by role

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

* Track open rates and click rates across campaigns to identify your best-performing subject lines
* Monitor unsubscribe and bounce rates to maintain list health
* Use Aggregate transformation to roll up metrics by topic or tag, giving you category-level performance views
* Export to Looker Studio or Google Sheets for shareable campaign performance dashboards
  {% endtab %}

{% tab title="Marketing ops" %}

* Join campaign reports with CRM data to connect email engagement to pipeline outcomes
* Use Append to combine data from multiple Zoho Campaigns accounts into a single destination
* Feed subscriber and campaign data into BigQuery for SQL-based analysis and historical trend tracking
* Pipe campaign data into Claude or ChatGPT to auto-generate performance summaries for stakeholders
  {% endtab %}

{% tab title="Growth teams" %}

* Analyze list growth over time using Subscribers and Total contacts data
* Identify engaged segments by filtering subscribers with high open or click history
* Use topics and tags to segment campaign performance by content category or audience type
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Zoho Campaigns API keys are scoped to the account — make sure the key belongs to a user with access to all lists and campaigns you need
* The **Recent campaigns** and **Recent sent campaigns** entities return a limited window of campaigns — use **Campaign details** if you need data on older campaigns by ID
* Contact status values (active, unsubscribed, bounced) reflect the state at the time of sync, not historical state changes
* Tags and topics are organization-level metadata — useful for filtering in your destination but not tied to performance metrics directly

## Zoho Campaigns common issues

### Connection issues

<details>

<summary>Invalid API key error when connecting</summary>

Double-check that you copied the full API key from Zoho Campaigns without any trailing spaces. In Zoho Campaigns, go to **Settings → Developer Space → API Keys** and regenerate the key if needed. Paste it fresh into Coupler.io.

</details>

<details>

<summary>Authentication succeeds but no data loads</summary>

This usually means the API key belongs to a user who doesn't have access to any campaigns or lists. Make sure the user whose key you're using has at least read access to the entities you're trying to pull.

</details>

### Missing data

<details>

<summary>Recent campaigns entity returns fewer campaigns than expected</summary>

The **Recent campaigns** and **Recent sent campaigns** entities only return a recent subset of your campaigns. If you need data on older campaigns, use **Campaign details** and specify the campaign ID, or pull **Campaign reports** which may have broader coverage.

</details>

<details>

<summary>Campaign reports entity shows no data for a campaign</summary>

Reports are only available for campaigns that have been sent. Draft or scheduled campaigns won't appear in campaign reports. Check the campaign's status using the **Recent sent campaigns** entity first.

</details>

<details>

<summary>Subscriber data is incomplete or missing fields</summary>

Custom contact fields in Zoho Campaigns may not always surface in the API response if they have no value. Fields that are blank for a contact may be omitted from the row entirely. Expect some columns to have gaps depending on how thoroughly your contacts are profiled.

</details>

### Permission errors

<details>

<summary>"Access denied" error when pulling specific entities</summary>

Some entities — particularly campaign recipients and subscriber details — may require elevated API permissions. Check that your Zoho Campaigns plan supports API access for those endpoints, and that the API key owner has admin or manager-level access.

{% hint style="warning" %}
Zoho Campaigns API access may be restricted on lower-tier plans. Verify your plan's API limits in your Zoho account settings.
{% endhint %}

</details>

### Data discrepancies

<details>

<summary>Open rates in Coupler.io don't match the Zoho Campaigns dashboard</summary>

Zoho Campaigns may calculate rates using slightly different denominators (e.g., delivered vs. sent) in their UI compared to the raw API fields. Use the raw counts (opens, delivered count) to recalculate rates in your destination for consistency.

</details>

<details>

<summary>Subscriber count in Total contacts differs from Mailing lists data</summary>

Total contacts reflects the global count across your entire account, including contacts that may belong to multiple lists. The count per mailing list reflects only that list's active subscribers — overlap between lists is expected and normal.

</details>

### Rate limits

<details>

<summary>Data flow fails or times out with a rate limit error</summary>

Zoho Campaigns enforces API rate limits per account. If you have a large number of subscribers or campaigns, pulling multiple entities in a single data flow can hit these limits. Try splitting entities across separate data flows and running them at different times.

</details>

## Zoho Campaigns FAQ

<details>

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

Log in to Zoho Campaigns and go to **Settings → Developer Space → API Keys**. If you don't see this option, your plan may not include API access — check your plan details or contact Zoho support.

</details>

<details>

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

Yes. Add each account as a separate source within the same data flow using its own API key, then use the **Append** transformation to combine the data before sending it to your destination.

</details>

<details>

<summary>What's the difference between Recent campaigns and Recent sent campaigns?</summary>

**Recent campaigns** includes all recently created campaigns regardless of their status — drafts, scheduled, and sent. **Recent sent campaigns** filters to only campaigns that have already been delivered to recipients. Use Recent sent campaigns when you only care about live performance data.

</details>

<details>

<summary>Can I get historical campaign data, not just recent campaigns?</summary>

The recent campaign entities return a limited window. For broader historical access, use the **Campaign details** and **Campaign reports** entities — these may give you access to older campaigns depending on your Zoho plan and API response limits.

</details>

<details>

<summary>Why do my open rates look higher than I'd expect?</summary>

Apple Mail Privacy Protection pre-fetches emails and triggers open tracking pixels even when a subscriber hasn't actually opened the email. This inflates open counts. Use click data as a more reliable engagement signal.

</details>

<details>

<summary>Can I combine Zoho Campaigns data with Zoho CRM data in Coupler.io?</summary>

Yes. Add both Zoho Campaigns and Zoho CRM as sources in the same data flow and use the **Join** transformation to link records — for example, joining subscribers by email address with CRM contacts to connect email engagement with sales pipeline data.

</details>

<details>

<summary>Which entities are best for building an email performance dashboard?</summary>

Start with **Campaign reports** for metrics and **Campaign details** for context, then join them on Campaign ID. Add **Mailing lists** if you want to slice performance by audience segment. Send the combined data to Looker Studio or Google Sheets for visualization.

</details>

<details>

<summary>Can I use Zoho Campaigns data with AI tools through Coupler.io?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route your campaign reports or subscriber data directly to these tools for automated analysis, summaries, or recommendations.

</details>

{% hint style="info" %}
For a full list of available fields and metrics, see the [Data Overview](#zoho-campaigns-data-overview) article. For connection errors or missing data, check the [Common Issues](#zoho-campaigns-common-issues) article.
{% 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/zoho-campaign.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.
