[MGNLDEMO-181] Demonstrate behavioral personalization with a cookie trait Created: 18/Aug/16 Updated: 12/Sep/16 Resolved: 05/Sep/16 |
|
| Status: | Closed |
| Project: | Magnolia Demo Projects |
| Component/s: | magnolia-travels |
| Affects Version/s: | None |
| Fix Version/s: | 0.14 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 4d | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Release notes required: |
Yes
|
| Date of First Response: | |
| Epic Link: | Component P13N |
| Sprint: | Basel 60 |
| Story Points: | 13 |
| Description |
|
This story demonstrates the use of component personalization in the travel demo. It's a behavior-based scenario that matches content to the visitor based on the visitor's activity on the site. Set a cookie when the visitor answers the "Which tour type are you?" on the travel demo home page. When the visitor returns to the home page, don't show the tour type question anymore. Show instead a featured tours component that lists tours that match the visitor's preferred tour type. |
| Comments |
| Comment by Philip Mundt [ 05/Sep/16 ] |
|
Reverted on ee-packs due to migration diff. Needs fix before it can be added to pro-webapp. |