> 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/common-issues.md).
# Common Issues
## Connection issues
My API key is not being accepted
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.
The data flow fails immediately after I run it
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.
## Missing data
Some contacts are not showing up in the Contacts entity
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.
My Reports entity returns no data
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.
Forms data appears empty
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.
## Permission errors
I get a "permission denied" or "unauthorized" error
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.
## Data discrepancies
The open and click counts in Coupler.io don't match what I see in Campayn's dashboard
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.
Subscriber counts in Lists don't match the Contacts entity
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.
## Rate limits
My data flow is slow or times out on large contact lists
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.
---
# 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/common-issues.md?ask=&goal=
```
`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.