Source connector

ActiveCampaign connector

ActiveCampaign integration for databases, warehouses and BI tools

CRM plus marketing automation and journeys. Datrise captures ActiveCampaign entities such as contacts, automations, campaigns, and sales pipeline updates, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The ActiveCampaign API v3 authenticates with API key, incremental runs key on filters[updated_after] / filters[updated_before], and ActiveCampaign caps calls at 5 requests per second per account.

Of the 4 objects, 4 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `activecampaign_contacts`) with a schema derived from the ActiveCampaign API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the ActiveCampaign pipeline page, and join the waitlist to get the ActiveCampaign connector (Marketing) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What ActiveCampaign data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
contacts	activecampaign_contacts	Upsert by primary key, incremental on updated-at
automations	activecampaign_automations	Upsert by primary key, incremental on updated-at
campaigns	activecampaign_campaigns	Upsert by primary key, incremental on updated-at
sales pipeline updates	activecampaign_sales_pipeline_updates	Upsert by primary key, incremental on updated-at

ActiveCampaign API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	ActiveCampaign API v3
Authentication	API key — Every request carries the account's API key in an `Api-Token` header; the key is generated per-account under Settings > Developer, and requests go to `https://<account-name>.api-us1.com`.
Pagination	offset — List endpoints take `limit` (default 20, max 100) and `offset` query params; the response's `meta.total` gives the total record count for the collection.
Rate limit	5 requests per second per account
Incremental cursor	filters[updated_after] / filters[updated_before] — For high-volume contact lists, ActiveCampaign's own docs recommend `orders[id]=ASC` with `id_greater` instead of `offset` pagination, since deep offset paging degrades in performance.
Webhooks	Yes — Account Webhooks (Settings > Webhooks)
Bulk export	No
Deletes detectable	No — Deleted contacts and other objects are removed from list/filter endpoint results with no documented `deleted` flag or tombstone; detection requires diffing full ID snapshots or relying on webhook events at the time of deletion

Official API reference

What bites when replicating ActiveCampaign

The rate limit is a strict 5 requests per second per account with no documented burst allowance, reported via `RateLimit-Limit`/`RateLimit-Remaining` headers and a `Retry-After` value on HTTP 429.
List endpoints cap `limit` at 100 and default to 20, and offset-based paging is explicitly discouraged by ActiveCampaign for large contact tables in favor of `orders[id]=ASC` combined with `id_greater`.
Webhooks are delivered at-least-once but are explicitly never retried on failure, so a temporarily-down receiver permanently misses that event rather than getting a redelivery.
There is no documented `deleted` flag on contacts or deals; once a record is removed it simply disappears from list/filter results, so incremental syncs based only on `filters[updated_after]` never see deletions.

Compare this against every other documented API

Popular destinations for ActiveCampaign

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

ActiveCampaign connector FAQ

What ActiveCampaign data does the connector extract?: 4 objects: contacts, automations, campaigns and sales pipeline updates. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the ActiveCampaign integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load ActiveCampaign data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each ActiveCampaign → destination pair has its own page with the object-to-table mapping.

Related Marketing sources

Other sources in the same category, each with its own connector page.

Early access

Launch your ActiveCampaign pipeline with guided onboarding

Join the waitlist to get priority access for ActiveCampaign integrations with guided setup, schema-aware mapping, and production-grade incremental sync.