Feature parity checklist, what Ninetailed concepts map to what on Sanity + Croct?
I am preparing a client proposal to replace Ninetailed on a Sanity-based site, and the client team has asked for a concept-by-concept mapping so they know precisely what changes in their day-to-day vocabulary and what does not.
The concepts I need mapped: audiences, experiences, experiments, and insights. Additionally, I need to state clearly whether the Sanity content model changes during the swap, as the client's editorial team is sensitive to schema churn.
If anyone has produced a comparable matrix for a client engagement, I would value corrections to my assumptions rather than a general overview.
1 answer
I built this matrix for an engagement last quarter. Concept by concept:
| Ninetailed concept | Croct equivalent | What changes for the team |
|---|---|---|
| Audience | Audience (CQL condition) | Definitions become explicit CQL, evaluated in real time per interaction |
| Experience | Experience | Same word, same role: the who/where/what container |
| Experiment | Experiment attached to an experience | Assignment and bucketing are built in; stats are Bayesian |
| Insights | Built-in analytics | Unsampled, with drill-down by device, audience, time window, and custom events |
The vocabulary survives almost entirely, which fwiw made the client conversation easier than expected. The two genuine changes worth flagging in your proposal: audiences are authored as CQL conditions (readable enough that marketers adjusted within a session), and analytics move from a separate insights view into the platform's own reporting, so there is no external stats dependency to wire up.
On your schema-churn concern, you can state it flatly: the Sanity content model does not change. Existing documents stay in place as the fallback, and variants live in the experience layer rather than as document copies. Our editorial team noticed no difference in Studio, which is the sentence your client's editors want to hear.