For the complete documentation index, see llms.txt. This page is also available as Markdown.

ActiveCampaign

ActiveCampaign is a customer experience automation platform that combines email marketing, CRM, and marketing automation. Sales, marketing, and customer success teams use it to manage contacts, run email campaigns, track deals, and automate outreach across the customer lifecycle. By connecting ActiveCampaign to Coupler.io, you can automatically export CRM and email data to spreadsheets, BI tools, or data warehouses — without manual exports or custom code.

Coupler.io's ActiveCampaign integration pulls data from the ActiveCampaign REST API using API key authentication, covering 6 data entities: Campaigns, Contacts, Lists, Deals, Segments, and Forms.

Why connect ActiveCampaign to Coupler.io?

  • Automate email performance reporting — Schedule regular exports of campaign data (opens, clicks, bounces, unsubscribes) so your email dashboards are always current without manual downloads.

  • Track your sales pipeline — Pull Deals data to build custom pipeline reports, monitor win rates, and track deal values over time.

  • Analyze contact and list health — Export Contacts and Lists to monitor list growth, bounce rates, and subscriber engagement trends.

  • Build cross-platform dashboards — Combine ActiveCampaign data with advertising, e-commerce, or finance data from other sources for a unified view.

  • Flexible destinations — Export to AI tools, Google Sheets, Excel, BigQuery, Looker Studio, or other supported destinations.

Prerequisites

Before connecting, make sure you have:

  • An ActiveCampaign account with access to the data you want to export

  • Your ActiveCampaign API key and account username — find these under Settings > Developer in ActiveCampaign

  • A Coupler.io account

The ActiveCampaign API key is tied to your user account. If your account has restricted permissions (e.g., limited deal pipeline access), the exported data will reflect those restrictions. Use an admin account for full access.

Quick start

How to connect

1

In Coupler.io, create a new data flow and select ActiveCampaign as the source.

2

Enter your account username and API key in the connection form. Your API key is available under Settings > Developer in your ActiveCampaign account.

3

Select a data entity — Campaigns, Contacts, Lists, Deals, Segments, or Forms.

4

Choose your destination and run the import.

ActiveCampaign 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

  • 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.

  • 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.

  • 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.

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.

ActiveCampaign common issues

Connection issues

Invalid API key or account username — connection fails immediately

Problem: Coupler.io cannot connect to ActiveCampaign and returns an authentication error after entering your credentials. A common error in the logs looks like:

This error usually means the Account username was entered incorrectly.

Fix:

  1. Verify your account username — this is the subdomain from your ActiveCampaign URL, not your company's display name or email address. For example, if your account URL is https://mycompany.activehosted.com, your username is mycompany (no spaces, no capitals, no full URL).

  1. Double-check your API key by going to Settings > Developer in your ActiveCampaign account. Copy the key exactly — it should be a long alphanumeric string.

  2. Make sure you're using credentials from the correct ActiveCampaign account if you manage multiple accounts.

  3. If your credentials recently changed (e.g., API key was regenerated), update the connection in Coupler.io with the new key.

Connection worked before but now fails — API key regenerated or revoked

Problem: A previously working data flow now fails with an authentication error.

Fix:

  1. Go to Settings > Developer in ActiveCampaign and check whether your API key has changed or been regenerated.

  2. In Coupler.io, go to your connections, remove the existing ActiveCampaign connection, and reconnect with the updated credentials.

  3. If you're on a team account, confirm your user account has not been deactivated or had its permissions changed.

Missing data

Deals entity returns limited data — only id, title, and isDisabled appear

Problem: The Deals export contains far fewer fields than expected. Most rows show only id, title, and isDisabled = 1.

Fix:

  1. In ActiveCampaign, go to Settings > Users and verify the user account linked to your API key has access to all deal pipelines.

  2. If possible, regenerate the API key from an admin account with full pipeline permissions and reconnect in Coupler.io.

  3. Contact your ActiveCampaign admin to grant the appropriate pipeline management permissions.

Contacts export is missing recently added contacts

Problem: Contacts added in the last few hours or days don't appear in the export.

Fix:

  1. The ActiveCampaign API may have a short delay before new records become available for export. Wait a few minutes and re-run the data flow.

  2. Verify the contacts exist in ActiveCampaign by checking the Contacts list view directly.

  3. If the missing contacts were imported via a bulk CSV upload, the API sometimes lags behind — retry after the import fully processes.

Segments or Forms export returns an empty dataset

Problem: The Segments or Forms entity export returns no records, even though they exist in ActiveCampaign.

Fix:

  1. Verify that Segments or Forms have actually been created in your ActiveCampaign account under Contacts > Manage Segments or Website > Forms.

  2. If segments exist but the export is empty, try reconnecting your ActiveCampaign account in Coupler.io to refresh the API session.

  3. Check that your API key has the appropriate permissions to access segments and forms — some ActiveCampaign plan tiers may restrict API access to these entities.

Data discrepancies

Campaign open and click counts differ from the ActiveCampaign dashboard

Problem: The opens, linkclicks, or other campaign metrics exported by Coupler.io don't match the numbers shown in your ActiveCampaign campaign reports.

Fix:

  1. Check whether you're comparing total vs. unique values. The export includes both (e.g., opens vs. uniqueopens, linkclicks vs. uniquelinkclicks). The ActiveCampaign dashboard may display either depending on the view.

  2. ActiveCampaign campaign statistics can update with a short delay after sends complete. If you exported shortly after a campaign was sent, re-export to get the final numbers.

  3. The send_amt field reflects sends to active subscribers; the total_amt field reflects the total list size at send time. Make sure you're using the right field for your calculation.

Deal value looks much larger than expected

Problem: The value field in the Deals export shows numbers like 150000 instead of 1500.00.

Fix:

ActiveCampaign stores deal values in the smallest currency unit (e.g., cents for USD). A $1,500 deal is stored as 150000. Divide the value field by 100 in your destination to display the correct monetary amount.

Add a formula column in your destination (e.g., a Google Sheets formula =value/100) or use Coupler.io's formula columns feature to compute the display value.

Contacts export includes deleted contacts I didn't expect

Problem: The Contacts export contains records that appear to be inactive or deleted contacts.

Fix: The ActiveCampaign API returns both active and deleted contacts. The deleted field is set to 1 for deleted contacts and 0 for active ones. Filter your destination data on deleted = 0 to exclude deleted contacts from your analysis.

Rate limits

Data flow fails or times out on large accounts

Problem: The data flow runs for a long time and either times out or fails mid-run, particularly for large Contacts datasets.

Fix:

  1. The ActiveCampaign API paginates results. Coupler.io handles pagination automatically, but very large datasets (100,000+ contacts) can take a significant amount of time to fully export.

  2. ActiveCampaign enforces API rate limits. If the data flow is hitting limits, Coupler.io will retry automatically, but overall run time may increase.

  3. Set your data flow to run during off-peak hours (e.g., overnight) to reduce competition for API quota.

  4. If timeouts persist, contact Coupler.io support with your data flow URL for guidance on handling large-scale exports.

ActiveCampaign FAQ

Which ActiveCampaign entities can I export?

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.

Where do I find my ActiveCampaign API key?
  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.

Can I filter the data I export from ActiveCampaign?

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

See Data Overview for details on available fields per entity that can be used as filter criteria.

Why are my deal values showing very large numbers?

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

See Best Practices for guidance on setting up deal value conversion in your workflow.

Why does the Deals export show limited data for some deals?

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.

Can I export automation data from ActiveCampaign?

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.

How do I combine Deals with Contacts data?

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.

What's the difference between "opens" and "uniqueopens" in Campaigns?
  • 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.

My data flow is timing out. What should I do?

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

See Common Issues for more troubleshooting steps related to timeouts and rate limits.

Can I export ActiveCampaign reports or email analytics dashboards?

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.

Last updated

Was this helpful?