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

# Send events

## Overview

The ActiveCampaign Events destination sends a named event and an optional text value to an existing ActiveCampaign contact matched by email.

To get started:

* Add the Event Tracking credentials described in the [connection guide](/integrations/destination-platforms/active-campaign.md#authentication-for-events).
* Create a model or segment containing the events to send.
* Configure an activation using the **Events** destination service.

## Destination setup

### Event Tracking credentials

The ActiveCampaign connection must contain its API URL, API Key, Event Key, and numeric Account ID. You can add the Event Tracking credentials to an existing connection when you configure the Events destination.

### Existing contacts

{% hint style="warning" %}
The contact must already exist in ActiveCampaign. DinMo does not create contacts while sending events. An event for an unknown email is rejected.
{% endhint %}

Use [Synchronize contact attributes](/integrations/destination-platforms/active-campaign/synchronize-contact-attributes.md) to create contacts before sending their events.

## Activation configuration

### Fields mapping

| Field      | Required                                      | Description                                                                      |
| ---------- | --------------------------------------------- | -------------------------------------------------------------------------------- |
| Email      | Yes                                           | Email address of the existing ActiveCampaign contact.                            |
| Event name | Yes, unless a static event name is configured | Name of the activity, with a maximum length of 32 characters.                    |
| Event data | No                                            | One text value describing the event, such as an order reference or download URL. |

Choose exactly one way to provide the event name:

* Enter a static **Event name** in the activation configuration to send the same name for every row.
* Leave the static value empty and map a source field to **Event name**.

Static event names are trimmed and limited to 32 characters. Mapped event names must also be present and no longer than 32 characters for every submitted row.

### Event data

Map a source field to **Event data** when you want to attach one additional text value to the event.

ActiveCampaign accepts a single `eventdata` value. The Event Tracking endpoint does not expose separate custom event properties.

### Event time

ActiveCampaign Event Tracking does not accept an event timestamp. The destination does not map an occurrence time or support historical backdating.

### Scheduling

Choose the synchronization schedule as for other event activations. ActiveCampaign does not provide an idempotency key for this endpoint. DinMo serializes runs for a given activation and does not automatically replay a request whose delivery result is ambiguous. Review ambiguous failures before retrying them.


---

# 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/send-events.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.