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.
For detailed upgrade instructions, see the upgrade guide.
]]>sc_{SitecoreEdgeContextId} is now sc_cid
sc_{SitecoreEdgeContextId}_personalize is now sc_cid_personalize
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.
]]>New user interface
In Developer center > Batch uploads, you can now monitor all batch upload activities within the past 30 days. You can filter uploads by status and search by batch reference. The list displays real-time status updates, processing time, and success rates for each file. You can also download error logs directly from the user interface, making it easier to troubleshoot batch uploads.
New Batch API endpoints
The Batch API has two new endpoints:
Retrieve the details of batch uploads - the new /batches/inspect endpoint lets you list all batches from the past 30 days and examine a specific batch to see the status of individual files, such as file_uploaded or processing.
Retrieve upload status of a specific batch - the new /batches/inspect/{batchRef} endpoint supports the additional file_uploaded status, which is not available in the original /batches/{batchRef} endpoint.
Use profile traits to build audience segments, access key customer metrics, and improve targeting. You can apply them to conditions, segmentation, and analytics. If you have both CDP and Personalize, you can also use profile traits in experiments and experiences.
]]>Use cases
The support for deeply-nested structures makes advanced mode a powerful tool for more complex, real-world export scenarios. For example, customer records can now include arrays of contacts, detailed order histories, or detailed session data. This means you can now export session data for each user, including session duration, pages visited, and conversion events, to support behavior analytics or customer journey tracking.
Get started
Open a CDP audience export.
Click Output format > Edit > Advanced.
Enter your JavaScript function manually or generate it with the Code Assistant using natural language.
Advanced mode gives you full control over your export format and unlocks new possibilities for automation and personalization.
]]>Deliver stronger marketing outcomes, faster
Instant code generation - ask the Code Assistant what you need using natural language, and it will deliver precise, context-aware JavaScript.
Seamlessly contextual - the Code Assistant understands your editor’s current code combined with your underlying data schema and adapts the output accordingly. Your new JavaScript will be created using CDP’s supported entities and functions.
Built specifically for CDP - the Code Assistant can generate code in the following areas of CDP:
Audience export computations - compute the exact audience data you need for your next marketing campaign.
Conditional audience filtering - write robust, rule-based filters to target the right audience at the right time.
Session traits management - store session-based values to better understand your customer.
Privacy and security are top priority - we never use your prompts or code context to train our LLM. Your proprietary logic, brand details, and customer insights remain private.
Get started
Open your JavaScript editor in CDP to launch the Code Assistant.
Enter your natural language prompt or choose an example from our documentation.
Instantly receive clean, ready-to-run JavaScript.
We’re excited for you to use the Code Assistant to unlock new marketing possibilities!
]]>Customers with access to the Cloud Portal (primarily XM Cloud, CDP, Personalize, and Search customers) can request Stream FREE through the Cloud Portal starting today.
Customers who do not have access to Cloud Portal (primarily Content Hub and XP customers, with some exceptions) will need to sign updated Terms & Conditions (including the Cloud and AI Addendum) and be provisioned for Cloud Portal access. To initiate this, customers should contact their customer representative to request Cloud Portal provisioning.
Once Cloud Portal access has been granted, the customer’s Organization Owner or Admin can log in to the Cloud Portal, click the “Stream FREE” call to action, and accept the Cloud Addendum. After accepting the addendum, the customer will be automatically provisioned and will receive a Stream welcome email. The typical timeframe from accepting the T&Cs to receiving the welcome email is 2–4 hours.
To learn more about Stream and what is available in each tier, click here.
]]>Personalization - you now need to manually enable the capture of geolocation data. This ensures compatibility with Next.js 15, which no longer captures geolocation data automatically.
Search - the Cloud SDK now supports:
Document grouping, which lets you display all variations of an item (such as a product entity) as individual search results, or as a single grouped result based on a specific attribute.
The capture of country and referrer in search event interfaces.
You can now connect audience exports in Sitecore CDP directly to Sitecore Connect recipes, making it easier to automate data transfers to third-party systems. This feature removes the need to manually create a Sitecore Connect connection in CDP, copy webhook URLs, or switch back and forth between CDP and Connect, so it's simpler and faster to manage your audience exports.
When setting up an audience export in CDP, you can easily add a Sitecore Connect recipe by selecting from a list of active recipes. Here's how it works:
In Sitecore Connect, create a recipe and configure the webhook trigger. This step generates a webhook URL and lets you define the payload.
Add a prebuilt CDP action to the recipe, complete the setup, and activate the recipe.
In CDP, open your audience export and connect the active recipe directly by choosing it from the list.
When the audience export runs, it automatically triggers the connected recipe to process and forward the exported data based on your setup.
]]>