Uploaded image for project: 'Magnolia Personalization'
  1. Magnolia Personalization
  2. MGNLPN-474

Get personalized content from the Delivery endpoint

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Selected
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.8
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      User story:

      As a SPA developer, I want to get personalized content from the website workspace, so I can deliver personalized experiences in my SPA.

      Notes:

      Personalization is one of the enterprise features that pure headless CMS do not have, now that we know many customers want to use the pages editor and personalization to populate headless frontends we should provide this.

      Acceptance criteria:

      • Developer can configure a delivery Endpoint to return personalized content. 
      • When so-configured, it resolves the same content as the pages app templates do, based on the same active user information & traits.
      • Alternatively, the REST call can specify which traits or segments should be used in the resolution (rather then using the info in the user session) - at least by querystring and post body as well as possibly other approaches.
      • If not specially configured, then a delivery endpoint delivers the same non-personalized format that it delivers now, including all of the variants. (This can still be useful if a developer wants to implement personalization in the frontend itself.)
      • This is only expected to work on any workspaces that are saved to by a "pages app", but there should be no limitations as other app types may eventually also support variant nodes.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mgeljic Mikaël Geljić
              Reporter:
              viet.nguyen Viet Nguyen
              Votes:
              4 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Date of First Response:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Time Spent - 31m Remaining Estimate - 4h 40m
                  4h 40m
                  Logged:
                  Time Spent - 31m Remaining Estimate - 4h 40m
                  31m