Data entities reference

Important

Feature availability is part of a phased rollout. Your organization may not see this functionality yet. It will become available when your environment is included in the rollout.

This page describes the data entities available through the data lake export service, including their attributes and types. Use this reference when building queries, reports, or integrations against the exported data.

Entity relationship diagram

The following diagram shows the relationships between the data lake export service data entities.

Entity relationship diagram for data lake export service data entities

Data entities reference

The following tables describe the data entities and their attributes as they appear in the exported data.

Profile

NameTypeDescriptionExample
idstringUnique identifier for the profile, system generated."123e4567-e89b-12d3-a456-426614174000"
createdAttimestampTimestamp indicating when the profile was initially created, system generated."2020-09-08T16:17:16.000Z"
modifiedAttimestampTimestamp indicating the last time the profile was updated, system generated."2020-09-08T16:17:16.000Z"
lastSeenAttimestampTimestamp indicating when the profile was last seen, system generated."2020-09-08T16:17:16.000Z"
typestringSpecifies the type of profile, which can be either identified or visitor."identified"
contactobjectContains the contact information associated with the profile.See Profile.contact
identifiersarrayCollection of identifiers associated with the profile, such as email or phone number.[ { "provider": "email", "id": "[email protected]" } ] See Profile.identifiers
clientIdsarrayList of user IDs associated with the profile."f3a9c2e4-7b8d-4c2a-9f1e-8a6d3b2c9e1a"
extensionsmapCustom guest attributes.See Profile.extensions
traitsobjectFree-form structure to hold various traits related to the profile and session.See Profile.traits
audiencesobjectInformation regarding the segments or audiences the profile belongs to.See Profile.audiences

Profile.contact

NameTypeDescriptionExample
firstNamestringThe individual's first name, which must not be empty. (1–500 characters)"John"
lastNamestringThe individual's last name. (1–500 characters)"Smith"
emailstringA valid email address format, which includes a local part, an "@" symbol, and a domain."[email protected]"
dateOfBirthdateThe date of birth formatted in ISO 8601 standard, representing the year, month, and day."1995-01-01"
genderstringThe gender of the individual. Free text is accepted, but one of the suggested values is recommended.Suggested: male | female | unknown | other (1–100 characters)
languagestringThe language code represented in ISO 639-1 format, using two uppercase letters."EN"
titlestringA title for the individual, which can be free text or one of the specified enumerated values.Suggested: "Br", "Brigadier", "Capt", "Colonel", "Dame", "Dr", "Elder", "Fr", "General", "Hon", "Judge", "Lord", "Master", "Miss", "Mr", "Mrs", "Ms", "Mstr", "Prof", "Rabbi", "Rev", "Shaikha", "Sheikh", "Sir", "Sister", "Sr" (1–100 characters)
phoneNumbersmapA structured representation of various phone numbers, including home, work, and mobile.See Profile.contact.phoneNumbers
addressobjectA structured representation of a physical location, including street, city, state, and postal code.See Profile.contact.address

Profile.contact.address

NameTypeDescriptionExample
streetstringThe street address. (1–500 characters)"12 Baker Street"
citystringThe name of the city. (1–500 characters)"Madrid"
statestringThe name of the state or region. (1–500 characters)"Colorado"
postCodestringThe postal code, formatted according to the country. (1–500 characters)"AB 123"
countrystringThe country code, required if address is present."ES"

Profile.contact.phoneNumbers

  • Recommended to use E.164 for interoperability or document your local pattern.
  • Open map, values can be set by the customer. See samples below.
NameTypeDescriptionExample
homestringHome phone number in E.164 format or can be empty."+34911222333"
workstringWork phone number in E.164 format or can be empty."+34914445566"
mobilestringMobile phone number in E.164 format or can be empty."+353861234567"

Profile.identifiers

NameTypeDescriptionExample
providerstringSpecifies the provider of where the identifier came from."email"
idstringThe actual identifier value, formatted according to the specified provider."[email protected]"

Profile.traits

NameTypeDescriptionExample
affinitiesmapSystem generated affinity score based on page view.See Profile.traits.affinities

Profile.traits.affinities

  • Stores customer-defined affinity signals in a nested map structure.
  • Group names and value names are dynamic and customer-defined. Only the leaf object has fixed schema fields.
  • First-level key = affinity group name (example: brand, category, productType). Second-level key = affinity value inside that group (example: adidas, running, shoes). Leaf object = affinityValue with fixed fields: views, score, lastViewAt.
NameTypeDescriptionExample
affinityGroupstring keyDynamic top-level affinity group.brand
affinityValueKeystring keyDynamic value key under a group.adidas
affinityValueobjectFixed leaf object for one affinity value.{ views, score, lastViewAt }
NameTypeDescriptionExample
viewsintegerNumber of views for this affinity value.25
scorenumberAffinity score for this value.0.95
lastViewAttimestampLast viewed or updated timestamp (ISO-8601 UTC)."2026-05-20T14:22:31Z"

Profile.audiences

NameTypeDescriptionExample
segmentMembershiparrayInformation regarding the segments or audiences the profile belongs to.[ "segment1", "segment2" ]

Profile.extensions

  • General-purpose extensible attributes (business-specific). Defined by customers to meet their business needs.
NameTypeDescriptionExample
attributestring, boolean, number, list, objectOne or many name/value pair attributes for custom data.[ "segment1", "segment2" ]

Session

NameTypeDescriptionExample
idstringUnique identifier for the session, system generated."123e4567-e89b-12d3-a456-426614174000"
profileIdstringUnique identifier for the profile, system generated."123e4567-e89b-12d3-a456-426614174000"
createdAttimestampTimestamp when the session was created."2026-01-08T16:17:16.000Z"
createdAtIsostringISO-8601 representation of creation timestamp. Used as data partitioning."2026-01-08"
modifiedAttimestampTimestamp when the session was last updated."2026-01-08T16:17:16.000Z"
clientIdstringUser identifier associated with the profile."123e4567-e89b-12d3-a456-426614174000"
siteIdstringSite/application identifier."SpinAir"
channelstringChannel through which the session occurred."Web"
statusstringCurrent status of the session."Closed"
languagestringThe language of the site/page being viewed. Optional parameter that can be sent and derived from the events."EN"
clientDeviceobjectDevice information.See Session.clientDevice
geolocationobjectLocation information.See Session.geolocation
utmobjectUTM attribution data.See Session.utm
statsobjectSession statistics.See Session.stats

Session.clientDevice

NameTypeDescriptionExample
typestringDevice type."mobile"
softwarestringBrowser or application name."Chrome"
softwareVersionstringBrowser/application version."125.0"
operatingSystemstringOperating system name."Android"
operatingSystemVersionstringOperating system version."14"

Session.geolocation

NameTypeDescriptionExample
citystringName of the city."Dublin"
continentstringContinent code."EU"
countrystringCountry code."IE"
regionstringRegion or state name."Leinster"

Session.utm

NameTypeDescriptionExample
sourcestringUTM source."newsletter"
mediumstringUTM medium."email"
termstringUTM term."productivity_tools"
contentstringUTM content descriptor."cta_button_top"
campaignstringUTM campaign name."july_promo"

Session.stats

NameTypeDescriptionExample
refererstringThe source from which the user arrived at the current page."google.com"
firstPagestringFirst page visited."home"
lastPagestringLast page visited."offers"
durationInSecondsintegerDuration of session in seconds.18
eventTypeCountmapEvent counts grouped by event type.See Session.stats.eventTypeCount

Session.stats.eventTypeCount

  • Values can be set by the customer. See samples below.
FieldTypeDescriptionExample
pageViewsnumberNumber of page views.5
contentClicknumberNumber of content clicks.11
searchnumberNumber of searches.2

Events

NameTypeDescriptionExample
idstringUnique identifier for the event, system generated."123e4567-e89b-12d3-a456-426614174000"
sessionIdstringUnique identifier for the session, system generated."123e4567-e89b-12d3-a456-426614174000"
createdAttimestampTimestamp when the event was created."2026-05-20T14:22:31Z"
createdAtIsostringISO-8601 representation of creation timestamp. Used as data partitioning."2026-05-20"
modifiedAttimestampTimestamp when the event was last updated."2026-05-20T14:30:00Z"
clientIdstringClient/device identifier associated with the profile."123e4567-e89b-12d3-a456-426614174000"
typestringPredefined list for Sitecore events with customer-allowed custom events."pageView", "form", "identity"
siteIdstringSite/application identifier."Sitecore"
channelstringChannel through which the session occurred."web", "mobile", "mobileApp", "offline"
namestringThe page/content associated to the event. Can be the full page name for a pageView or human readable name for content."homepage"
languagestringThe language of the site/page being viewed. Optional parameter that can be sent."en-US"
customDatamapAdditional parameters customers can add to the event for their own business needs.See Events.customData
coreobjectSitecore defined key/value pairs, determined by the eventType.See Events.core

Events.core

NameTypeDescriptionExample
pageViewobjectPage view event.See Events.pageView
formobjectForm interaction event.See Events.form
searchobjectSearch interaction event.See Events.search
identityobjectIdentity event.See Events.identity

Events.customData

  • Values can be set by the customer. See samples below.
FieldTypeDescriptionSample
attributestring, boolean, number, list, objectOne or many name/value pair attributes for custom data.{ "timeToComplete": 60, "formName": "Contact Us" }

Events.pageView

NameTypeDescriptionExample
pageVariantIdstringOptional. ID of page variant."main-page-1"
currencystringOptional. The alphabetic currency code of the currency the site visitor uses. If unset, this property will not be part of the payload."eur", "gbp", "usd"

Events.form

NameTypeDescriptionExample
formIdstringID of the form."form_123"
componentInstanceIdstringThe UUID of the component that contains the XM Cloud form. Used for A/B/n testing."ac4109f5-9831-4abef-8005-647c70bfba01"
interactionTypestringType of action."submitted", "viewed", "interacted"
NameTypeDescriptionExample
componentIdstringRequired. The unique identifier of the widget."axfd3243252454"
componentInstanceIdstringThe UUID of the component that contains the XM Cloud form. Used for A/B/n testing."ac4109f5-9831-4abef-8005-647c70bfba01"
interactionTypestringType of action."viewed", "clicked"
keywordstringThe text the site visitor entered in the search field to perform a search."athletic sneakers"
nullResultsbooleanShows if any results were returned for searched keyword.false

Events.identity

NameTypeDescriptionExample
currencystringOptional. The alphabetic currency code of the currency the site visitor uses. If unset, this property will not be part of the payload."eur", "gbp", "usd"
contactobjectContains the contact information associated with the profile.See Events.identity.contact
identifiersarrayCollection of identifiers associated with the profile, such as email or phone number.See Events.identity.identifiers

Events.identity.contact

NameTypeDescriptionExample
firstNamestringThe individual's first name, which must not be empty. (1–500 characters)"John"
lastNamestringThe individual's last name. (1–500 characters)"Smith"
emailstringA valid email address format, which includes a local part, an "@" symbol, and a domain."[email protected]"
dateOfBirthdateThe date of birth formatted in ISO 8601 standard, representing the year, month, and day."1995-01-01"
genderstringThe gender of the individual. We allow free text but suggest using one of the specified enumerated values. Suggested: male | female | unknown | other (1–100 characters)"male"
languagestringThe language code represented in ISO 639-1 format, using two uppercase letters."EN"
titlestringA title for the individual, which can be free text or one of the specified enumerated values. Suggested: "Br", "Brigadier", "Capt", "Colonel", "Dame", "Dr", "Elder", "Fr", "General", "Hon", "Judge", "Lord", "Master", "Miss", "Mr", "Mrs", "Ms", "Mstr", "Prof", "Rabbi", "Rev", "Shaikha", "Sheikh", "Sir", "Sister", "Sr" (1–100 characters)"Mr"
phoneNumbersmapA structured representation of various phone numbers, including home, work, and mobile.See Events.identity.contact.phoneNumbers
addressobjectA structured representation of a physical location, including street, city, state, and postal code.See Events.identity.contact.address

Events.identity.contact.address

NameTypeDescriptionExample
streetstringThe street address. (1–500 characters)"12 Baker Street"
citystringThe name of the city. (1–500 characters)"Madrid"
statestringThe name of the state or region. (1–500 characters)"Colorado"
postCodestringThe postal code, formatted according to the country. (1–500 characters)"AB 123"
countrystringThe country code, required if address is present."ES"

Events.identity.contact.phoneNumbers

  • Recommended to use E.164 for interoperability or document your local pattern.
  • Open map, values can be set by the customer. See samples below.
NameTypeDescriptionExample
homestringHome phone number in E.164 format or can be empty."+34911222333"
workstringWork phone number in E.164 format or can be empty."+34914445566"
mobilestringMobile phone number in E.164 format or can be empty."+353861234567"

Events.identity.identifiers

NameTypeDescriptionExample
providerstringSpecifies the provider of where the identifier came from."email"
idstringThe actual identifier value, formatted according to the specified provider."[email protected]"
If you have suggestions for improving this article, let us know!