Website Tool Website Interactions

These are the Events related to the Website tool that will be shown under Website Interactions.

The Event data associated with each Event allows you to create Segments in Audience to easily target Profiles in your APSIS One activities.


In this article


Sign-up Bar Events

View

They navigated into a page where you placed a Sign-up bar. 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.

Submit

They submitted their email address or mobile number via your Sign-up bar. This Event is logged into Unknown Profiles who enter their email into your Sign-up bar, and a Known Profile is then created with a Email or SMS Consent Event. Browsing data prior to the consent is kept in the Unknown Profile with this Event, until the Known and Unknown merge due to additional browsing behavior or Double Opt-in. When merged, both Events will be present in the merged Profile.

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.

address: The email address or mobile number the person associated with the Profile provided with their explicit consent.

Return Offer Click

They clicked on the CTA/button link on your Sign-up bar. 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.

offer-url: Refers to the URL associated with the Return Message CTA of the Sign-up bar they clicked.


View

They navigated into a page where you placed a cookie banner. 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.

Submit

They submitted their cookie consent via your cookie banner. This could be an APSIS One Cookie Banner or connect your own. 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.


Product Views Events

Collect

They viewed a product page upon browsing your website. This will only appear if you have completed the Website activity Product Views in Collect. 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.

name: The name of the product, according to what was mapped in the Product Views activity.

category: The product category, according to what was mapped in the Product Views activity.

Any other additional fields mapped in your Product Views activity will be collected and stored in Profiles' Product Views Events.

Did this answer your question?