Events
What an event is, how events attach to profiles and how they are added, read and corrected.
An event records something that happened to a profile: a purchase, a page view, a login, an email opened. Profiles describe who someone is; events describe what they did and when. Behaviour-based segments, signals, analytics and attribution are all built from events.
What an event holds
| Part | Meaning |
|---|---|
| Event type | The kind of event, for example purchase or page_view. |
| Profile | The one profile the event belongs to. |
| Timestamp | When it happened. Leave it empty when adding an event in the console to use the current time. |
| Source | Where the event came from, for example a website, an app or a connector. |
| Attributes | The details: order value, product, page address, and so on. Each attribute has a type. |
Events are not edited casually. They form the record of what happened, and corrections are possible but tracked.
Event types: the schema
An event type defines one category of event and the attributes it can carry, including their types, PII levels and consent purposes. You manage them in the console under Settings → Workspace → Schema, on the Event types tab.
As with entity types, a Strict event type rejects an event that carries an attribute it does not declare, and non-strict event types accept anything. A data contract defined for the event type is checked on every incoming event. See profiles and entities.
How events arrive
- From your website or app, through the SDKs.
- From other systems, through connectors, file imports and streams.
- From your own code, through the API: the
events/addoperation accepts a batch of events. Each event is checked against its event type and any data contract, and the response lists the ids Optima gave the events. See the API reference. - From the console, with Add event on a profile.
- From Optima itself. Campaign activity is recorded as events too: a message queued, sent, delivered, opened, clicked or bounced, and a customer's response to an offer. This is how reports, caps and attribution know what happened.
Reading and correcting events
The Events screen searches the whole event stream. Filter by Event type, Profile ID and time (From and To), and add attribute conditions. Select an event to see its attributes and its change history. A profile's page also lists that profile's events, filtered by type.
As with profiles, attributes are shown according to your acting purpose, PII access level and the subject's consent, and reads are logged.
- Updating an event changes its source and attributes. Values you set are added or changed, values you clear are removed, and values you do not touch stay. A single request cannot both set and remove the same attribute.
- Deleting an event is permanent: the console asks you to confirm.
- History. Every change is recorded. The API can return an event as it was at a past moment with an
attimestamp, and the change trail of one event.
Events and profile merges
When two profiles are merged, the events of the absorbed profile move to the surviving profile. Identity resolution does not move events, because it leaves the original profiles in place and groups them. See identity.