Feature #71694


Personalized Content

Added by Carsten Tornow over 8 years ago. Updated about 8 years ago.

Must have
Target version:
Start date:
Due date:
% Done:


Estimated time:
PHP Version:
Sprint Focus:


A website should be made to deliver the best possible content for the readers. From this perspective, it is important to create personalized content. Wouldn't it be great, if TYPO3 could offer that as well?

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #17638: Integrate possibility to show content elements depending on a given ruleClosed2007-09-29

Related to TYPO3 Core - Feature #72049: Marketing SectionClosed2015-12-03

Actions #1

Updated by Mathias Schreiber over 8 years ago

  • Description updated (diff)

Hi Carsten,

this is a balancing act between functionality and system requirements.
We've have been doing personalized content for quite some time but you need different software to be installed other than PHP and MySQL (which are our current system requirements).
So in order to add fully personalized content you need other means of data storage in order to make it run in a performant manner.

I do fully agree that these Feature would be neat, but given the current system requirements I rather envision these features to be part of a personalization suite that can be installed on top of the TYPO3 core

Actions #2

Updated by Oliver Hader over 8 years ago


I totally agree with Mathias here, doing personalization right it requires much more than the default MySQL/PHP web environment. But maybe I/we are thinking a bit too complicated and maybe you, Carsten, could please outline what personalization means in your scope - just some examples. Terms like inference and reasoning on a semantic level or even going the direction of the recent activity stream enhancements of the W3C social WG would just be too much for TYPO3's basic requirements in the core.

I'm looking forward to more specific input on that feature request. Thanks in advance.

Actions #3

Updated by Georg Ringer over 8 years ago

  • Status changed from New to Needs Feedback
Actions #4

Updated by Carsten Tornow over 8 years ago

Hi Matthias & Oliver,

I'm definitely none of the hardcore programmers, I'm more a content guy. But in my view, there would be a possible approach:

First you would have to create so called „personas“ in TYPO3 - with different characteristics: Country/City, time on the site, which pages were visited, male/female ... This characteristics could combined booleish. The "personas" are saved in a separate field in the table "tt_content".

The next step: All access data located i.e. in Google Analytics. These datasets have to get into the system somehow. There is a so called "Collection API". Is this a possible implementation: ?

Next: All content elements should get an additional selection field - very similarly as the „categories“. If a visitor should be identified as a specific „persona“, this content-element is rendering on the webpage.

As I said, I see it from a little different point of view, compared to a classic programmer. But if I can help you somehow, I'd love to…


Edit: Therefore there is no need of special view helpers or things like this... and btw. solutions like pimcore based on PHP (zend framework) and MySQL too...

Actions #5

Updated by Mathias Brodala over 8 years ago

This sounds a little bit like the contexts extension. Did you already have a look at this?

And yes, something like this or the channels concept of Neos would be useful in the TYPO3 core.

Actions #6

Updated by Carsten Tornow over 8 years ago

Yes, thank you... The special concept of this new feature would be the usage of external tracking/targeting data...

Actions #7

Updated by Alexander Opitz over 8 years ago

Can we close this issue?

Actions #8

Updated by Alexander Opitz about 8 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.


Also available in: Atom PDF