[TYPO3-team-core-v5] Feature Inspiration: Targeting and Personalisation

[Aske Ertmann]

Hey Daniel

This is already a feature of the CMS eZ publish to some extend. I have a colleague whom might be interesting in doing this for Phoenix at some point, but it's still a "nice to have" feature and many things needs to be sorted out before we can focus on this. I do agree though that it could be a nice addition to the CMS, and in my opinion it should be merged with some kind of A/B test support. It does however cause some issues with caching, especially if the server has to render all contexts based on the users agent, geolocation etc.

Thanks for the suggestion, and we should keep this in mind when we reach the point to go over the feature list again.

Aske

On 12/05/2012, at 10.59, Daniel Pötzinger wrote:

> I just watched a nice marketing Video from Adobe CQ in the header here and wanted to share it with the 5.0 team:
> http://www.adobe.com/solutions/digital-marketing/web-experience-management.html
> 
> Imho it shows what CMS in the future (and now) need to be capable of - Its not anymore just building a website consisting of static content.
> Its more of having a tool that allows me to manage and preview the website for the different target groups around the world...
> 
> For 5.0 something like this can be the feature that drives the demand to update - what do you think.
> 
> Some technical thoughts on this, that I wanted to share:
> - there could be a flexible personalization / targeting container, where I can add multiple versions of a content based on targeting rules (such as selecting personas, locations, weather, time ...).. (And the (ESI) caching of this block supports different cachekeys based on the specified rules..)
> -  the "visitor context" of a website could hold common (anonymous infos) like the geolocation, local-time, deviceinfos..
> - after a user is authenticated he could be "mapped" to a certain persona (automatically)
> - the frontend preview allows to preview the website in different contexts - I think Adobe solved this very well
> 
> Cheers,
> Daniel
> 
> _______________________________________________
> TYPO3-team-core-v5 mailing list
> TYPO3-team-core-v5 at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core-v5