Skip to content
Optima docs
Get started

Key concepts

The main ideas in Optima on one page, with a link to the full explanation of each.

Optima uses a small number of ideas everywhere. Learn these and every screen makes sense.

Profiles and entities

A profile is Optima's record of one subject: a customer, a household, a device, an account. An entity type defines a kind of profile and the attributes it can carry. A profile has identifiers (such as an email address or a loyalty number) that Optima uses to recognise it, and attributes (such as a name, a city or a lifetime value). Read more.

Events

An event is something that happened to a profile at a point in time: a purchase, a page view, a login, a message opened. Profiles say who someone is; events say what they did and when. Read more.

Identity

The same person often appears under several identifiers. Identity resolution applies rules you define to recognise them as one identity cluster, without changing the original profiles. Read more.

Attributes and computed attributes

Most attributes are stored. A computed attribute is defined once and worked out from current data when it is needed, for example a lifecycle stage or spend over the last 90 days. Read more.

Segments, signals and cohorts

A segment is a saved audience: a question about your profiles that is answered live. A signal is a score computed per profile, such as churn risk. A cohort is a named group defined by signal values. Read more.

Every use of personal data happens for a declared purpose, such as marketing or analytics. Optima checks the purpose against the customer's consent and against what the person acting is allowed to see. Read more.

Channels and delivery

A channel is a way of reaching a customer: email, SMS, push, WhatsApp and others, plus on-site and in-app channels. Providers do the sending. Contact policies such as fatigue limits and silent hours decide when a message may go out. Read more.

Licences and roles

Your organisation's licence decides which features exist. Your roles decide which of those you can see and change. Read more.

Tenants and environments

Your data lives in a tenant, also called an environment: an isolated space with its own profiles, events, configuration, team and API keys. A company account can have several, for example production and sandbox. A sandbox sends nothing to real people. The tenant switcher in the top bar changes which one you are working in.

Where to go next

Pick the reading path for your job on the Start here pages, or see how the screens are laid out in the Console section.

On this page