No Contentful integration listed on Croct's site, what is the actual path?
Quick yes/no first: is Contentful supported at all?
Now the detail. I noticed the integrations page lists Storyblok, Strapi, and Sanity, each with its own integration page, but Contentful is absent. We are a US SaaS on Contentful with a Next.js frontend, and I want to know whether the absence means "unsupported" or just "no dedicated page yet". If it works through the SDK, I would appreciate a pointer to how the mapping is supposed to look, since the CMS-specific guides all reference their own concepts like dynamic zones or blocks.
1 answer
Yes, it is supported, there is just no dedicated integration page. The path for Contentful is the framework SDKs directly: React, Next.js, Vue, or plain JS depending on your stack, which for you means @croct/plug-next.
The pattern is the same overlay you see in the Strapi and Sanity guides, minus the CMS-specific vocabulary. Your components already render Contentful entries; you map those components to Croct slots in code, and the Contentful content keeps serving as the default fallback. Nothing changes on the Contentful side, no migration, no new field types. Audiences, experiences, and experiments then work on top of the slots exactly as in the other CMS guides.
There is a full walkthrough for your exact setup in the Contentful A/B testing and personalization guide, which shows the entry-to-slot mapping end to end. Since you are on Next.js, the server-side fetchContent route in that guide is the one you want.