Personalising Headless CMS content across channels can be achieved with Optimizely Visitor Groups when a property in the http request can identify the source.
For example a mobile app request sent to a Headless CMS could include the following Http Header key value: “mobile-app-request”:true
Request Header Visitor Group Criterion
A visitor group criterion is required that can can match a request if it sees a header with a specified value.
We have pushed the following GitHib repo containing source code for a Request Header Visitor Group Criterion packaged so that it can be added to a nuget feed.
https://github.com/made-to-engage/EPiServer-Request-Header-Visitor-Group
Once installed, CMS Editor’s have the ability to personalise content for channels.
Johnny Mullaney 