Sitecore CDP - every API call to Full Stack Experience creates a new session

on

 If you've experienced an issue with Sitecore CDP/Personalize where every API call to full stack experience creates a new tracking session, you are not alone.

In one of my past projects, I had this issue with CDP + Personalize tenant wherein we noticed that every API call from the web application creates a new tracking session in the user data. I subsequently created a Sitecore support ticket# CS0348516.

If you want to know the session count limitation that you can access within your decision model, take a look at this post.

Though Sitecore said the decision model should have access to past 1000 sessions, but it was the not case in reality as the model had access only to 40 sessions.

As outlined in this documentation page https://doc.sitecore.com/personalize/en/developers/api/call-the-personalize-api.html, there are multiple ways to call the callFlows REST API viz.,

  • Using email
  • Using custom identifier
  • Using browserId
In our case, we used the custom identifier to call the /callFlows API. Sitecore suggested us to use browserId instead as it was not causing the extra session to be created in CDP/Personalize. But based on my testing, it was not the case.

Sitecore registered a feature request to have their product development team look into it in their future backlog.

If you are planning to use session/event data in your decision model, be wary of this limitation and if you are looking for a workaround, take a look at this blog post.


Comments

Post a Comment