Advanced: Profile Data

About Profile Data

Profiles are containers of data created and assigned to individuals that interact with your brand, which can either be Unknown or Known. They contain four types of data: Attributes, Events, Tags and Consent lists and Topics. All personal data, of course, has been provided with explicit consent.

In this article you will find detailed information about the data collected and stored in APSIS One Profiles in correlation with your existing APSIS One activities. 

Continue reading this article to learn more about Profile data, or click an item on the left navigation to jump to a specific section.

profilesNew1.jpg

 


 

Attributes

Attributes are the containers of essential Profile information belonging to an individual that has interacted with your brand, like a name, location, phone number, Email address, customer status, etc. Once Attributes have been added to a Profile, they can be used for segmentation and personalisation purposes (e.g. a segment containing Profiles of only those who live in Australia; an SMS including the value of an Attribute: "Hi ##firstname##" = "Hi Anita!").

As to their properties, Attributes have a name, type and a value.

The name of the Attribute determines (or should determine, in the case of custom Attributes) which type of data will be collected (firstname, birth date, mobile).

The value of the Attribute is the actual data associated with the Profile, tracked as an Attribute (Maria, 0793477765, etc.).

Finally, the type of the Attribute determines the shape or form of the data (text, date, number).

These are the five types of Attributes you can choose to track with APSIS One:

Text: UTF-8 encoded text (string) value with a 1000-character limit. For example: Female, Non-binary, Male.

True/False: A boolean Attribute. For example, downloaded the app = true. The supported values are: true or false (lower case).

Number: A field for numbers, like an age or a phone number.

Number w/decimals: Same as the number field, yet this one has the ability to track numbers with decimals. Like a person's height.

Date: A date of birth, for example. The date format currently supported is ISO-8601 (YYYY-MM-DD).

There are default, Ecommerce and custom Attributes. Below you can read about default and Ecommerce Attributes. Custom Attributes are created in order to track and store additional Profile data according to your personalised setup. To learn how to create a custom Attribute, head over here.

 

Default Attributes

The Attributes that APSIS One tracks by default are the following:

  • First name: The first name or names of the person associated with the Profile.
  • Last name: The last name or names of the person associated with the Profile.
  • Email: The email address the person associated with the Profile provided with their explicit consent.
  • Mobile: The phone number the person associated with the Profile provided with their explicit consent. Phone numbers must contain no spaces or zeros at the start. The country code is mandatory. Follow the MSISDN format, for example: 46793699558.
  • Birth date: The date of birth of the person associated with the Profile. The date format for birth dates currently supported is ISO-8601 (YYYY-MM-DD).
  • CRM-ID: The customer ID associated with the Profile. It is exclusively created and managed internally.

 

Ecommerce Attributes

Ecommerce Attributes are a part of the Expand Ecom package for APSIS One. Read more about Expand Ecom...

  • Last purchase date: The date the Profile last made a purchase in your website.
  • Accumulated revenue (Coming soon...): The amount of revenue the Profile has brought to your business so far, or the total value (money) of all purchases the Profile made in your website.
  • Last purchase value: The value of the last purchase the Profile made in your website.
  • Total of purchases (Coming soon...): The number of times the Profile made a purchase in your website.

 


 

Events

Events are logged into your APSIS One Profiles when they perform an action related to an existing APSIS One activity. Continue reading this article to learn more about each type of Profile Events, or click a link below to jump there:

Response Data Events: Here you can find all the information about a Profile's response to your communications, sent via the Email or SMS tool. Opens, Clicks, and even Bounces.

Forms & Pages Events: All Profile interactions related to your Forms & Pages Landing pages, Sign-up forms, Pop ups and more.

Achievement Events: 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 a positive 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.

Consent Timeline: A comprehensive timeline of a Profile's channel consent (opt-in, confirmed opt-in and opt-out) in relation to your APSIS One activities.

Ecommerce Events: All Ecommerce-related Events, like those associated with the Ecom Add-on, and APSIS One integrations Profile data.

Website Interaction Events: 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.

 


 

Response Data

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.

Response.jpg

 

Email Tool Events

Click an item below to expand:

Sent

You've sent them an Email. 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".

Delivered

An Email you've sent has been successfully delivered. Here are the type 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".

Opened

They opened an Email you've sent them. Email clients will identify an opened email when the images in the email load. So, if a Profile receives and opens an email from an email client that does not load the images initially, APSIS One may not receive the data about the Profile having opened that email. If they clicked the email, however, that Event will be logged as long as the link is tracked. 

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

device: Refers to the device the Event took place.

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

Click

They've clicked a link on an Email you've sent them. 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: "d9dd666c-666-4a6d-666b-63ec2666b280".

device: Refers to the device the Event took place.

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

id: Refers to the id of the link in the content associated with the Event.

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

All URLs from links inserted into emails contain a unique link ID at the end. When using the Segment Builder to target all Profiles that clicked a link in your email, make sure to set up your condition to contain the original URL. For example: "Email - Click: url contains https://heartland.com/accessories/sunglasses".

title: The title of the link associated with the Event.

Bounced

An Email you've sent them wasn't delivered, it bounced. 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".

bounceCode: The code associated with the bounceReason.

bounceReason: The occurrence, associated with the Email client or provider, that caused the Email to bounce.

All Email Reports contain information about the delivery details of your email sending. To see which Profiles bounced and their corresponding bounce code and reason, export the Bounces section of the Email Report. Read more about Email Reports....

Here are the possible values for bounceCode and bounceReason, with all hard bounces in bold.

bounceCode    bounceReason

1004

Other - Unknown

2000

Hard - General hard bounce

2001

Hard - Recipient email does not exist

2002

Hard - Domain name does not exist

2004

Hard - Closed email account

3001

Soft - Mailbox is full

3002

Soft - Recipient email server is currently too busy

3003

Soft - Email account is inactive

4000

Technical - General error

4003

Technical - Network error

4007

Technical - SPF authentication error

4008

Technical - DMARC authentication error

4009

Technical - DKIM authentication error

9999

Soft - Unknown

 

Unsubscribe

They've decided to unsubscribe from your communications, through the unsubscribe link in an Email you've sent. 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".

topicIds: The ID for the Topics that the Profile unsubscribed from.

Report Spam

They've reported an Email you've sent them as spam. 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".

topicIds: The ID for the Topics that the Profile unsubscribed from.

targetId: The ID for the Consent list that is associated with the Event.

 

SMS Tool Events

Click an item below to expand:

Sent

You've sent them an SMS. 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".

Delivered

An SMS you've sent has been successfully delivered. 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.

Click

They've clicked a link on an SMS message you've sent them. 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: "d9dd666c-666-4a6d-666b-63ec2666b280".

device: Refers to the device the Event took place. For SMS messages, the value is usually mobile.

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

id: Refers to the id of the link in the content associated with the Event.

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

All URLs from links inserted into SMS messages contain a unique link ID at the end. When using the Segment Builder to target all Profiles that clicked a link in your SMS message, make sure to set up your condition to contain the original URL. For example: "SMS - Click: url contains https://heartland.com/accessories/sunglasses".

title: The title of the link associated with the Event.

Bounced

An SMS you've sent them wasn't delivered, it bounced. 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".

bounceReason: The occurrence, associated with the mobile number, phone carrier, etc., that caused the SMS to bounce.

Unsubscribe

They've decided to unsubscribe from your communications, through the unsubscribe link in an SMS you've sent. 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".

maFlowId: The name of the tool that initiated the activity.

Topic: The ID for the Topic that is correlated with the Event.

 

Marketing Automation Tool Events

Click an item below to expand: 

Enter Flow

The Profile entered a Marketing Automation flow. 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".

dstNodeId: Refers to the ID of the destination node, or the ID of the specific node that the Profile moved onto. In this case, the ID corresponds with the node that follows the Listen Node in this particular flow.

Move Profile

The Profile moved, in a Marketing Automation flow, from one node to another. 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".

srcNodeId: Refers to the ID of the source node, or the ID of the specific node that the Profile moved from.

dstNodeId: Refers to the ID of the destination node, or the ID of the specific node that the Profile moved onto.

Exit Flow

The Profile left the Marketing Automation flow. 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".

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

srcNodeId: The ID of the specific node that the Profile left the flow on.

reason: The reason the Profile left the Marketing Automation Flow. A string (text) value.

Read about the possible values below:

Reason Description
Finished The Profile reached the Finish Node and completed the flow. 
MatchTags The Profile matched the Tag specified in the Flow Settings under Terminate. 
OverLimit

The Profile has entered the flow the maximum amount of times specified in the Flow Settings.

CheckedProfile The Profile didn't pass a Check Profile node, and the path for those who don't match was the final node of the flow, where they left.
Reset The Profile was removed from the flow when pausing and reactivating the flow.
NodeDeleted The Profile was in a node that was deleted, and left the flow.
MissingConsent The Profile is missing consent for the node's given channel.
TooManyHardBounces The Profiles email address bounced enough times to reach the bounce limit. Read more about bounces here.
MissingEmail The Profile does not contain an email Attribute, necessary for the email node. 
MissingSMS The Profile does not contain an SMS Attribute, necessary for the SMS node. 
ProfileNotRetrieved Technical error that prevented the Profile from being found by an email node. Please contact support. 
ProfileLocked The Profile was locked in Audience. 
AttributeNotFound The Profile does not contain the Attribute necessary to complete the email node. 
AttributeValueNotFound The Profile does not contain the Attribute Value necessary to complete the email node. 
UnknownReason Unknown reason. Please contact support. 
WebhookError The Webhook node returned an error, resulting from a failed request.
InsufficientCredits Your APSIS One account does not contain enough SMS credits, so the Profile left the flow in the SMS node.
Bounce The Profile's email address or mobile number bounced in the Email or SMS node. 
Timeout The Profile didn't perform an action specified by the Wait for Event node, and the path for those who don't act in time was the final node of the flow, where they left.

 

Third Party Events

Whenever an email is sent through the Marketing Automation Tool, the Events are then part of the Email tool domain. Check the Email tool Events for more information.

 


 

Forms & Pages

Coming soon...

In the Forms & Pages tab of the Profile view you can see all Profile Events related to your Forms & Pages tool Landing pages, Sign-up forms, Pop ups and more.

Click an item below to expand:

View

They navigated into a page where you placed a Forms & Pages tool 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.

Started

They started filling in a Forms & Pages tool 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.

Submit

They submitted their information into your Forms & Pages tool 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.

Any other additional fields mapped in your Forms & Pages activity will be collected and stored in Profiles' Forms & Pages Response Data Events.

Reject

They submitted a Forms & Pages tool activity that was rejected. 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 Consent list associated with this Event.

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

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

These are the possible values for rejectReason:

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.

 


 

Achievements

When a Profile earns an achievement set by an Achievement Node in a Marketing Automation flow or the APSIS One API, the achievement, points and monetary value will be displayed here.

Achiev.jpg

 

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.

 


 

Consent Timeline

In the Consent timeline tab of the Profile view you can see a comprehensive timeline of a Profile's channel consent (opt-in, confirmed opt-in and opt-out) in relation to your APSIS One activities.

Individuals can provide and withdraw different types of consent, in various levels.

Profiles' consent can be generally divided in two different statuses, and this is often enough to understand whether a Profile will or will not receive your communications:

  • Opt-in: Subscribed, provided consent.
  • Opt-out: Unsubscribed, withdrawn consent.

However, there are different types of consent, and this is most relevant to you when enabling Double Opt-in! For a deeper look into the types of consent, head over to Advanced: About Consent.

consentTimeline2.jpg

 

Website Tool: Sign-up Bar Consent

Click an item below to expand:

Email Consent

They provided their email consent (opt-in) via a Sign-up bar. The Sign-up bar - Submit is logged into Unknown Profiles who enter their email into your Sign-up bar, and a Known Profile is then created with an Email Consent Event. Browsing data prior to the consent is kept in the Unknown Profile with the Submit Event, until the Known and Unknown merge due to additional browsing behaviour 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 Sign-up bar 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 where the Sign-up bar was placed.

url: The URL where the visitor filled in the Sign-up bar.

domain: The domain where the Sign-up bar was placed.

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

address: The Email the person associated with the Profile provided with their explicit consent.

topicIds: The ID for the Topics that the Profile unsubscribed from.

targetId: The ID for the Consent list that is associated with the Event.

SMS Consent

They provided their SMS consent (opt-in) via a Sign-up bar. They provided their SMS consent (opt-in) via a Sign-up bar. The Sign-up bar - Submit is logged into Unknown Profiles who enter their mobile number into your Sign-up bar, and a Known Profile is then created with an SMS Consent Event. Browsing data prior to the consent is kept in the Unknown Profile with the Submit Event, until the Known and Unknown merge due to additional browsing behaviour 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:

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

source: The ID for the particular Sign-up bar 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".

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

topicIds: The ID for the Topics that the Profile unsubscribed from.

targetId: The ID for the Consent list that is associated with the Event.

   

APSIS Pro: Email Consent

Click an item below to expand:

Email Consent

This Event happens when a visitor submits their consent to email communications related to APSIS Pro. The Migration Wizard creates or updates an APSIS One Profile with Topic consent in your APSIS One account. This Event will only be created in APSIS One Profile if you have an active migration.

Here are the types of data associated with this Event:

mailinglist: The unique ID of the APSIS Pro mailing list.

address: The email address of the person associated with the Profile provided with their explicit consent. 

targetId: The ID for the Consent list that is associated with the Event.

topicId: The ID for the Topic that the Profile subscribed to. 

 


 

Ecommerce

Ecommerce Events are those that are related to your APSIS One integrations, as well as a part of the Ecom add-on for APSIS One. Here's where you can read more about Integrations Profile data.

Cart abandoned

The Profile added one or more items to their cart on your website and then became inactive for at least 60 minutes.

Here are the types of data associated with this Event:

websiteId: The unique ID of the website where the Event occurred.

sessionId: The ID for the visitor's active browsing session where the Event occurred.

cartId: The ID that identifies the shopping cart related to the Event on your website.

currency: The three-letter currency code for the currency the product price is displayed with, in ISO 4217 format.

totalValue: The number with decimals that reflects the price or total amount of the items left in the cart.

url: The URL for the cart that was abandoned.

Product viewed

The Profile viewed or opened a page for one of the products in your website.

Here are the types of data associated with this Event:

websiteId: The unique ID of the website where the Event occurred.

sessionId: The ID for the visitor's active browsing session where the Event occurred.

cartId: The ID that identifies the shopping cart related to the Event on your website.

sku: The SKU of the product viewed.

name: The name of the product viewed.

group: The group the product related to the Event belongs to.

category: The category path that corresponds to the product. For example: shoes/sport/running.

size: If the product comes in different sizes, the size of the product related to the Event.

thumbnail: The URL of the image used as a thumbnail for the product related to this Event.

unitPrice: Product price per unit.

currency: The three-letter currency code for the currency the product price is displayed with, in ISO 4217 format.

stock: The number of units of the product in stock.

Browse abandonment

The Profile browsed your website and became inactive for at least 60 minutes.

Here are the types of data associated with this Event:

websiteId: The unique ID of the website where the Event occurred.

sessionId: The ID for the visitor's active browsing session where the Event occurred.

cartId: The ID that identifies the shopping cart related to the Event on your website.

Product purchased

The Profile completed a purchase in your website for one or more products. This Event is logged per product purchased; if their cart contained multiple products, the Event will be logged once per every product.

Here are the types of data associated with this Event:

websiteId: The unique ID of the website where the Event occurred.

sessionId: The ID for the visitor's active browsing session where the Event occurred.

cartId: The ID that identifies the shopping cart related to the Event on your website.

orderId: The ID of the order placed in your website.

sku: The SKU of the product purchased.

name: The name of the product purchased.

group: The group the product related to the Event belongs to.

category: The category path that corresponds to the product. For example: shoes/sport/running.

size: If the product comes in different sizes, the size of the product related to the Event.

thumbnail: The URL of the image used as a thumbnail for the product related to this Event.

unitPrice: Product price per unit.

currency: The three-letter currency code for the currency the customer paid with, in ISO 4217 format.

stock: The number of units of the product in stock.

quantity: A number that reflects the quantity ordered by the customer.

totalValue: The number with decimals that reflects the price or total amount of the items left in the cart.

Product carted

The Profile added an item to their shopping cart in your website. This Event is logged per product carted; if they add multiple products to their cart, the Event will be logged once per every product.

Here are the types of data associated with this Event:

websiteId: The unique ID of the website where the Event occurred.

sessionId: The ID for the visitor's active browsing session where the Event occurred.

cartId: The ID that identifies the shopping cart related to the Event on your website.

orderId: The ID of the order placed in your website.

sku: The SKU of the product carted.

name: The name of the product carted.

group: The group the product related to the Event belongs to.

category: The category path that corresponds to the product. For example: shoes/sport/running.

size: If the product comes in different sizes, the size of the product related to the Event.

thumbnail: The URL of the image used as a thumbnail for the product related to this Event.

unitPrice: Product price per unit.

currency: The three-letter currency code for the currency the product price is displayed with, in ISO 4217 format.

stock: The number of units of the product in stock.

quantity: A number that reflects the quantity ordered by the customer.

totalValue: The number with decimals that reflects the price or total amount of the items left in the cart.

Cart purchased

The Profile completed a purchase in your website. This Event is logged once per cart. For an Event that describes the products in the cart, see Product purchased Event.

Here are the types of data associated with this Event:

websiteId: The unique ID of the website where the Event occurred.

sessionId: The ID for the visitor's active browsing session where the Event occurred.

cartId: The ID that identifies the shopping cart related to the Event on your website.

orderId: The ID of the order placed in your website.

currency: The three-letter currency code for the currency the customer paid with, in ISO 4217 format.

totalValue: The number with decimals that reflects the price or total amount of the items left in the cart.

 


 

Website Interactions

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.

WebsiteInt.jpg

 

 

Domain Tracking

Coming soon...

  Did you set up Tracking in your domain?

This type of Events will only be displayed if you have set up Tracking in your domain. It allows you to track basic browsing behaviour from your website's visitors as well as data from integrations with Facebook ads, Google Analytics, Google SEO/SEM, and many more.

Click an item below to expand:

Google Analytics

These interactions are fed into APSIS One if you use UTM parameters to track interactions with Google Analytics. If the APSIS One Tracking Script identifies a page load with any of the supported UTM parameters, it will enrich the Profile with a Google Analytics Event. For example: http://www.example.com/?utm_source=exampleblog&utm_medium=referral&utm_campaign=summer-sale

Here are the types of data associated with this Event:

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.

utmcampaign: Corresponds with a Google Analytics parameter. This one refers to the text used to identify a particular campaign.

utmcontent: Corresponds with a Google Analytics parameter. Useful to differentiate similar content or links within the same Email.

utmmedium: Corresponds with a Google Analytics parameter. Refers to the communication medium used to display the content, like whether it's an Email newsletter, a banner, etc.

utmsource: Corresponds with a Google Analytics parameter. Identifies the origin on the website interaction, if it was visited by clicking on a website, via a Google search, etc.

utmterm: Corresponds with a Google Analytics parameter. In the case of the campaigns being Tagged with certain keywords, this parameter allows you to specify the keyword.

Google SEO/SEM

These interactions are fed into APSIS One if you have a Google SEO/SEM integration. If the APSIS One Tracking Script identifies that a visitor has arrived to the website from a google domain. They can be from a paid source, identified with a Google Click ID (GCLID) parameter in the URL, or an organic source.

Here are the types of data associated with this Event:

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.

type: Corresponds with Google SEO/SEM. Determines whether the traffic comes from a paid (GCLID parameter in the URL) or an organic source.

Page view

They viewed or browsed a page in your website. Note that all this data is fed to APSIS One as it is mapped in your website's code. Here are types of data associated with this Event:

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.

title: The name of the product viewed by the Profile upon browsing your website.

File download

They downloaded a file from your website. This is detected when the link contains a file extension (like .PDF, .EPUB, .ZIP...) or a "download" parameter. Here are the types of data associated with this Event:

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.

link: A link to the file that was downloaded.

title: Title of the file's link.

Site search

They performed a search in your website. This Event is picked up by the URL's search key, which you entered when setting up Tracking for your domain.

Here are the types of data associated with this Event:

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.

term: The search term used by the Profile.

Facebook Ad Referral

They reached your website from a Facebook ad, with a Facebook Click ID (FBCLID) parameter that is automatically added by Facebook when linking to your website. For example: http://www.site.com?fbclid=juihd8239732buibiee32809jeee2i90. Here are the types of data associated with this Event:

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.

term: The search term used by the Profile.

type: (Coming soon...)

 

Website Tool: Sign-up Bar Interactions

Click an item below to expand:

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

 

Website Tool: Cookie Banner Interactions

Click an item below to expand:

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

 

Website Tool: Auto Collect Data

Click an item below to expand:

Google Analytics

These interactions are fed into APSIS One if you use UTM parameters to track interactions with Google Analytics. If the APSIS One Tracking Script identifies a page load with any of the supported UTM parameters, it will enrich the Profile with a Google Analytics Event. For example: http://www.example.com/?utm_source=exampleblog&utm_medium=referral&utm_campaign=summer-sale

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.

utmcampaign: Corresponds with a Google Analytics parameter. This one refers to the text used to identify a particular campaign.

utmcontent: Corresponds with a Google Analytics parameter. Useful to differentiate similar content or links within the same Email.

utmmedium: Corresponds with a Google Analytics parameter. Refers to the communication medium used to display the content, like whether it's an Email newsletter, a banner, etc.

utmsource: Corresponds with a Google Analytics parameter. Identifies the origin on the website interaction, if it was visited by clicking on a website, via a Google search, etc.

utmterm: Corresponds with a Google Analytics parameter. In the case of the campaigns being Tagged with certain keywords, this parameter allows you to specify the keyword.

Google SEO/SEM

These interactions are fed into APSIS One if you have a Google SEO/SEM integration. If the APSIS One Tracking Script identifies that a visitor has arrived to the website from a google domain. They can be from a paid source, identified with a Google Click ID (GCLID) parameter in the URL, or an organic source.

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.

type: Corresponds with Google SEO/SEM. Determines whether the traffic comes from a paid (GCLID parameter in the URL) or an organic source.

Page view

They viewed or browsed a page in your website. Note that all this data is fed to APSIS One as it is mapped in your website's code. Here are 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.

title: The name of the product viewed by the Profile upon browsing your website.

File download

They downloaded a file from your website. This is detected when the link contains a file extension (like .PDF, .EPUB, .ZIP...) or a "download" parameter. 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.

link: A link to the file that was downloaded.

title: Title of the file's link.

Site search

They performed a search in your website. This Event is picked up by the URL's search key, which you entered in your Auto-Collect activity. Read more about data sources...

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.

term: The search term used by the Profile.

Facebook Ad Referral

They reached your website from a Facebook ad, with a Facebook Click ID (FBCLID) parameter that is automatically added by Facebook when linking to your website. For example: http://www.site.com?fbclid=juihd8239732buibiee32809jeee2i90. 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.

term: The search term used by the Profile.

type: (Coming soon...)

 

Website Tool: Product Views

Click the item below to expand:

Product Views Data

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.

 

Website Tool: Cart Events (Available via code snippet)

This Event can only be tracked after manually installing a code snippet in your website. We aim to release Website Tool activities that will simplify the collection of these Events for all kinds of APSIS One users. However, you can find what is possible already today in terms of additional data collection under Advanced: Manual Data Tracking in this article.

Click an item below to expand:

Cart - Created

The visitor added one or more items to their cart on your website, creating a cart in your online shop.

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.

cartId: The ID of the cart created in your website.

createdAt: The date the cart was created. Date format ISO-8601.

websiteName: The name of the website where the cart was created.

storeName: The name of the store where the cart was created.

Cart - Product

A visitor added a product to their cart on your website's online shop.

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.

productId: The ID of the product carted.

sku: The SKU of the product carted.

name: The name of the product carted.

productUrl: The URL where the product is hosted on your website.

productImageUrl: The URL of the image that corresponds with the product carted.

qtyOrdered: A number with decimals that reflects the quantity carted by the customer.

priceAmount: Product price per unit.

rowTotalAmount: If the customer carted more than one piece of this product, the total price for all pieces of the product carted.

 

Website Tool: Order Events (Available via code snippet)

This Event can only be tracked after manually installing a code snippet in your website. We aim to release Website Tool activities that will simplify the collection of these Events for all kinds of APSIS One users. However, you can find what is possible already today in terms of additional data collection under Advanced: Manual Data Tracking in this article.

Click an item below to expand:

Order - Created

The visitor completed an order in your website's online shop.

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.

orderId: The ID of the order placed in your website.

customerId: The ID given to the customer that placed the order. If it's a guest visitor or an Unknown Profile, the value will be 0.

isGuest: Whether the visitor's Profile is a guest visitor or not, a True or False value.

createdAt: The date the order was created. Date format ISO-8601.

websiteName: The name of the website where the order was placed.

storeName: The name of the store where the order was placed.

grandTotalAmount: The number with decimals that reflects the total amount of the purchase.

shippingAmount: What the customer paid for shipping and handling costs, a number with decimals.

discountAmount: The amount saved by the customer after applying any discounts, a number with decimals.

shippingMethodName: The shipping and handling method chosen by the customer.

paymentMethodName: The payment method used by the customer to complete their order.

itemsCount: The number of products included in their order.

currencyCode: The three-letter currency code for the currency the customer paid with, in ISO 4217 format.

Order - Product

The visitor ordered a product from your website's online shop.

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.

orderId: The ID of the order placed in your website.

productId: The ID of the product purchased.

sku: The SKU of the product purchased.

name: The name of the product.

productUrl: The URL where the product is hosted on your website.

productImageUrl: The URL of the image that corresponds with the product purchased.

qtyOrdered: A number with decimals that reflects the quantity ordered by the customer.

priceAmount: Product price per unit.

rowTotalAmount: If the customer purchased more than one piece of this product, the total price for all pieces of the product purchased.

 

Website Tool: Conversion Events (Available via code snippet)

This Event can only be tracked after manually installing a code snippet in your website. We aim to release Website Tool activities that will simplify the collection of these Events for all kinds of APSIS One users. However, you can find what is possible already today in terms of additional data collection under Advanced: Manual Data Tracking in this article.

Click an item below to expand:

Conversion - Basic

A visitor in your website has been successfully become a customer or lead.

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.

EventCategory: Typically, the object or product that the visitor interacted with in order to cause the conversion.

EventAction: The type of interaction the visitor performed.

EventLabel: Added manually, useful for categorising conversion Events.

EventValue: A numeric value associated with the Event.

 


 

Profile Tags

Tags are internal markers that can be manually applied to Profiles. They can be created from your account settings.

Profiles34.jpg

 

To read more about how to create Tags from your account settings, go to this article. Only Admin Users may access the account settings.

These are the main differences between Attributes and Tags:

  • Tags, themselves, do not contain data. Attributes can be understood as being something like "type of data = data" (gender = female) while Tags are more like "Label = yes / no" (either Tag is applied or it isn't).
  • Profile Tags are applied manually. Attributes, on the contrary, gather the data automatically and feed it into the Profile. In order for a Profile to have a Tag, a user must apply the Tag. Alternatively, if a file containing Profile data is uploaded, they can be Tagged in advance.
  • Tags are internal and the relevance of a Tag depends on its creator. Attributes reflect the reality of the data in the Profiles, while Tags don't have to. For example, if a user imports Profiles with the File Import Wizard and Tags them as "Special Import 19", then it will be possible to filter the recipients of an email send-out to make sure only those Profiles Tagged receive the email.

 

Was this article helpful?