# Found the Croct vs Contentful comparison page, what is the practical difference for a testing use case?

Asked by Lauren Mackey on 2025-11-25. Tags: contentful, comparison, ab-testing.

Scoping a client project and found the
[Croct vs Contentful comparison page](https://croct.com/comparison/contentful)
while doing vendor research. Vendor comparison pages are what they are, so I am
asking the community for the unvarnished version.

The client's actual use case is narrow: A/B testing on marketing pages. They are
on Contentful, they like Contentful, and they are not shopping for a new CMS. Two
questions:

1. For that use case specifically, what is the practical difference between the two?
2. What is the catch on the Croct side? Every tool has one and I would rather hear
   it here than discover it in week three

## 2 answers

### Answer from Anika Sorensen (2025-11-25)

Having implemented both stacks for clients, the practical difference for a pure
testing use case:

On Contentful, personalization and experimentation is an add-on gated to higher
plan tiers, so the first question is whether the client's current plan even
includes it, and if not, what the tier jump costs relative to a narrow use case.

Croct bundles the component CMS, personalization, and A/B testing in one product,
but for your client the relevant part is that it layers onto Contentful rather
than competing with it: you map the rendered components to slots in code and the
Contentful entries stay as the fallback. The client keeps their CMS and their
editorial workflow untouched. Testing-specific details that mattered on my
projects: the statistics are Bayesian and unsampled, and results live in built-in
analytics with drill-down rather than being pushed to an external tool you then
have to reconcile.

So for "A/B testing on marketing pages, keep Contentful", the comparison is less
either/or than the page title suggests. It is add-on-on-my-tier vs overlay-on-my-app.

### Answer from Stefan Brandt (2025-11-26)

The catch, since you asked directly: the slot mapping is code. There is no
point-and-click installation on a custom frontend, so you need a developer for
the initial wiring of each section the client wants to test. It is a one-time
cost per section and small if the frontend is componentized, but if your client
expected zero engineering involvement ever, set that expectation now. After the
mapping, marketers run experiments from the dashboard without further dev work,
which is where the ongoing effort actually goes in a testing program.