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

# 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](/sources/category/email/zoho-campaign/data-overview.md) article. For connection errors or missing data, check the [Common Issues](/sources/category/email/zoho-campaign/common-issues.md) 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 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/zoho-campaign/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.