Actions data points

Action events can include a variety of data points, grouped into user sessions. Each session may track multiple events, and certain data points may appear multiple times within a session. While most event data is optional, some key data points are automatically included with every event.

Some data is populated on events automatically; please see the reference below for details. In most cases, the generated data will be added to all session events automatically.

Automatically generated data can still be overridden through the analytics API when submitting events.

Using data points in queries

Both generated and customer-assigned data fields can be referenced in queries. Natural language processing allows to both callout fields by their system name (BrowserName) as well as their fluent equivalents (what is the most common browser and version?)

Data reference

Session dimensions

Data point

Source

Description

SessionId

Generated automatically

Unique session ID.

Automatically added to all events within the session.

ProjectId

Customer-assigned

Populated from URL

Allows customers to assign a related project ID to events.

Cohort

Customer-assigned

Populated from URL

Typically used in A/B testing scenarios to identify the relevant user group

Time dimensions

Data point	Source	Description
Created	Generated automatically	Timestamp when the event was created
Year	Generated automatically	Year when the event was created
Month	Generated automatically	Month when the event was created
Day	Generated automatically	Day when the event was created
Hour	Generated automatically	Hour when the event was created

Channel dimensions

Data point	Source	Description
SitesCodes	Generated automatically	A comma-separated list of site codes for which the configurator was loaded.
SiteCode1	Generated automatically	The first site code from the `SitesCodes` list
SiteCode2	Generated automatically	The second site code from the `SiteCodes` list
Locales	Generated automatically	A locale for which the configurator was loaded, in ISO code format (`en-US`)
Region	Customer-assigned Populated from URL	Allows customers to group configurator users by a region where sites codes or locales do not provide the necessary aggregation level. Consider EU, for example. `SiteCodes` may identify the e-commerce channel (`SFCC` for Salesforce Commerce Cloud), while a locale may indicate a country and language (`fr-FR`). It may be desired to group all EU users together for analytics tracking purposes however by setting the `Region` variable to `EMEA` (or another customer-defined value)

Browser dimensions

Data point	Source	Description
BrowserMobile	Generated automatically	Indicates whether the user’s browser is a mobile device.
BrowserName	Generated automatically	Browser family name.
BrowserVersion	Generated automatically	Browser version
BrowserWidth	Generated automatically	If enabled, contains the user’s browser width descriptor, reduced to a breakpoint. See reference for more details.
BrowserHeight	Generated automatically	If enabled, contains the user’s browser height descriptor, reduced to a breakpoint. See reference for more details.

Customization dimensions

Data point

Source

Description

Placement

Generated automatically when selecting a component

Updated placement code.

Component

Generated automatically when selecting a component

Selected component code. For standard events, this is a placement independent code.

Order dimensions

Data point	Source	Description
Recipe	Generated automatically when saving a design	Associated recipe ID
OrderNumber	Customer-assigned	Associated order number.
LineId	Customer-assigned	Line item ID within the order.
Quantity	Customer-assigned	Number of custom products within the line item.

User experience dimensions

Data point	Source	Description
Page	Customer-assigned Populated from URL	Source page identifier.
Screen	Customer-assigned	Screen identifier.
Step	Customer-assigned	Step identifier. For example, a navigation step within the customer’s experience
Button	Customer-assigned	Button or CTA ID.

Generic event dimensions

Generic event dimensions allow customers to track arbitrary data. It is advised however to use specific event dimensions, if available, in order to increase performance and efficiency.

Data point	Source	Description
Category	Customer-assigned	Event category.
Action	Customer-assigned	Event action.
Label	Customer-assigned	Event label.
Value	Customer-assigned	Event value.