# FAQ

<details>

<summary>Which ActiveCampaign entities can I export?</summary>

Coupler.io supports the following ActiveCampaign entities, one per data flow:

* **Campaigns** — email campaigns with engagement metrics (opens, clicks, bounces, unsubscribes, etc.)
* **Contacts** — CRM contact records with email, name, phone, bounce status, and activity dates
* **Lists** — subscriber/mailing lists with opt-in settings and sender details
* **Deals** — CRM sales pipeline deals with value, stage, owner, and win probability
* **Segments** — audience segments built from contact conditions
* **Forms** — lead capture and subscription forms

Each data flow exports one entity at a time.

</details>

<details>

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

1. Log in to your ActiveCampaign account.
2. Go to **Settings** (gear icon in the left navigation).
3. Click **Developer**.
4. Your API key and API access URL are displayed there.

Your **account username** is the subdomain of your ActiveCampaign URL. For example, if your account URL is `https://mycompany.activehosted.com`, your username is `mycompany`.

</details>

<details>

<summary>Can I filter the data I export from ActiveCampaign?</summary>

The ActiveCampaign source in Coupler.io does not currently include a date range or field-level filter in the source configuration. Each run exports all available records for the selected entity.

To narrow your data in reporting:

* Apply filters in your **destination** (e.g., Google Sheets filter views, Looker Studio filter controls, or BigQuery WHERE clauses)
* Use Coupler.io's **data filtration** feature in the Transform step to filter rows before they reach the destination

{% hint style="info" %}
See [Data Overview](https://docs.coupler.io/sources/category/crm/activecampaign/data-overview) for details on available fields per entity that can be used as filter criteria.
{% endhint %}

</details>

<details>

<summary>Why are my deal values showing very large numbers?</summary>

ActiveCampaign stores deal monetary values in the smallest currency unit — cents for USD. A $1,500 deal is stored as `150000`.

To display the correct value:

* In Google Sheets: add a formula column `=value_column/100`
* In Looker Studio: create a calculated field `value / 100`
* In Coupler.io: use the formula columns feature in the Transform step to add a computed column

{% hint style="info" %}
See [Best Practices](https://docs.coupler.io/sources/category/crm/best-practices#recommended-setup) for guidance on setting up deal value conversion in your workflow.
{% endhint %}

</details>

<details>

<summary>Why does the Deals export show limited data for some deals?</summary>

When the user account linked to your API key does not have permission to manage a specific deal pipeline, ActiveCampaign's API returns restricted data for those deals. You'll typically see only the `id`, `title`, and `isDisabled = 1` fields.

To resolve this:

1. In ActiveCampaign, go to **Settings > Users** and verify that the account used for authentication has permission to manage all pipelines.
2. If not, regenerate the API key from an admin account with full pipeline access and update the connection in Coupler.io.

</details>

<details>

<summary>Can I export automation data from ActiveCampaign?</summary>

No. ActiveCampaign's automation run history — such as which contacts are enrolled in which automations, step completion data, or goal achievement rates — is not available via the ActiveCampaign REST API. Coupler.io exports raw entity records only.

To analyze automation performance, use ActiveCampaign's built-in **Automations** reports directly within the platform.

</details>

<details>

<summary>How do I combine Deals with Contacts data?</summary>

Each Coupler.io data flow exports one entity, but you can combine them using Coupler.io's **data join** feature:

1. Create a data flow for **Deals** — note the `contact` field, which contains the linked contact's ID
2. Create a data flow for **Contacts** — the `id` field is the contact identifier
3. Use a data join to match `contact` (from Deals) with `id` (from Contacts)

This enriches your deals data with the contact's email, name, phone, and other fields.

</details>

<details>

<summary>What's the difference between "opens" and "uniqueopens" in Campaigns?</summary>

* **`opens`** — the total number of times the campaign email was opened, including multiple opens from the same contact
* **`uniqueopens`** — the number of individual contacts who opened the email (each contact counted once)

For calculating **open rate**, always use `uniqueopens` divided by `send_amt`. Using `opens` overstates the rate because it counts repeat opens from the same person.

The same logic applies to `linkclicks` vs. `uniquelinkclicks` for click rate.

</details>

<details>

<summary>My data flow is timing out. What should I do?</summary>

Timeouts can occur when exporting large datasets, particularly for accounts with many thousands of contacts. To address this:

1. Schedule the data flow to run during **off-peak hours** (e.g., overnight) when API load is lower
2. If you only need a subset of fields, use Coupler.io's **column selection** in the Transform step to drop unused columns before loading to the destination
3. Contact Coupler.io support with your data flow URL if the timeout persists — they can advise on configuration options for large accounts

{% hint style="info" %}
See [Common Issues](https://docs.coupler.io/sources/category/crm/common-issues#rate-limits) for more troubleshooting steps related to timeouts and rate limits.
{% endhint %}

</details>

<details>

<summary>Can I export ActiveCampaign reports or email analytics dashboards?</summary>

No. ActiveCampaign's built-in reports and dashboard analytics are not accessible via the API. Coupler.io exports raw entity data — for example, the Campaigns entity includes aggregate metrics (opens, clicks, bounces) per campaign, but not the visual reports or custom date-range breakdowns shown in the ActiveCampaign interface.

To recreate report-style analysis, export the Campaigns entity and build aggregations in your destination — Google Sheets, Looker Studio, Power BI, or BigQuery.

</details>
