[MGNLPN-542] Get (stateful) personalized content from the Delivery endpoint Created: 28/Apr/21  Updated: 13/Jul/21  Resolved: 13/Jul/21

Status: Closed
Project: Magnolia Personalization
Component/s: None
Affects Version/s: 1.8
Fix Version/s: 2.1

Type: New Feature Priority: Major
Reporter: Christopher Zimmermann Assignee: Jaroslav Simak
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 1d 5h
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLPN-474 Get (stateless) personalized content ... Closed
Relates
relates to MGNLPN-543 INT-Test::scenarios::Headless p13n vi... Closed
causality
is causing MGNLPN-552 DOC: Getting (statefull) personalized... Closed
dependency
depends upon MGNLREST-313 Introduce Stateless flag for REST per... Closed
relation
is related to MGNLPN-557 Implement "root level" cookie, header... Closed
Template:
Acceptance criteria:
Empty
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Headless p13n
Sprint: HL & LD 31, HL & LD 32
Story Points: 5

 Description   

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


Generated at Mon Feb 12 06:38:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.