Core concepts

Organisation, workspaces and environments

• Organisation. Your company account. It owns members and workspaces.
• Workspace. One product or brand, such as acme-shop. Data is never shared across workspaces.
• Environment. Every workspace has two: Test and Live. They hold separate data, keys, segments and campaigns. See Test and Live.

The console URL shows where you are: /w/<workspace>/<test|live>/….

Profiles and identity

A profile is one person. It holds attributes (name, plan, city), devices, contact details and a timeline.

• A person who has not logged in is anonymous. The SDK gives them an anonymous id.
• When you call identify with your own user id (the external id), the anonymous profile is linked to that id. If another profile already holds it, the two are merged.
• Servers can address a person by external id, email or phone. See Send server events.
• Contact details are masked in the console. Revealing one needs a reason and is recorded.

Events

An event is something a person did, such as Order Placed. It has a name, optional properties and a time. Events trigger campaigns and flows, build segments and feed Analytics.

• Names are title case and identical across platforms.
• Reserved names (for example App Opened) come from the SDK. Your code cannot send them.
• Property types are learned from the first value you send, so send real numbers and booleans.

Segments

A segment is a saved audience defined by attributes and behaviour, such as "placed an order in the last 30 days and lives in Indore". A segment shows a live count and can be the audience of a campaign.

Campaigns and flows

	Campaign	Flow
Shape	One message, optionally with variants	Several steps on a canvas
Types	One-time, recurring, event-triggered, API-triggered, transactional	Entered by event, schedule, business event, another flow's exit, or API
Use it for	A sale announcement, a receipt, a reminder	An onboarding series, win-back, cart recovery with waits and branches

Both can use push, email, SMS and in-app messages, and both can have a conversion goal.

A transactional message is a one-to-one send such as an OTP or a confirmation. You define an endpoint in the console and call it from your backend. See Send a transactional message.

A business event is a named signal your backend activates, such as market_open. One activation starts every flow bound to it. See Activate a business event.

Templates

A template is reusable message content for one channel. Campaigns and flows pick a template instead of holding their own copy. You can preview it with a real profile, send a test, and publish a version when it is ready. See Templates overview.

Apps

An app is one web, iOS or Android app registered in a workspace. A new app stays pending until it proves itself: a mobile app by its first SDK event, a website by a record on its domain. See Register your apps.

Smart links

A smart link is one web address that opens your app on the right screen, sends people without the app to the store, and counts clicks, installs and opens. See Smart Links overview.

Ad platforms

Ad platforms connects a workspace to Google Ads, Meta and Google Analytics 4. TrueEngage records which ad brought each person, sends the events you choose as conversions, and syncs segments as ad audiences. Everything is consent gated. See Ad platforms.

The send gate

Every send passes through the same checks:

• Consent and opt-out status.
• Frequency caps.
• Quiet hours and do-not-disturb.
• In Test, the allowlist of people who may receive messages.

Transactional sends skip frequency caps and do-not-disturb, because an OTP cannot wait. Consent still applies unless the endpoint is set to bypass it.

Next

• Quickstart
• Test and Live
• Team and roles