Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Add feedback Subscribe
Status Investigating
Product Customized Commerce
Categories Technical
Created by Guest
Created on Mar 8, 2023

RELATED FEEDBACK

Change sort order of tracking interceptor classes

I have noticed that the Product Recs integration to Commerce 14 is creating three cookies on a new browser session:

  • epi_RecommendationsTrackingSessionId

  • epi_RecommendationsTrackingUserId

  • EPiSessionId

However the last one is set before the first one overwrites it. And for the rest of its lifetime it is not used anymore. It looks like it is a default value, which is overwritten by the more specific Session Id from Product Recs.

To reduce the header size of all following requests, I suggest swap the sort order of EPiServer.Personalization.Commerce.Tracking.PersonalizationTrackingDataInterceptor and EPiServer.Tracking.Core.Interceptors.TrackingSessionIdInterceptor. This way the EPiSessionId cookie is only set, if the Product Recs Session Id cookie is not already set (which could be because that plugin is not even installed).

  • Post comment
  • Optimizely
    Tom Bramley
    Reply
    |     Oct 4, 2023

    Thank you for submitting this request! Our team is currently reviewing if and how we may implement this feature, particularly with consideration of our wide client base. We will update this ticket once we have completed this investigation