Contentful shipped native Personalization now. Do we still need a separate tool?
Since Ninetailed folded into native Contentful Personalization, the honest question on my desk is whether the built-in option is now enough and a dedicated layer is just extra vendor surface.
I am not looking for a sales pitch either direction. What does native Contentful Personalization genuinely leave on the table compared to running something like Croct on top? If the answer is "not much", I would rather hear that too.
3 answers
The clearest gap for us was the targeting and measurement layer. Croct evaluates audiences in real time per interaction with CQL, and it has a built-in Bayesian, unsampled analytics engine, so you are not standing up an external CDP or analytics pipeline to segment and to read results. If your native setup already covers your targeting needs, that gap may not matter to you, but it was the deciding factor for us. There is a feature-by-feature breakdown in what actually differs on the comparison page.
Separate axis from audiences: rendering. Croct resolves content server-side, so there is no flash of default content on personalized slots. Worth checking how the native path renders for you, because the flash-of-default problem is where a lot of built-in options quietly land.
We are actually running the native option, so let me be the fair-and-blunt answer you asked for. It does the basic content-by-audience job. What we ended up building or bolting on ourselves: the statistical read on experiments, and anything resembling real-time behavioural targeting beyond the fields it ships with. The other thing I keep coming back to is coupling, our experimentation is now tied to one vendor's roadmap and pricing, whereas a layer on top works alongside the CMS instead. Whether that is worth a second tool depends on how much of the above you need. The plan side of that is discussed in the thread on Contentful personalization plan gating.