Overview

The ActiveCampaign integration imports your ActiveCampaign accounts, contacts and deals into Summit53. It is read-only upstream: Summit53 only reads from ActiveCampaign and never creates, changes or deletes anything there. Deals arrive as Summit53 opportunities, so they flow into pipeline, forecasting and framework analysis like any other CRM record.

Open it from Integrations by selecting Connect on the ActiveCampaign row (or Manage once it is connected), or go directly to /admin/integrations/activecampaign. The page header shows the connection status: Not configured, Test required or Connected.

Only organisation owners and administrators can manage ActiveCampaign. Other members see “Only organization owners and administrators can manage ActiveCampaign.”

Tabs

Credentials: save the API URL and token, test the connection, or disconnect. This is the default tab.
Configuration: choose the default owner and which record types to import, and check owner matching and pipeline access.
Sync: turn on automatic sync, preview and start manual syncs, check sync health, and review recent runs.
Field Mapping: override built-in mappings and map ActiveCampaign custom fields.

Before You Start

Create a dedicated integration user in ActiveCampaign and copy its API URL and API token from ActiveCampaign.
Give that user access to the deal pipelines and stages you want to import, and permission to read users (needed to match owners).
Make sure the people who own records in ActiveCampaign are approved Summit53 members with the same email address, so ownership carries across.

Credentials

In ActiveCampaign API URL, enter your account’s API address, for example https://your-account.api-us1.com. Enter the address only: Summit53 adds the API path itself. The URL must use HTTPS.
In API token, paste the integration user’s token. The token is encrypted and never shown again on the page. Once a token is stored, you can leave the field blank on later saves to keep it.
Select Save credentials. You will see “Credentials saved. Test the connection before syncing.”
Select Test connection. Summit53 checks it can read the API user, your users, pipelines, stages and deals. A successful test shows Connection verified and switches the integration on.

Changing the token or the API URL switches the connection off until you test it again.

Disconnecting

Select Disconnect, then Disconnect now to confirm. This clears the stored token, stops future syncs and turns off automatic sync. Records already imported into Summit53 are kept.

Configuration

Optionally enter a Connection label to name this connection.
Choose a Default Summit53 owner. This person owns any record whose ActiveCampaign owner cannot be matched by email. It is required.
Under Record types, choose Accounts, Contacts and Deals. All three are selected by default; at least one must be.
Select Save configuration.

Two panels help you check the setup:

Owner matching lists your ActiveCampaign users, each marked Email matched or Uses default.
Pipeline access lists the pipelines and stages the API user can see. If a pipeline is missing, grant the API user access to it in ActiveCampaign and test again.

Sync

Manual sync

Under Preview and run, choose a Sync mode:
- Full sync: reads every enabled record type in full. Use it for the first import.
- Incremental sync: reads contacts and deals changed since the last successful sync. Accounts and reference data are still read in full.
Optionally select Preview sync to see counts of users, pipelines, stages, accounts, associations, contacts and deals before importing.
Select Start full sync or Start incremental sync. Only one sync can run at a time.

The run card shows a progress bar, counts of Fetched, Imported, Updated and Skipped records, and the phases: Users, pipelines, stages; Accounts; Account associations; Contacts; Deals; Account rollups. If a run fails, the card shows the phase that failed and a Resume failed sync button. Resuming runs every phase again.

Automatic incremental sync

Automatic sync is off by default. It is available once the connection has been tested successfully.

Turn on Automatic incremental sync.
Choose an Organization cadence: Every 30 minutes (default), Hourly, Every 6 hours or Daily.
Select Save automatic sync.

Automatic runs are always incremental. The cadence is the earliest your organisation becomes due again after its last successful sync, manual or scheduled. Summit53 checks for due organisations every few minutes, so a run may start a little after that point. The Schedule timeline shows the last successful sync, the last scheduled attempt and the next eligible run.

After a temporary failure, automatic sync waits through a retry cooldown that gets longer with each failure. If the credentials, configuration or API user permissions stop working, automatic sync pauses until you fix the problem. Then select Retry automatic sync.

Sync health and history

Sync health shows a status (healthy, degraded or failing), the last successful sync, the 7-day error rate and the average latency. A connection is degraded at a 2% error rate or after 48 hours without a successful sync, and failing at 10% or after 7 days. Degraded or failing connections show Needs attention on the Integrations page.
Recent syncs lists the last 10 runs with their source (Scheduled or Manual), mode, status, start time and record counts.

What Gets Imported

Accounts become Summit53 accounts (name, website and owner). Accounts without a name are skipped.
Contacts become Summit53 contacts (name, email, phone, job title and owner), linked to their account. Contacts without an email, and deleted or anonymised contacts, are skipped.
Deals become Summit53 opportunities with amount, currency, expected close date, description, stage, probability and owner. Won deals are imported as Closed Won and lost deals as Closed Lost.
Contacts and deals with no ActiveCampaign account are placed under an account called Unassigned ActiveCampaign Records.
Pipeline stages are mapped to Summit53 stages automatically by name (for example, stages containing “proposal” map to Proposal). Existing stage mappings are not overwritten.
Owners are matched to Summit53 members by email. Unmatched owners fall back to the default owner.

Re-running a sync updates the records it imported before rather than creating duplicates.

Field Mapping

Built-in mappings apply unless you override them. Add mappings only for fields that need a different Summit53 destination.

Standard field overrides: select Add standard mapping, then choose the ActiveCampaign source field, the Summit53 field for the same record type, an optional Transformation (for example Currency to number or Parse date), an optional default value, and whether it is a Required value.
Custom field mappings: select Add custom mapping, then choose an ActiveCampaign custom field, the Summit53 field, its Value type, an optional default value, and whether it is a Critical value.

Select Save field mappings to apply the whole set; changes apply from the next sync. If a required or critical value is missing or invalid, that record is skipped. You can add up to 100 mappings of each type.

Quick Start

Open Integrations and select Connect on the ActiveCampaign row.
On Credentials, enter the API URL and token, select Save credentials, then Test connection.
On Configuration, choose a default owner and record types, then Save configuration.
On Sync, run a Full sync.
Turn on Automatic incremental sync to keep Summit53 up to date.

Troubleshooting

Credentials rejected: the API URL or token is wrong. Copy both again from ActiveCampaign and save.
Permission update needed: the API user cannot see every deal pipeline and stage, deals or users. Update its permissions in ActiveCampaign, then select Test connection again.
Rate limit reached: ActiveCampaign is limiting requests. Wait for the time shown and test again.
“The ActiveCampaign API hostname is not in the configured allowlist.”: your account uses an API host Summit53 does not accept yet. Contact Summit53 support.
“No approved Summit53 owners are available.”: approve at least one organisation member before saving the configuration.
Records are skipped: check for missing names or emails, an unmatched owner with no default owner, or a required field mapping with no value.
“An ActiveCampaign sync is already running.”: wait for the current run to finish; the page attaches to it automatically.
Progress stops updating: the page stops checking after five minutes. Reopen the Sync tab to continue monitoring.

ActiveCampaign Integration: Connect, Sync & Field Mapping