Events

Send behavioral events about your contacts to trigger campaigns, gate waits, and power segments.

An event is a behavioral signal you send about one of your contacts — a purchase, a page view, a feature used. Events are how EngageApp knows what your users are doing.

What an event contains

Each event has:

event_name — what happened (e.g. purchase).
properties — an object of extra detail about the event (e.g. amount, product ID).
occurred_at — when it happened.
external_id — ties the event to a contact.

Sending events

Ingest events one of two ways:

Public API — call POST /api/v1/public/events to batch events from your backend.
SDK — emit events from your app through a client SDK.

What events power

Event-triggered campaigns — start a flow the moment an event arrives. See Triggers.
wait_until steps — hold a contact in a flow until they perform (or fail to perform) a given event.
Segment rules — build audiences from event history. See Segments.

Reviewing events

Open the Events page to review recent events as they arrive. This is the fastest way to confirm your integration is sending the data you expect before you build automation on top of it.

Next steps

See how events attach to people in Contacts.
Fire a campaign on an event with Triggers.
Build behavioral audiences with Segments.
Integrate ingestion via the public API reference.

Contacts

How EngageApp models your end-users as contacts, the fields they carry, and the ways to add them.

Triggers & enrollment

A trigger decides how contacts get enrolled into a campaign — manually, by event, on a schedule, or when they join or leave a segment.

Segments

Group contacts by attribute and behavior rules to target campaigns and manual enrollments.

Public API reference

The public HTTP API for server-side and SDK integrations — authentication headers and endpoints.