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.
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
The contact must already exist in ActiveCampaign. DinMo does not create contacts while sending events. An event for an unknown email is rejected.
Use Synchronize contact attributes to create contacts before sending their events.
Activation configuration
Fields mapping
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.
Last updated