An Event is a piece of data that indicates an action a Profile has performed — like a page view on your website, a click in an email, or completing a Marketing Automation Flow. Events are logged on Profiles automatically when they interact with your Activities, and they power your timeline view, segmentation and Marketing Automation triggers.

Find the logged Events in the 360 Profile view, or use them for segmentation and personalisation. There are many types of Events, depending on what kind of activity the Event is related to.

An Event is a piece of data that indicates an action a Profile has performed.

Events are logged onto Profiles when they perform an action related to an existing Activity — like a click in an email or a page view on your website. Events contain information about the specific action the individual behind the Profile performed, and are organised in a timeline.

You will find logged Events in the 360 Profile view, and you can use them for segmentation and personalisation.

There are many types of Events, depending on what kind of activity the Event is related to. Continue reading this article for a rundown of each type of Event.

Behind the scenes, every Event in Apsis One belongs to one of three classes. They look the same on a Profile timeline, but they behave differently when it comes to who creates them and whether you can edit them.

When you create and activate an Activity, it is saved together with its corresponding Event as a version. Any later changes made to this Activity are also saved, and a new version of the Event is created.

This applies to Forms, Surveys, Product Views and Custom Events. Read more about Event Versions →

Response Data are all the different Events that reflect a Profile's response to your communications sent via the Email Tool, SMS Tool or Marketing Automation.

These Events are shown under Profile Activity in the Response Data tab of a Profile. When you click a specific Activity, you will see a popover with more information.

All Profile interactions related to your Forms & Pages and Sign-up forms.

In the Forms & Pages tab of the Profile view you can see all Profile Events related to your Forms & Pages Tool Landing Pages.

Profiles navigated into a page where you placed a Form activity. Here are the types of data associated with this Event:

Profiles started filling in a Form activity on your website. Data associated:

Profiles submitted their information into your Form activity. If you chose to track certain fields as form response only, you will find your visitors' answers in this Event.

Profiles submitted a Form activity that was rejected. This can happen if a visitor fills in a Form where you chose to block duplicates or overwriting of existing profile data.

Possible values for rejectReason:

Profiles viewed a page where you placed a Page activity.

Points and other data profiles have earned by reaching an Achievement node in a Marketing Automation flow. Achievement Events are created and logged into profiles whenever they perform an action related to your Marketing efforts — effectively turning them into Sales, Marketing, or Product leads.

The types of Achievement Events reflect whether they're a Sales, Marketing, or Product qualified lead, and a numeric value is added to reflect the value of their interaction.

The Consent Timeline is a comprehensive timeline of a profile's channel consent (opt-in, confirmed opt-in, and opt-out) in relation to activities created in the system.

Website Interactions reflect all of the profile's browsing behaviour in your domains — a timeline containing page views, product views, and cookie consent, for example.

This data is a result of your Website Tool activities or your Manual Data Tracking setup.

There are different types of Website Interactions, depending on whether they originate from a Website tool activity or your Custom Data Tracking setup.

Custom Events allow you to track exactly the data you need, by tailoring what kind of information is collected and stored in profiles.

Learn more about Custom Events →

Use Product View – Collect Events from your Website Tool Activity to find Profiles who viewed a specific product category in the last 7 days, then email them a targeted offer.

Use the Form – Submit Event of a specific Form Activity as the Listen Node trigger in a Flow. Profiles who fill in that form are automatically enrolled in the welcome journey.

If you want to log when a booking is made, an order is created, a loyalty tier changes or any other action that is not covered by the default Events, create a Custom Event for it.

Use Achievement Events with point values to track lead quality (MQL, SQL, PQL) and feed those scores into your segmentation or CRM workflow.

More on use cases:

Form Events (View, Start) require marketing cookie consent. If a profile hasn't given cookie consent, only the Submit event is recorded. Check your cookie banner setup and verify the profile gave consent.

A few things to check:

That's expected behaviour — Apsis One keeps every version of an Event so historical data stays consistent. Pick the version that matches the time period you're targeting. Read more about Event Versions.

Achievement Events are only created when a profile completes the flow by passing through an Achievement node. Verify the flow is active, the profile actually entered the flow, and the Achievement node settings (type: MQL, SQL, PQL) are configured. Profiles only earn the achievement at the Finish node.

Website Interactions depend on (a) the Tracking Script being installed on the relevant pages and (b) the profile having given cookie consent. Profiles without cookie consent won't have website interaction data tied to them.

That's correct — activity IDs are unique identifiers (e.g. d9dda47c-6145-4a6d-96bb-63ec2c87b280). To find which activity an ID refers to, open the activity in the relevant tool and check the URL — the ID is the trailing part.

❓ A Segment using an Event stopped working after I edited the source Activity.
​

When you edit an Activity (Form, Survey, Product View) or a Custom Event, a new Event version is created. Adding fields is safe. Removing a field is technically a major change and can break Segments and Marketing Automation Flows that reference the removed field. Restore the field or update the dependent Segment / Flow to use a different field.

❓ My event-triggered Marketing Automation Flow isn't picking up new Activity submissions.
​

If the Flow combines an Event trigger with a Segment condition, and the Event version changed (because you edited the Activity), the Flow may stop processing entries. Check that the version referenced in the Segment matches the current Event version, or rebuild the Segment to reference the new version. Read more about Event Versions →

❓ I want to post Custom Events to a Profile from another system.
​

You can post Custom Events to Profiles via the Apsis One API or Zapier. You cannot create new Custom Event types through the API — they must first be created in the Data Model in Apsis One. See Post Custom Events with the Apsis One API.