# Data Overview

Coupler.io's ActiveCampaign integration pulls data from the ActiveCampaign REST API (v3). You select one entity per data flow — email marketing entities like Campaigns or Lists, CRM entities like Contacts or Deals, or audience-management entities like Segments and Forms.

## Available data entities

| Entity        | Description                                                                                                                                                            | Typical use case                                |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
| **Campaigns** | Email campaigns with engagement metrics: sends, opens, clicks, bounces, unsubscribes, forwards, and replies. Includes campaign type, status, and scheduled/sent dates. | Email performance dashboards, A/B test tracking |
| **Contacts**  | CRM contact records with email, name, phone, organization link, bounce status, and engagement dates (created, updated, email-changed, last active).                    | Contact list management, engagement analysis    |
| **Lists**     | Subscriber/mailing lists with name, opt-in settings, tracking flags, sender details, and subscription/unsubscription notification settings.                            | List health monitoring, subscriber growth       |
| **Deals**     | CRM pipeline deals with title, value, currency, pipeline, stage, owner, linked contact, win probability, and status (open/won/lost).                                   | Sales pipeline dashboards, revenue forecasting  |
| **Segments**  | Audience segments built from contact conditions used to scope campaigns and automations.                                                                               | Audience analysis, segment auditing             |
| **Forms**     | Lead capture and subscription forms with name, type, action settings, and created/modified dates.                                                                      | Form inventory, lead source tracking            |

## Configuration options

#### Entity selection

Each data flow exports one entity. To combine data from multiple entities — for example, enriching Deals with contact details — set up a separate data flow for each entity and use Coupler.io's data join feature.

## Entity field reference

#### Campaigns

| Field              | Description                                          |
| ------------------ | ---------------------------------------------------- |
| `id`               | Unique campaign ID                                   |
| `name`             | Campaign name                                        |
| `type`             | Campaign type (e.g., `single`, `recurring`, `split`) |
| `status`           | Campaign status (0 = draft, 1 = scheduled, 5 = sent) |
| `cdate`            | Created date                                         |
| `mdate`            | Last modified date                                   |
| `sdate`            | Scheduled send date                                  |
| `ldate`            | Last sent date                                       |
| `send_amt`         | Number of emails sent                                |
| `total_amt`        | Total recipients                                     |
| `opens`            | Total opens                                          |
| `uniqueopens`      | Unique opens                                         |
| `linkclicks`       | Total link clicks                                    |
| `uniquelinkclicks` | Unique link clicks                                   |
| `hardbounces`      | Hard bounce count                                    |
| `softbounces`      | Soft bounce count                                    |
| `unsubscribes`     | Unsubscribe count                                    |
| `forwards`         | Forward count                                        |
| `replies`          | Reply count                                          |
| `userid`           | Owner user ID                                        |

#### Contacts

| Field          | Description                 |
| -------------- | --------------------------- |
| `id`           | Unique contact ID           |
| `email`        | Email address               |
| `firstName`    | First name                  |
| `lastName`     | Last name                   |
| `phone`        | Phone number                |
| `orgid`        | Linked organization ID      |
| `cdate`        | Contact created date        |
| `udate`        | Last updated date           |
| `adate`        | Last active date            |
| `edate`        | Email last changed date     |
| `bounced_hard` | Hard bounce flag (0/1)      |
| `bounced_soft` | Soft bounce flag (0/1)      |
| `bounced_date` | Date of last bounce         |
| `sentcnt`      | Total sends to this contact |
| `deleted`      | Deleted flag (0/1)          |

#### Lists

| Field                  | Description                     |
| ---------------------- | ------------------------------- |
| `id`                   | Unique list ID                  |
| `name`                 | List name                       |
| `stringid`             | URL-safe list slug              |
| `cdate`                | List created date               |
| `udate`                | Last updated date               |
| `userid`               | Owner user ID                   |
| `private`              | Private list flag (0/1)         |
| `optinoptout`          | Double opt-in enabled (1 = yes) |
| `sender_name`          | Sender display name             |
| `sender_addr1`         | Sender address line 1           |
| `sender_city`          | Sender city                     |
| `sender_country`       | Sender country                  |
| `p_use_tracking`       | Open tracking enabled flag      |
| `p_use_analytics_read` | Analytics read tracking flag    |
| `p_use_analytics_link` | Analytics link tracking flag    |

#### Deals

| Field            | Description                                         |
| ---------------- | --------------------------------------------------- |
| `id`             | Unique deal ID                                      |
| `title`          | Deal name                                           |
| `description`    | Deal description                                    |
| `value`          | Deal value (in smallest currency unit, e.g., cents) |
| `currency`       | Currency code (e.g., `usd`)                         |
| `status`         | Status (0 = open, 1 = won, 2 = lost)                |
| `owner`          | Owner user ID                                       |
| `contact`        | Linked contact ID                                   |
| `organization`   | Linked organization ID                              |
| `group`          | Pipeline ID                                         |
| `stage`          | Stage ID                                            |
| `percent`        | Close probability percentage                        |
| `winProbability` | AI-predicted win probability                        |
| `cdate`          | Created date                                        |
| `mdate`          | Last modified date                                  |
| `edate`          | Expected close date                                 |
| `nextdate`       | Next task due date                                  |
| `activitycount`  | Number of deal activities                           |

#### Segments

| Field               | Description                  |
| ------------------- | ---------------------------- |
| `id`                | Unique segment ID            |
| `name`              | Segment name                 |
| `logic`             | Condition logic (`and`/`or`) |
| `hidden`            | Hidden flag                  |
| `created_timestamp` | Created date                 |
| `updated_timestamp` | Last updated date            |

#### Forms

| Field        | Description                     |
| ------------ | ------------------------------- |
| `id`         | Unique form ID                  |
| `name`       | Form name                       |
| `action`     | Form submission action type     |
| `actiondata` | Submission action configuration |
| `cdate`      | Created date                    |
| `mdate`      | Last modified date              |
| `userid`     | Owner user ID                   |

## Use cases by role

{% tabs %}
{% tab title="Marketing teams" %}

* Export Campaigns to track email performance (open rates, click rates, bounce rates, unsubscribes) over time and across different campaign types.
* Use Lists to monitor subscriber counts per list and track growth trends.
* Combine Contacts with Campaigns data to build engagement-tier segmentation for reporting.
  {% endtab %}

{% tab title="Sales teams" %}

* Pull Deals to build custom pipeline dashboards that show deals by stage, owner, pipeline, and win probability.
* Use the `value` and `currency` fields to calculate forecasted revenue per stage.
* Join Deals with Contacts to add contact-level context to each deal record.
  {% endtab %}

{% tab title="Operations and RevOps" %}

* Export all six entities across separate data flows and join them in your BI tool for a unified view of marketing and sales activity.
* Use Segments to audit which audience conditions are driving your campaigns.
* Track Forms to understand lead capture points and connect form submissions to downstream deal activity.
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* **Deal values are in the smallest currency unit** — The `value` field for Deals stores monetary amounts in cents (or the smallest unit for the currency). For example, a $1,500 deal is stored as `150000`. Divide by 100 in your destination to display the correct dollar amount.
* **Deal pipeline access is permission-scoped** — If the connected API key's user does not have permission to manage a specific pipeline, the API returns limited deal data (only `id`, `title`, and `isDisabled = 1`). Use an admin API key for full deal access across all pipelines.
* **Contacts includes active and deleted records** — The `deleted` field (0/1) indicates whether a contact has been deleted. Filter on `deleted = 0` in your destination if you want to exclude deleted contacts.
* **No date filtering in the source config** — The ActiveCampaign source does not include a date range filter. All records are exported on each run. Use Coupler.io's "Replace" destination mode to overwrite the dataset on each refresh rather than accumulating rows.
* **Automations and email replies are not available** — Automation run history and individual email reply content are not exported by this integration. Only campaign-level aggregate metrics are available.