Close Menu
    DevStackTipsDevStackTips
    • Home
    • News & Updates
      1. Tech & Work
      2. View All

      10 Top Node.js Development Companies for Enterprise-Scale Projects (2025-2026 Ranked & Reviewed)

      July 4, 2025

      12 Must-Know Cost Factors When Hiring Node.js Developers for Your Enterprise

      July 4, 2025

      Mirantis reveals Lens Prism, an AI copilot for operating Kubernetes clusters

      July 3, 2025

      Avoid these common platform engineering mistakes

      July 3, 2025

      Microsoft Gaming studios head Matt Booty says “overall portfolio strategy is unchanged” — with more than 40 games in production

      July 3, 2025

      Capcom reports that its Steam game sales have risen massively — despite flagship titles like Monster Hunter Wilds receiving profuse backlash from PC players

      July 3, 2025

      Cloudflare is fighting to safeguard “the future of the web itself” — standing directly in the way of leading AI firms

      July 3, 2025

      Microsoft reportedly lacks the know-how to fully leverage OpenAI’s tech — despite holding IP rights

      July 3, 2025
    • Development
      1. Algorithms & Data Structures
      2. Artificial Intelligence
      3. Back-End Development
      4. Databases
      5. Front-End Development
      6. Libraries & Frameworks
      7. Machine Learning
      8. Security
      9. Software Engineering
      10. Tools & IDEs
      11. Web Design
      12. Web Development
      13. Web Security
      14. Programming Languages
        • PHP
        • JavaScript
      Featured

      Laravel in the First Half of 2025

      July 4, 2025
      Recent

      Laravel in the First Half of 2025

      July 4, 2025

      PHP 8.5.0 Alpha 1 available for testing

      July 3, 2025

      Recording cross browser compatible media

      July 3, 2025
    • Operating Systems
      1. Windows
      2. Linux
      3. macOS
      Featured

      GOnnect – easy to use VoIP client

      July 4, 2025
      Recent

      GOnnect – easy to use VoIP client

      July 4, 2025

      Gnuinos – spin of Devuan Linux

      July 4, 2025

      5 Best Free and Open Source Backend Electronic Circuit Simulators

      July 4, 2025
    • Learning Resources
      • Books
      • Cheatsheets
      • Tutorials & Guides
    Home»Development»Getting Started with Personalization in Sitecore XM Cloud: Enable, Extend, and Execute

    Getting Started with Personalization in Sitecore XM Cloud: Enable, Extend, and Execute

    May 20, 2025

     

    In my previous blog – Personalization in Sitecore XM Cloud: What’s New, What’s Different, and What It’s Built On!, I explored what makes personalization in Sitecore XM Cloud so powerful – from its cloud-native infrastructure and headless architecture to the built-in rule-based targeting engine. Now, I’m shifting from concepts to implementation. In this post, I’ll walk you through how to enable personalization using analytics identifiers that track and categorize visitor behavior in real time. Then, I’ll show how to use Page Builder to create audience-specific page variants, and personalize components – all with a few clicks, not code.

    In Sitecore XM Cloud, personalization happens primarily at the page level. The process revolves around creating page variants and personalizing components. This functionality is fully integrated into Page Builder, allowing you to define variations of the page based on different personalization criteria.

    Key Points:

    • Personalization is configured directly within Page Builder on a per-page basis.
    • You can create page variants – each tailored to specific audiences or conditions.
      • Individual components on the page can be personalized : swapped, hidden and can be edited to show different content
    • All of this is managed via the Personalize tab available on the page within Page Builder.

    How to Check if Personalization is Enabled:

    To determine whether personalization is set up:

    • Go to the Page Builder for the desired page.
    • Click on the Personalize tab.

    Personalization Notenabled

     

    If personalization is not enabled, you will see :

    • No variant options available.
    • A prompt or empty state indicating no personalization rules are define.

     

    Personalization Enabled

    If personalization is enabled, you’ll see:

    • Variants listed based on configured rules.
    • Options to add/edit rules and personalize individual components.

     

     

    Adding Analytics Identifiers to Enable Personalization

    Analytics identifiers are essential for enabling personalization in Sitecore XM Cloud. They help track visitors, manage sessions, and unify data across sites for a complete view of user behavior. Without them, personalization rules and targeted content delivery won’t function. Assigning the same identifier to multiple sites allows for consolidated analytics, providing a holistic view of user engagement across different sites.

    Step 1: Access Site Settings

    1. Navigate to the XM Cloud Portal: Log in to your XM Cloud environment.
    2. Open the Sites Dashboard: In the top navigation bar, click on Sites to view all your sites.
    3. Select the Desired Site: Locate the site you wish to configure. Click on the Actions menu (three dots) associated with that site and select Settings.
    4. Select the Site hosts: Browse through the options on the left side and select Site hosts option and then select the desired host

    Personalization Site Hosts

    Step 2: Add or Assign an Analytics Identifier

    1. Navigate to the Analytics and Personalization Tab: Within the site settings, click on the Analytics and Personalization tab.
    2. Add Identifier for a Language: In the list of languages associated with the site, click the plus (+) icon next to the language you want to configure

    Personalization Analytics And Personalization Tab

    Step 3: Choose Identifier Type:

      • Create a New Identifier: Select the Create new tab.
        • Name the Identifier: Provide a unique name for the analytics identifier.
        • Set Session Timeout: Define the session timeout duration (default is 30 minutes).
      • Assign an Existing Identifier: Select the Assign existing tab.
        • Select Identifier: Choose from the list of existing identifiers available in your environment.

    Personalization Add Analytics Identifier

    Let’s Personalize a Page in Sitecore XM Cloud

    1. Navigate to the Page in the Page Builder
    • From the XM Cloud portal, open your site and select the page you want to personalize.
    • Once it loads in Page Builder, you’ll see a “Personalize” tab at the top navigation bar if personalization is enabled.

    Personalize Tab

    1. Create a Page Variant
    • Click on the Personalize tab.
    • Select Create Variant.
    • Provide a name for the variant (e.g. “Every Monday Campaign”)

    Create Variant

    • Click Next to proceed to audience configuration.

    Create Audience

    1. Define the Audience for the Variant

    Available Condition Categories

     

    Click Add first condition to define who should see this variant.

    Choose from the available conditions such of different tags

     

     

    • Configure the selected condition using the provided fields.

    Condition

    • You can add multiple conditions using AND/OR logic.

    Multiple Conditions

     

     

    Personalization Options Available

     

    1. Customize the Variant
    • Once you click on Save, your variant is created and the audience is defined, you can now edit the variant.
    • On the side is a screenshot of the Page Builder that lists down all that we can do with personalization on the page.

     

     

     

     

    Personalized Component

    • You’ll see a color-coded border or indicator showing that you’re editing a personalized version.
    • Each change you make is isolated to that variant and won’t affect the default view.

     

    1. Preview the Variant
    • Use the Preview feature to see what the page will look like for the targeted audience.
    1. Publish the Variant
    • When satisfied, click Publish to activate your personalized variant.
    • Sitecore XM Cloud will now automatically show the appropriate variant to users matching the defined audience.

     

    Personalization in Sitecore XM Cloud isn’t just a feature – it’s a strategic advantage. By enabling analytics identifiers and using Page Builder to create tailored experiences, you can deliver the right content to the right audience at the right time. With this setup in place, you’re well on your way to building smarter, more engaging digital experiences.

    In the next blog, I’ll take you behind the scenes of how personalized content is actually delivered in Sitecore XM Cloud. We’ll explore the request lifecycle, how the Cloud SDK plays a role in fetching and rendering personalized variants, and the technical flow that powers real-time targeting. This deeper dive will help you understand not just what personalization looks like, but how it works under the hood.

     

    Source: Read More 

    Facebook Twitter Reddit Email Copy Link
    Previous ArticleUniversal Design and Global Accessibility Awareness Day (GAAD)
    Next Article Community News: Latest PECL Releases (05.20.2025)

    Related Posts

    Common Vulnerabilities and Exposures (CVEs)

    CVE-2025-53602 – Zipkin Spring Boot Actuator Heapdump Information Disclosure

    July 4, 2025
    Common Vulnerabilities and Exposures (CVEs)

    CVE-2025-7068 – HDF5 Memory Leak Vulnerability

    July 4, 2025
    Leave A Reply Cancel Reply

    For security, use of Google's reCAPTCHA service is required which is subject to the Google Privacy Policy and Terms of Use.

    Continue Reading

    CVE-2025-23098 – Samsung Mobile Processor Exynos Use-After-Free Privilege Escalation

    Common Vulnerabilities and Exposures (CVEs)

    Laid off but not afraid with X-senior Microsoft Dev MacKevin Fey [Podcast #173]

    Development

    CVE-2025-4182 – PCMan FTP Server Buffer Overflow Vulnerability

    Common Vulnerabilities and Exposures (CVEs)

    CVE-2025-6369 – D-Link DIR-619L Stack-Based Buffer Overflow Vulnerability

    Common Vulnerabilities and Exposures (CVEs)

    Highlights

    CVE-2025-32421 – Next.js Race Condition Page Prop Exposure

    May 15, 2025

    CVE ID : CVE-2025-32421

    Published : May 14, 2025, 11:15 p.m. | 3 hours, 51 minutes ago

    Description : Next.js is a React framework for building full-stack web applications. Versions prior to 14.2.24 and 15.1.6 have a race-condition vulnerability. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve `pageProps` data instead of standard HTML. This issue was patched in versions 15.1.6 and 14.2.24 by stripping the `x-now-route-matches` header from incoming requests. Applications hosted on Vercel’s platform are not affected by this issue, as the platform does not cache responses based solely on `200 OK` status without explicit `cache-control` headers. Those who self-host Next.js deployments and are unable to upgrade immediately can mitigate this vulnerability by stripping the `x-now-route-matches` header from all incoming requests at the content development network and setting `cache-control: no-store` for all responses under risk. The maintainers of Next.js strongly recommend only caching responses with explicit cache-control headers.

    Severity: 3.7 | LOW

    Visit the link for more details, such as CVSS details, affected products, timeline, and more…

    That new Elden Ring Nightreign trailer has me more excited than ever for the roguelike RPG, but one thing has me worried

    May 2, 2025

    CVE-2025-46535 – AlphaEfficiencyTeam Custom Login and Registration Missing Authorization Vulnerability

    April 25, 2025
    Rilasciata Wifislax64 4.0: La distribuzione GNU/Linux per la sicurezza delle reti wireless

    Rilasciata Wifislax64 4.0: La distribuzione GNU/Linux per la sicurezza delle reti wireless

    April 9, 2025
    © DevStackTips 2025. All rights reserved.
    • Contact
    • Privacy Policy

    Type above and press Enter to search. Press Esc to cancel.