Events is in this case not a social gathering. An Event s is a piece of data that indicates an action a Profiles has performed – like a pageview on your website, a click in an email or completing a marketing Automation Flow.

An event s is a piece of data that indicates an action a Profiles has performed.

Events are logged into Profiles when they perform an action related to an existing Activity like a click in an email or a pageview on your website. Events contain information related to the specific action the individual behind the Profile performed, and are organized in a timeline.

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.

Continue reading this article for a rundown of each type of Event.

When you create and activate an activity, it is saved, and its corresponding Event, as a version. Any changes later made to this activity are also saved, and a new version of the Event is created. Read more about Event Versions.

Jump to the type of Event you are looking for.

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

These are the Events that will be 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.

The Form Events will only be collected if the Profile has agreed to marketing cookies. If a Profile dos not give consent to marketing cookie only a submit event will be collected.

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

activityId: The ID for the particular activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain associated with the Event.

url: Refers to the specific URL associated with the Event.

domain: The domain where the Event took place.

location: The country where the Event happened in the ISO 3166-1 alpha-2 format (SE, US, for example).

type: The type of Form chosen for this specific activity.

Profiles started filling in a Form activity on your website. Here are the types of data associated with this Event:

activityId: The ID for the particular activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain associated with the Event.

url: Refers to the specific URL associated with the Event.

domain: The domain where the Event took place.

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. Here are the types of data associated with this Event:

activityId: The ID for the particular activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain associated with the Event.

url: Refers to the specific URL associated with the Event.

domain: The domain where the Event took place.

location: The country where the Event happened in the ISO 3166-1 alpha-2 format (SE, US, for example).

type: The type of Form chosen for this specific activity.

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. Here are the types of data associated with this Event:

activityId: The ID for the particular activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

address: The email address of the person associated with the Profile.

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain associated with the Event.

url: Refers to the specific URL associated with this Event.

domain: The domain where the Event took place.

location: The country where the Event happened in the ISO 3166-1 alpha-2 format (SE, US, for example).

targetId: The ID for the Folder associated with this Event.

topicId: The ID for the Subscription associated with this Event.

rejectReason: The Profile already exists in your account. The possible values correspond with how you set up your Forms & Pages activity, specifically in the Form Action step.

Reject: If you chose Block and show message.

Reject and trigger communication: If you chose Block, show message and trigger "Edit my Preferences" flow.

Rejected because CRM ID was set: If you chose Block if Profile has CRM ID.

Profiles viewed a page where you placed a Page activity. Here are the types of data associated with this Event:

activityId: The ID for the particular activity that is considered the source of the Event. To locate an activity ID, open the activity. On your browser, take a look at the URL: the ID is the series of characters at the end of the URL. For example: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

referrer: The page where the website traffic originated, or where the Profiles were before reaching the domain associated with the Event.

url: Refers to the specific URL associated with the Event.

domain: The domain where the Event took place.

location: The country where the Event happened in the ISO 3166-1 alpha-2 format (SE, US, for example).

type: The type of Form chosen for this specific activity.

Points and other data they 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--with the Marketing Automation Tool, for example--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, as additional Event data, a numeric value is added to the Event in order to reflect the value of their interaction.

Here are the types of data associated with this event:

achievementId: A unique ID for the achievement associated with the Achievement Node.

type: What type of achievement the Profile earned: MQL, SQL or PQL. The type of achievement is a part of the Achievement Node settings.

points: The abstract numeric value assigned to the Profile upon reaching the Finish node and completing the flow.

value: The numeric monetary value assigned to the Profile upon reaching the Finish node and completing the flow.

sourceType: The tool considered as the source for this Event. In this case, it's the Marketing Automation Tool (For now this is the only source creating achievements, but we'll let you know when other tools start doing it too).

sourceId: The ID for the specific activity that corresponds with the achievement.

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 behavior 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.

Website Interactions Events

These are the Events that will be shown under Website Interactions. When you click a specific interaction, you will see a tooltip with more information.

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 allows you to be able to track what kind of data you need, by tailoring what kind of information is collected and stored in Profiles. Learn more about Custom Events.

About Event Versions

Segmentation

About Attributes

About Profile Tags