Introducing the XM Cloud connector with Sitecore Connect
This new connector enables seamless integration between XM Cloud and marketing sites, social media, content management systems, or third-party applications such as Salesforce.
The connector includes several out-of-the-box actions:
Create asset in Media Library – use this to create an asset based on information from a third-party system.
Fetch asset from Media Library – use this to fetch a Media Library asset and upload it to a third-party system.
Get an item – retrieve a Sitecore item by name. Useful to fetch content details into Power BI or Tableau dashboards.
Create an item – add a new item to Sitecore. Ideal for automating content creation with external CMSs or form submissions.
Update an item – modify the title and text of an existing item in Sitecore. Perfect for syncing updates from tools such as Google Sheets.
Delete an item – remove a Sitecore item by name, helping ensure compliance by removing expired or sensitive content.
Custom action – invoke any Sitecore XM Cloud Authoring API endpoint to build custom solutions by providing an appropriate GraphQL mutation.
Documentation
This new connector enables seamless integration between XM Cloud and marketing sites, social media, content management systems, or third-party applications such as Salesforce.
The connector includes several out-of-the-box actions:
Create asset in Media Library – use this to create an asset based on information from a third-party system.
Fetch asset from Media Library – use this to fetch a Media Library asset and upload it to a third-party system.
Get an item – retrieve a Sitecore item by name. Useful to fetch content details into Power BI or Tableau dashboards.
Create an item – add a new item to Sitecore. Ideal for automating content creation with external CMSs or form submissions.
Update an item – modify the title and text of an existing item in Sitecore. Perfect for syncing updates from tools such as Google Sheets.
Delete an item – remove a Sitecore item by name, helping ensure compliance by removing expired or sensitive content.
Custom action – invoke any Sitecore XM Cloud Authoring API endpoint to build custom solutions by providing an appropriate GraphQL mutation.
Documentation
You can now upload PDFs and Microsoft Word files directly from the Page builder
New publishing jobs table user interface and advanced API capabilities
This is something we've been missing since XP and eventually, we've got the visibility over the publishing operations and history.
- Gain immediate visibility of your publishing operations for the past 30 days, for ongoing peace of mind.
- Identify whether a particular job is queued, and where it is in the queue, so you can report confidently on its progress.
- Track publishing jobs from start to finish with status updates. Know exactly when your content is being published or if an issue needs your attention, so you can troubleshoot in the moment and avoid missed deadlines.
- See who triggered each publishing job and when. This level of clarity ensures effortless to help address issues before they become obstacles.
- Access additional job details, such as the specific publishing type and publishing options selected. Each job is uniquely identified by an internal job ID, enabling you to easily locate it in the publishing logs for further investigation.
- See the start and finish time of each job, along with comprehensive metrics such as total duration, queue time, and running time.
- Accidentally started a publishing job or spotted an issue? Cancel jobs at any time, without the need for disruptive environment restarts.
- Designed for marketers, not just admins. Everyone on your team can access and do whatever they need to deliver content without delays.
Read more
This is something we've been missing since XP and eventually, we've got the visibility over the publishing operations and history.
- Gain immediate visibility of your publishing operations for the past 30 days, for ongoing peace of mind.
- Identify whether a particular job is queued, and where it is in the queue, so you can report confidently on its progress.
- Track publishing jobs from start to finish with status updates. Know exactly when your content is being published or if an issue needs your attention, so you can troubleshoot in the moment and avoid missed deadlines.
- See who triggered each publishing job and when. This level of clarity ensures effortless to help address issues before they become obstacles.
- Access additional job details, such as the specific publishing type and publishing options selected. Each job is uniquely identified by an internal job ID, enabling you to easily locate it in the publishing logs for further investigation.
- See the start and finish time of each job, along with comprehensive metrics such as total duration, queue time, and running time.
- Accidentally started a publishing job or spotted an issue? Cancel jobs at any time, without the need for disruptive environment restarts.
- Designed for marketers, not just admins. Everyone on your team can access and do whatever they need to deliver content without delays.
Read more
❤1
Lots of improvements into Pages builder!
- A new button in the context toolbar lets you swap an existing component for another directly in the Page builder canvas.
- The right-hand configuration panel now shows the workflow state of the content item assigned to the selected component.
- The Page builder now respects the validation rules configured for fields. After you change the workflow state of a page, the popup now shows the correctly incremented version number.
- Local datasource items can now be created on pages that originate from a page branch.
- The Help panel is now also available from the top navigation toolbar in the Page builder.
- A new button in the context toolbar lets you swap an existing component for another directly in the Page builder canvas.
- The right-hand configuration panel now shows the workflow state of the content item assigned to the selected component.
- The Page builder now respects the validation rules configured for fields. After you change the workflow state of a page, the popup now shows the correctly incremented version number.
- Local datasource items can now be created on pages that originate from a page branch.
- The Help panel is now also available from the top navigation toolbar in the Page builder.
👍2
Sitecore Cloud SDK is now an open-source project available on GitHub. Current version is 0.5 and is available on npm.
The Cloud SDK works hand in hand with the already open-sourced Content SDK and our starter solutions, giving you visibility into the full application stack, from head implementation to content delivery and behavioral data handling.
The Cloud SDK works hand in hand with the already open-sourced Content SDK and our starter solutions, giving you visibility into the full application stack, from head implementation to content delivery and behavioral data handling.
❤4
You can now filter using the
_latestversion predicate set to true or false in search queries in the Preview GraphQL schema, and the result will be the highest version available in the system for a given item.Wow! Martin Miles has reversed engineered Sitecore PowerShell Remoting and re-implemented that back in a shape of a new cloud SitecoreAI Marketplace!
This is a very first PoC video confirming that IS in fact POSSSIBLE and seeking for a feedback. Based on the feedback, it could be laid on as a blueprint template for SitecoreAI Marketplace apps using PowerShell Extension.
Watch it yourself: https://youtu.be/bZGxODHq9rs
This is a very first PoC video confirming that IS in fact POSSSIBLE and seeking for a feedback. Based on the feedback, it could be laid on as a blueprint template for SitecoreAI Marketplace apps using PowerShell Extension.
Watch it yourself: https://youtu.be/bZGxODHq9rs
👏2👍1
Forwarded from Sitecore Telegram
Blok design system based on Tailwind and Shadcn has officially moved out of Beta and reached General Availability!
What’s new and why GA matters:
- Production-ready stability - fully validated for enterprise use.
- Consistent, scalable design language across Sitecore solutions.
- Enhanced developer experience with streamlined components and improved documentation.
Highlights from the Beta phase:
- Added more getting started guides based on community feedback.
- Extended and fixed MCP documentation for clarity and completeness.
- Redesigned the website for better intuitiveness and usability.
- Introduced sub-navigation for easier variant browsing.
- Added code tabs to improve developer experience.
- Created overview pages for better component discoverability.
- And much more refinements to make Blok future-prove, robust and developer-friendly.
Link
What’s new and why GA matters:
- Production-ready stability - fully validated for enterprise use.
- Consistent, scalable design language across Sitecore solutions.
- Enhanced developer experience with streamlined components and improved documentation.
Highlights from the Beta phase:
- Added more getting started guides based on community feedback.
- Extended and fixed MCP documentation for clarity and completeness.
- Redesigned the website for better intuitiveness and usability.
- Introduced sub-navigation for easier variant browsing.
- Added code tabs to improve developer experience.
- Created overview pages for better component discoverability.
- And much more refinements to make Blok future-prove, robust and developer-friendly.
Link
❤2
Marketer MCP got three new MCP tools that enhance how teams work with page previews and personalization:
get_page_preview_url - retrieve a preview URL for any page, enabling faster and more streamlined review cycles.get_personalization_condition_templates - access the full set of available personalization condition templates.get_personalization_condition_template_by_id - retrieve a specific template by ID for easier rule creation and automation.SitecoreAI certification 20% off discount code:
Valid through December 31st, 2025. Cannot be
combined with any other discount, entitlement, or
promo. Exam must be completed by February 28, 2026
SAI20Valid through December 31st, 2025. Cannot be
combined with any other discount, entitlement, or
promo. Exam must be completed by February 28, 2026
Cloud SDK v0.6.1 was released
Version 0.6.1 of the Sitecore Cloud SDK improves the creation process for the new, renamed cookies introduced in version 0.6.0.
In version 0.6.1, if old cookies are present in the web browser, the new cookies will inherit their values. This ensures that existing browser ID and guest ID values carry over to the new cookies.
In addition Version 0.6 of the Sitecore Cloud SDK introduces simplified cookie names:
-
-
This is a breaking change that requires updating application code, privacy policies, and cookie consent banners that reference the old cookie names.
For detailed upgrade instructions, see the upgrade guide.
Version 0.6.1 of the Sitecore Cloud SDK improves the creation process for the new, renamed cookies introduced in version 0.6.0.
In version 0.6.1, if old cookies are present in the web browser, the new cookies will inherit their values. This ensures that existing browser ID and guest ID values carry over to the new cookies.
In addition Version 0.6 of the Sitecore Cloud SDK introduces simplified cookie names:
-
sc_{SitecoreEdgeContextId} is now sc_cid-
sc_{SitecoreEdgeContextId}_personalize is now sc_cid_personalizeThis is a breaking change that requires updating application code, privacy policies, and cookie consent banners that reference the old cookie names.
For detailed upgrade instructions, see the upgrade guide.
You can now create a fully configured page in SitecoreAI using an existing page as a blueprint. This makes it easier to standardize page structures, accelerate content creation, and automate repetitive site‑building tasks.
To create a page from a blueprint, use the Create a page from a blueprint endpoint. Using this endpoint, you can:
- Create pages programmatically using a predefined blueprint structure.
- Ensure new pages inherit the blueprint's configuration, reducing setup time and minimizing manual errors.
To create a page from a blueprint, use the Create a page from a blueprint endpoint. Using this endpoint, you can:
- Create pages programmatically using a predefined blueprint structure.
- Ensure new pages inherit the blueprint's configuration, reducing setup time and minimizing manual errors.
You can now use AI-powered content optimization for the following field types: Droplist, Droplink, Droptree, Treelist, TreelistEx, Multiroot treelist, Multilist, Multilist with search, Taglist, and Checklist.
This enhancement helps you quickly identify the most relevant item options available for your component fields, improving accuracy and reducing manual selection time. You can also review AI generated suggestions for any supported list field directly in the Page builder without opening the Content Editor.
Read more
This enhancement helps you quickly identify the most relevant item options available for your component fields, improving accuracy and reducing manual selection time. You can also review AI generated suggestions for any supported list field directly in the Page builder without opening the Content Editor.
Read more
❤1
The Brand Review REST API evaluates whether a given piece of content complies with the brand guidelines defined in a brand kit. It analyzes input content provided in the request, such as text, images, and metadata, by comparing it against brand kit sections to ensure alignment with tone of voice, visual identity, legal requirements, and accessibility standards.
The API returns brand compliance scores, explanations, and improvement suggestions generated by SitecoreAI.
Admins can use this API to:
- Provide input content for brand review and determine whether it complies with brand guidelines or deviates from them.
- Evaluate how well the input content aligns with specific brand kit sections and subsections (fields), including Brand Context, Do’s and Don’ts, Tone of Voice, Grammar Checklists, and Visual Guidelines.
- Receive a brand compliance score for the input content on a scale from 1 to 5, where 5 indicates the highest level of alignment with the brand guidelines.
- Review and validate multiple input formats, including text, images, PDFs, metadata, Markdown, and JSON.
Read more
The API returns brand compliance scores, explanations, and improvement suggestions generated by SitecoreAI.
Admins can use this API to:
- Provide input content for brand review and determine whether it complies with brand guidelines or deviates from them.
- Evaluate how well the input content aligns with specific brand kit sections and subsections (fields), including Brand Context, Do’s and Don’ts, Tone of Voice, Grammar Checklists, and Visual Guidelines.
- Receive a brand compliance score for the input content on a scale from 1 to 5, where 5 indicates the highest level of alignment with the brand guidelines.
- Review and validate multiple input formats, including text, images, PDFs, metadata, Markdown, and JSON.
Read more
❤2
Public Marketplace apps now require data usage disclosures, AI usage disclosures (when applicable), and compliance with the Sitecore security checklist to ensure trust, transparency, and security for all users. Developers provide this information before submitting their public app for approval from Sitecore.
- Data usage disclosure - describe how the app collects, stores, and processes data.
- AI usage disclosure - if the app uses AI or machine learning in any capacity, describe how the app uses artificial intelligence and complies with relevant regulations.
- Sitecore security checklist - ensure the app complies with the Sitecore security requirements.
- Data usage disclosure - describe how the app collects, stores, and processes data.
- AI usage disclosure - if the app uses AI or machine learning in any capacity, describe how the app uses artificial intelligence and complies with relevant regulations.
- Sitecore security checklist - ensure the app complies with the Sitecore security requirements.
❤1
Unified real-time analytics with a modernized dashboard experience
SitecoreAI now offers a unified analytics experience with real-time updates across all performance dashboards. All analytics dashboards are consolidated into a single view in the Performance tab, reducing the need to navigate between multiple locations. The performance dashboards now include improved
SitecoreAI now offers a unified analytics experience with real-time updates across all performance dashboards. All analytics dashboards are consolidated into a single view in the Performance tab, reducing the need to navigate between multiple locations. The performance dashboards now include improved
<a target="_blank" rel="noopener noreferrer.👍1
From now on, all new SitecoreAI projects and environments automatically use decoupled deployments as it is enabled by default.
While you still can continue using the legacy Coupled Deployment model if needed, we do not recommend it. Future enhancements will primarily target the decoupled flow, so migrating ensures access to the full improvement set.
See the documentation how to create a new project.
Current projects that were creating with the coupled deployments continue to work without requiring configuration changes. Redeployment of these projects remains coupled deployments.
Sitecore recommends to actively switch any existing coupled deployment projects to the new decoupled architecture using the Convert option in the project settings.
See the documentation how to convert to decoupled deployment strategy.
Why Decoupled deployment matters
- Decoupled Deployments separate the CMS application from individual editing hosts, enabling:
- Targeted deployments without triggering full CMS rebuilds
- Independent codebases and repository structures for each editing host
- Reduced compute and search index load, improving performance and lowering costs
- Scalable multi‑site operations with isolated logs, clearer control, and faster iterations
- A better developer experience, especially in organizations with multiple applications sharing one CMS
- Editing hosts can now be configured to use separate Git repositories, giving teams the flexibility to isolate sites, streamline versioning, and align deployment flows with their preferred development and branching strategies.
While you still can continue using the legacy Coupled Deployment model if needed, we do not recommend it. Future enhancements will primarily target the decoupled flow, so migrating ensures access to the full improvement set.
See the documentation how to create a new project.
Current projects that were creating with the coupled deployments continue to work without requiring configuration changes. Redeployment of these projects remains coupled deployments.
Sitecore recommends to actively switch any existing coupled deployment projects to the new decoupled architecture using the Convert option in the project settings.
See the documentation how to convert to decoupled deployment strategy.
Why Decoupled deployment matters
- Decoupled Deployments separate the CMS application from individual editing hosts, enabling:
- Targeted deployments without triggering full CMS rebuilds
- Independent codebases and repository structures for each editing host
- Reduced compute and search index load, improving performance and lowering costs
- Scalable multi‑site operations with isolated logs, clearer control, and faster iterations
- A better developer experience, especially in organizations with multiple applications sharing one CMS
- Editing hosts can now be configured to use separate Git repositories, giving teams the flexibility to isolate sites, streamline versioning, and align deployment flows with their preferred development and branching strategies.
Did you know that SitecoreAI now lets you inspect real visitor profiles directly inside the platform, without stitching together clues from separate tools first?
With the new Profiles capability under "Audience and insights", you can browse your most recent site visitors, filter between anonymous and identified profiles, and search for a person by profile ID, client ID, or any identifier covered by your identity rules. That alone is already useful. But the real value starts when you open a profile.
SitecoreAI gives you a much richer picture of the visitor journey than a simple event list. You can see engagement metrics, session history, device usage patterns, top affinities, session locations, and even a time-of-day heatmap showing when that person tends to interact with your brand. In other words, this is where raw behavioral data finally starts becoming actionable.
For developers, architects, and technical marketers, this is especially interesting because #Profiles are not just a glossy UI layer. You can inspect the underlying JSON, review captured sessions and events, validate client IDs, and check whether your VIEW and IDENTITY events are actually producing the quality of data your personalization strategy depends on. That makes Profiles not only an analytics feature, but also a very practical diagnostics surface for implementation teams.
There is one important catch. Profiles become dramatically more valuable once Identity Resolution and Affinities are configured properly. Without identity resolution, visitor data stays fragmented across devices and sessions. Without affinities, you lose the dynamic interest scoring that helps SitecoreAI understand what each visitor actually cares about. So if you are seriously planning personalization, #Profiles should not be viewed as an isolated feature. They are the visible outcome of getting your data foundation right.
This is the part many teams underestimate. #Personalization does not fail because the UI is missing. It fails because the data model underneath is incomplete. #SitecoreAI #Profiles make that gap visible, and that is exactly why this release matters.
A few practical details worth knowing:
- Sitecore currently shows up to 100 recent profiles.
- Each profile can display up to 40 sessions from the last 90 days.
- Each session can show up to 100 events.
And yes, this is one of those features that looks simple on the surface, but for teams building serious personalization, optimization, and audience intelligence capabilities, it is a very meaningful step forward.
Documentation is available.
With the new Profiles capability under "Audience and insights", you can browse your most recent site visitors, filter between anonymous and identified profiles, and search for a person by profile ID, client ID, or any identifier covered by your identity rules. That alone is already useful. But the real value starts when you open a profile.
SitecoreAI gives you a much richer picture of the visitor journey than a simple event list. You can see engagement metrics, session history, device usage patterns, top affinities, session locations, and even a time-of-day heatmap showing when that person tends to interact with your brand. In other words, this is where raw behavioral data finally starts becoming actionable.
For developers, architects, and technical marketers, this is especially interesting because #Profiles are not just a glossy UI layer. You can inspect the underlying JSON, review captured sessions and events, validate client IDs, and check whether your VIEW and IDENTITY events are actually producing the quality of data your personalization strategy depends on. That makes Profiles not only an analytics feature, but also a very practical diagnostics surface for implementation teams.
There is one important catch. Profiles become dramatically more valuable once Identity Resolution and Affinities are configured properly. Without identity resolution, visitor data stays fragmented across devices and sessions. Without affinities, you lose the dynamic interest scoring that helps SitecoreAI understand what each visitor actually cares about. So if you are seriously planning personalization, #Profiles should not be viewed as an isolated feature. They are the visible outcome of getting your data foundation right.
This is the part many teams underestimate. #Personalization does not fail because the UI is missing. It fails because the data model underneath is incomplete. #SitecoreAI #Profiles make that gap visible, and that is exactly why this release matters.
A few practical details worth knowing:
- Sitecore currently shows up to 100 recent profiles.
- Each profile can display up to 40 sessions from the last 90 days.
- Each session can show up to 100 events.
And yes, this is one of those features that looks simple on the surface, but for teams building serious personalization, optimization, and audience intelligence capabilities, it is a very meaningful step forward.
Documentation is available.
Marketer MCP has renamed some tools - more info about it available here.
😁1