Track Event: ActiveCampaign action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Contact Email email	string	Required	Contact Email. e.g. "user@example.com"
Event Name event	string	Required	Event Name. Example: purchase_completed
Event Data eventdata	string	Optional	Additional data for the event

Sample request

{
  "email": "user@example.com",
  "event": "e.g. purchase_completed",
  "eventdata": "e.g. product=Pro Plan"
}

Returns

{
  "success": 1
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Track Event.

What does the Track Event action do in ActiveCampaign?

Pushes a custom behavioural event into ActiveCampaign's event store, where automation triggers can react to it. Requires Event Tracking to be enabled in the AC account. Useful for "user did X in our product → start the X-completed nurture flow" patterns where the event happens outside AC's native form/email tracking.

What inputs does Track Event require?

Required: Contact Email, Event Name. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if ActiveCampaign returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Track Event support batch operations?

Yes. Run Track Event inside a Loop node to process arrays. Tiny Command handles ActiveCampaign's rate limits automatically so you don't have to throttle manually.

More actions