> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/active-campaign.md).

# Active Campaign

ActiveCampaign integration helps connect your website events to your ActiveCampaign account. We handle server-side event streaming for you. Setup is quick - just enter your ActiveCampaign Account ID and Event Key, and we will send events to your ActiveCampaign account.

{% hint style="info" %}
Events are associated with contacts using the email.
{% endhint %}

### Details

Channel Name: activeCampaign

### Event Flow

Events are captured from your site and delivered to ActiveCampaign via server-side API.

By default, events are sent to your contacts' **Events feed** using Event Tracking. Alternatively, events can be stored as **Custom Object records** — see the [Custom Objects](#custom-objects) section below.

### Custom Objects

Instead of the Events feed, events can be written as records to a Custom Object in your ActiveCampaign account. This mode is enabled by providing three additional settings in the channel configuration:

| Setting      | Description                                                                  |
| ------------ | ---------------------------------------------------------------------------- |
| Account Name | Your ActiveCampaign subdomain, e.g. `myaccount` from `myaccount.api-us1.com` |
| API Key      | Found in your ActiveCampaign account under Settings → Developer              |
| Schema ID    | The ID of the Custom Object schema records are written to                    |

When all three are set, each event is delivered as follows:

1. The contact is looked up by email. If the contact does not exist yet, it is created automatically.
2. A record is created on your Custom Object with the event name and event data, linked to the contact. The record's `externalId` is set to the unique event ID, so retries never create duplicate records.

If any of the three settings are missing, the channel falls back to the default Events feed mode.

{% hint style="warning" %}
Custom Objects require an ActiveCampaign Enterprise plan.

Your Custom Object schema must follow the structure described in the [onboarding guide](/channels/active-campaign/onboarding.md).
{% endhint %}

### Useful links

{% embed url="<https://developers.activecampaign.com/reference/event-tracking>" %}

{% embed url="<https://developers.activecampaign.com/reference/create-or-update-record>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.edgetag.io/channels/active-campaign.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.