-
New Feature
-
Resolution: Done
-
Major
-
1.8
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
HL & LD 31, HL & LD 32
-
5
User story:
As a SPA developer, I want to get personalized content from the website workspace statefully, so I can deliver personalized experiences in my SPA.
Acceptance criteria:
- Delivery endpoint resolves the same content as the pages app templates do, based on the same active user information & traits.
- The OOTB traits work.
- Traits from existing modules with trait detectors work.
- The client can benefit from personaliztion without passing in explicit traits and segments
Notes
It is expected that to achieve the above there must be a stateful session in use. Somehow the client must communicate its sessionID. For example via a cookie or request parameter
- clones
-
MGNLPN-474 Get (stateless) personalized content from the Delivery endpoint
- Closed
- depends upon
-
MGNLREST-313 Introduce Stateless flag for REST personalization
- Closed
- is causing
-
MGNLPN-552 DOC: Getting (statefull) personalized content from the Delivery endpoint
- Closed
- is related to
-
MGNLPN-557 Implement "root level" cookie, header and request parameter traits
- Closed
- relates to
-
MGNLPN-543 INT-Test::scenarios::Headless p13n via Delivery endpoint
- Closed
- mentioned in
-
Page Loading...