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. Click on a heading on the left to jump to a specific part of this article.

profiles1_1.png

 

Here's a quick rundown of the general data categories: 

Details: All the essential information about the Profile, like their Channel Consent and their Attributes.

Tags: Tags are added manually to Profiles by APSIS One users to keep track of a certain type of visitor or customer.

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.

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.

Ecommerce Events: If you have the Expand Ecom license, these Events will reflect the Profile's Ecom-related interactions with your website. Read more about Expand Ecom...

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.

 


 

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: A text, or string, value. It has a 100-character limit. For example: female, non-binary, male.

True/False: A true or false, or boolean, attribute. For example, downloaded the app = true/false.

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, YYYY/MM/DD, DD/MM/YYYY, DD.MM.YYYY).

There are default, Ecommerce and custom attributes. Below you can read about default and Ecommerce attributes. To learn more about Custom Attributes, head over to the Admin Users section and take a look at this article.

 

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 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.
  • 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 an 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.
  • Last purchase value: The value of the last purchase the Profile made in your website.
  • Total of purchases (Coming soon...): The total of combining the value of all the purchases the Profile has made in your website so far.

 

 


 

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 on an item below to expand:

Sent

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

Delivered

An Email you've sent has been successfully delivered. Here's 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. 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 IP address of where the event originated.

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: "d9dda47c-6145-4a6d-96bb-63ec2c87b280".

device: Refers to the device the event took place.

location: The IP address of where the event originated.

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.

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.

Here's the bounceCode and bounceReason possible values, with all hard bounces in bold.

bounceCode    bounceReason

1004

Unknown

2000

General hard bounce

2001

Recipient email does not exist

2002

Domain name does not exist

2004

Closed email account

3001

Mailbox is full

3002

Recipient email server is currently too busy

3003

Email account is inactive

4000

General error

4003

Network error

4007

SPF authentication error

4008

DMARC authentication error

4009

DKIM authentication error

9999

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.

Forward

They've forwarded an Email you've sent them to another contact. 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 IP address of where the event originated.

Report Spam

They've reported an Email you've sent them as spam. Here's 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 on an item below to expand:

Sent

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

Delivered

An SMS you've sent has been successfully delivered. Here's the type of data associated with this event:

activityId: The ID for the particular activity that is considered the source of 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's 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.

reason: The reason that the profile left the flow:

  • Finished: The profile reached the Finish Node and completed the flow.
  • Match tags: The profile matched the tag specified in the Flow Settings under Terminate.
  • Over limit: The profile has entered the flow the maximum amount of times specified in the Flow Settings.
  • Missing consent: The profile has withdrawn their consent. Either they opted out or they have been deleted from Audience.
  • Reset: The profile was removed from the flow when pausing and reactivating the flow.

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

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.

 


 

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.

 


 

Ecommerce

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

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

 

Sign-Up Bar Interactions

Click on 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 website 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 to you via 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 website 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.

Email: The Email 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's 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 website 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.

 

Cookie Banner Interactions

Click on 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 website 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's 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 website 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.

 

Auto Collect Data

Click on an item below to expand:

  Did you set up Auto-Collect?

This type of events will only be displayed if you have created an Auto-Collect activity. This activity allows you to track data from integrations with Facebook ads, Google Analytics, Google SEO/SEM, and many more.

Read more about Auto-Collect...

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

category: The product category that was viewed by the profile upon browsing your website.

price: The price of a product that was viewed by the profile upon browsing your website.

image: The image URL of a product that was viewed by the profile upon browsing your website.

There is, of course, user-defined data. If you chose to collect any specific data and added it as a custom field, it will appear here.

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

 

Product Views

Click on an 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 website 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.

 

Cart Events

Click on an item below to expand:

Created - Coming soon...

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

referrer: The website 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.

Product - Coming soon...

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

referrer: The website 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.

 

Order Events

Click on an item below to expand:

Created - Coming soon...

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

referrer: The website 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.

Product - Coming soon...

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

referrer: The website 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.

 

Conversion Events

Click on an item below to expand:

Basic - Coming soon...

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

referrer: The website 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?