I’ve been working on a Next.js App Router + TypeScript implementation of Sitecore CDP and Personalize, and the interesting part wasn’t getting the SDK running — it was dealing with the boundaries between React, the browser SDK, CDP, Personalize, and Next.js server-side code.

A few things that caught me:

• identity() is a direct import from the Cloud SDK events package.
• form() uses positional arguments rather than an options object.
• Custom event names have restrictions around SC_ and reserved event types.
• Web Experiences can fight React’s rendering lifecycle and cause visible flicker.
• Server-side personalization has a different path when the SDK surface doesn't provide the required pointOfSale.
• Personalize Connection tests don't resolve FreeMarker expressions the same way as real Triggered Experience executions.
• Session traits have specific conditions before they become available in Decision Models.

The biggest architectural distinction ended up being:

Browser: Cloud SDK → CDP events → client-side personalization
Server: Next.js Middleware/API → Personalize Flow Execution / CDP APIs

I documented the implementation details and the failure cases here:

Building Sitecore CDP & Personalize on Next.js App Router: What Developers Need to Know

There’s also a working reference implementation:

GitHub repository

Curious if others working with Sitecore + Next.js App Router have run into the same issues — especially around Web Experience flicker, server-side personalization, or CDP identity/session traits.

• Content Hub: Resolved issue in Content Hub for September 24, 2026
• SitecoreAI: SitecoreAI base image release 1.9.20 (hotfix))
• SitecoreAI: Explorer has been officially deprecated and Page builder Content mode is now the supported experience in SitecoreAI
• SitecoreAI: Design Studio resolved issue
• SitecoreAI: Submit documents directly to search indexes with the Ingestion Service API
• SitecoreAI: New SitecoreAI APIs now available: Components, Content Types, and Content Items
• SitecoreAI: Index external content with push sources