> 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/configuration.md).

# Configuration

Let's review all the fields in the form and how to use them while adding the ActiveCampaign channel.

<figure><img src="/files/7jocn3e1E9XtXs8G1guS" alt=""><figcaption></figcaption></figure>

### Account ID

Account ID is unique numeric identifier that represents your specific ActiveCampaign account in their system. ActiveCampaign uses this ID to route events to the correct account. When EdgeTag sends events to ActiveCampaign's tracking endpoint, this Account ID is included in the request payload to identify which account should receive the event data.\
\
Where can you find the Account ID in ActiveCampaign?\
\
Account ID can be found in the ActiveCampaign Dashboard under\
**Website → Site Tracking → Event Tracking**

### Event Key

Event Key is a secure authentication token that validates your identity and authorizes EdgeTag to send events to your ActiveCampaign account. This key ensures that only authorized applications can send events to your ActiveCampaign account, protecting your data and preventing unauthorized access. EdgeTag includes this key in every HTTP request to ActiveCampaign's event tracking API to authenticate the request and prove that the events are coming from your authorized integration.<br>

Where can you find the Event Key in ActiveCampaign?\
\
Event Key can be found in the ActiveCampaign Dashboard under \
**Website → Site Tracking → Event Tracking**

{% hint style="info" %}
Make sure event tracking is enabled in your ActiveCampaign account.
{% endhint %}


---

# 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/configuration.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.