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

# ActiveCampaign

Sending data to ActiveCampaign: Step-by-Step Guide

## Supported Destination Services

DinMo supports the following destination services:

* [Synchronize contact attributes](/integrations/destination-platforms/active-campaign/synchronize-contact-attributes.md), to create contacts and update their standard and custom fields.
* [Export audiences](/integrations/destination-platforms/active-campaign/export-audiences.md), to keep ActiveCampaign contact lists synchronized with your DinMo segments.
* [Synchronize contact tags](/integrations/destination-platforms/active-campaign/synchronize-contact-tags.md), to add or remove a selected or newly created contact tag as contacts enter or leave your DinMo segment, using the audience destination service.
* [Send events](/integrations/destination-platforms/active-campaign/send-events.md), to send named events and optional event data to existing ActiveCampaign contacts.

Please refer to the dedicated documentation page for more information.

## Authentication to ActiveCampaign

For contact attributes, audiences, and contact tags, DinMo connects to ActiveCampaign using your account's **API URL** and **API Key**. Event Tracking uses separate credentials, described in the [Events authentication section](#authentication-for-events).

### Retrieve your credentials

1. Sign in to your ActiveCampaign account.
2. Open **Settings**, then select **Developer**.
3. Copy your **API URL** and **API Key**.

Use the exact API URL displayed in your account's Developer settings.

{% hint style="info" %}
Refer to the [ActiveCampaign documentation](https://help.activecampaign.com/hc/en-us/articles/207317590-Getting-started-with-the-API) for more information about retrieving your credentials.
{% endhint %}

### Connect ActiveCampaign to DinMo

1. In DinMo, navigate to **Destinations**.
2. Click **New destination**.
3. Click **Connect a new platform** and select **ActiveCampaign**.
4. Enter a name for your connection.
5. Paste your **API URL** and **API Key** into the corresponding fields.
6. Continue and select the destination service.
7. Complete its configuration and save.

If you already have an ActiveCampaign connection, you can reuse it when creating another destination.

{% hint style="info" %}
Learn how to create a destination in our [step-by-step tutorial](/guides/get-started-with-dinmo/initial-configuration-of-dinmo/create-a-destination.md).
{% endhint %}

## Authentication for events

ActiveCampaign Events uses two credential pairs on the same connection:

* **API URL** and **API Key** let DinMo verify that the contact already exists.
* **Event Key** and the numeric **Account ID** (`actid`) let DinMo submit the event through Event Tracking.

When you select the Events destination service, add the Event Tracking credentials to your new or existing ActiveCampaign connection. The Event Key and Account ID must be provided together. Connections without them remain valid for contact attributes, audiences, and contact tags.

To retrieve the Event Tracking credentials:

1. In ActiveCampaign, open **Website → Site Tracking**.
2. Scroll to **Event Tracking** and enable tracking.
3. Copy the **Event Key**.
4. Open **Event Tracking API** and copy the numeric **Account ID** (`actid`).

Enter the Account ID exactly as displayed. It can contain any number of digits, but no letters or spaces.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dinmo.io/integrations/destination-platforms/active-campaign.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.