Key concepts

EngageApp is built from a small set of objects that fit together. Once these click, the rest of the product is easy to navigate. This page defines each one.

Audience

Contact

One of your end-users, identified by your own external_id. A contact can carry an email, phone number, first and last name, custom attributes, a timezone, a subscribed flag, and one or more registered devices.

Segment

A rule-based audience. A segment can be dynamic (membership updates automatically as contacts match or stop matching the rules) or static (a fixed list).

Event

A behavioral event you send about a contact — something they did, which campaigns can react to.

Topic

A subscription category contacts opt into. Topics let people choose which kinds of messages they want to receive.

Channels and content

Channel

A configured delivery method: Email, SMS, WhatsApp, Push, Custom API, or In-App Takeover. See channels.

Template

The message content for a channel, with {{ variable }} merge fields resolved per contact at send time.

Campaigns

Campaign

A visual, multi-step flow that enrolls contacts and sends them messages. See campaigns.

Step

A node in a campaign. Types include send_message, delay, condition, wait_until, and action.

Edge

A connection between two steps. Edges are typed default, true, or false.

Enrollment

A single contact's run through a campaign.

Trigger

How contacts enter a campaign: manual, event, schedule, or segment.

Blueprint

A pre-built campaign in the Gallery you can clone into an editable draft.

Delivery and billing

Suppression

A block on sending to a particular recipient. See suppressions.

Credits & Wallet

EngageApp is prepaid — you top up credits in your wallet and each send debits from that balance. See billing.

Next steps

• Build one in campaigns overview.
• Define an audience with segments.
• Send behavioral events to power triggers.
• Let contacts self-select with topics.