Right now anything that we want to render for specific user segments must be built on the client side, since we have no way to identify users on the server side. We want to access to a session cookie ID (or similar) for each user within the context of a server-side so that we can target SSR experiences to behavioral segments.
Tod Gillespie
Hi Tod, thanks for submitting this idea.
This is one of the areas that PageBuilder has a hard no for the time being where PageBuilder and Arc Web Delivery are designed with multiple layers of cache to handle large-scale traffic that requires the server-side renders to stay agnostic from user-specific session context (by design, stateless). That means there is no way to store or process user-specific data on the server-side render.
We do have an upcoming capability on PageBuilder called Audience Targeting which will bring capabilities for user segments and have different page versions (including SSR) to be served for different users (we are also considering cookie-based targeting use cases which you mentioned). We're curious about your use cases related to segmentation. Please reach out to your TAM and the PM who is working on this new capabilities planning and who can provide more details about that initiative.