Cloud SDK terminology
Glossary
This topic explains general concepts and terms used within the Cloud SDK.
- browser ID
-
The browser ID is a universally unique identifier (UUID) that Sitecore CDP assigns to every site visitor of your site. It is unique per browser, and it associates sessions and events with the respective site visitor. The Cloud SDK stores the browser ID as the value for the first-party
sc_{SitecoreEdgeContextId}cookie in the web browser. - event
-
An event is an action a site visitor performs in your app. For example, viewing a webpage, clicking a button, submitting a Sitecore form, searching for content, or any other interaction you want to track.
When an event triggers, the event with all its data is sent to Sitecore and becomes available in the various Sitecore DXP products your organization has access to. This data drives real-time, unified tracking.
- friendly ID
-
The friendly ID is a unique identifier that Sitecore Personalize assigns to every experience and experiment. Cloud SDK developers use the friendly ID to run a specific interactive experience or interactive experiment.
- guest
-
A guest is a site visitor, also known as a user of your app. Site visitors are called guests in Sitecore CDP. That's why Cloud SDK developers encounter the term guest when they use the
eventspackage, and when they log in to Sitecore CDP to find captured events. - guest ID
-
The guest ID, called guest reference in Sitecore CDP, is a universally unique identifier (UUID) that Sitecore CDP assigns to every site visitor of your site. It is unique per site visitor. The Cloud SDK
personalizepackage stores the guest ID as a first-party cookie in the web browser. - interactive personalization
-
An interactive personalization is a type of personalization (experience or experiment) created in Sitecore Personalize typically by developers, and delivered to site visitors via APIs.
An interactive experience or interactive experiment enables developers to create dynamic content by using APIs to access back-end systems for maximum server-side personalization. These personalizations are used to show offers or operational messages with personalized, dynamic content.
- module
-
Cloud SDK packages consist of
browserandservermodules. Each module contains all the functions required to set up specific Sitecore DXP capabilities. Thebrowsermodule is for setting them up on the browser side, and theservermodule is for setting them up on the server side. - package
-
The Cloud SDK consists of packages. Each package represents a set of Sitecore DXP capabilities. Cloud SDK packages consist of
browserandservermodules. - personalization
-
Personalization is the process of creating multiple variants of pages or components and then displaying those variants to different audiences depending on specific conditions. The Cloud SDK supports the personalization process by displaying the relevant content to your site visitors.
- Sitecore Cloud SDK
-
The Cloud SDK is a set of JavaScript packages. JavaScript developers use the Cloud SDK to extend web applications with Sitecore digital experience platform capabilities such as tracking and personalization.
- Sitecore digital experience platform (Sitecore DXP)
-
Sitecore DXP is a suite of SaaS-enabled Sitecore products, each offering rich digital experience capabilities such as tracking and personalization. The Cloud SDK supports the following Sitecore products:
-
SitecoreAI
-
Sitecore CDP
-
Sitecore Personalize
-
Sitecore Search
-
- tracking
-
Tracking is the process of capturing events in response to site visitors' actions.
- unified tracking
-
Unified tracking means that a single event sent from a web app becomes available in the various Sitecore DXP products your organization has access to. Developers only have to use the Cloud SDK and its single tracking implementation to send rich tracking data to Sitecore.
- web personalization
-
A web personalization is a type of personalization (experience or experiment) created in Sitecore Personalize typically by marketers.
A web experience or web experiment enables marketers to create personalized content, offers, and operational messages using web templates.
- XM Cloud Front End Application Starter Kits
-
The starter kit is a code base that’s intended to be the basis of most SitecoreAI implementations for Next.js and Angular applications. To use it, you select the foundation template option when creating a new project. It is open source, and available on GitHub. Using the starter kit ensures you get the most stable and up-to-date version of the assets, references, assemblies, and artifacts we recommend using when you start building a solution with SitecoreAI. It includes:
-
Local development workstation resources that support debugging and testing.
-
JSS and headless libraries.
-
Headless SXA reference components, written in Next.js.
-
Personalization and analytics middleware.
XM Cloud is now SitecoreAISome code examples, images, and UI labels may still use XM Cloud while engineering assets are being updated.
-
- XM Cloud personalizations
-
XM Cloud personalizations are page-level personalizations of layouts and content for different audiences, typically created by marketers. These personalizations and tests run in JSS Next.js and JSS Angular apps automatically, with no coding required.