Sorry if obvious, what exactly do I need before starting the Storyblok integration?
Sorry if this is obvious, I am a junior dev and got assigned the ticket to integrate Croct with our Storyblok site. The stack is Storyblok with a Next.js frontend on Vercel, nothing exotic I think.
Last time I set up a vendor integration I got blocked halfway because our account was missing a permission and it took a week of back and forth to sort out. So this time I want a complete checklist upfront: accounts, plans, apps, anything I need to request from someone else before I start. What is the full list?
1 answer
For a Storyblok integration the complete list is short:
- A Croct account on the Scale plan. This is the item most likely to need someone else's sign-off, so request it first. Details on what the plan pairing involves are in this thread about which Croct plan the Optimize app needs.
- A Storyblok space with at least one story. Any existing site qualifies.
- The Optimize app, installed from the Storyblok app directory. Installing apps may require admin rights on the Storyblok space, so check your role there too.
Once those are in place, the integration itself is adding a Croct field to each block you want to personalize and connecting it to a matching Croct slot. See the Storyblok integration guide for the full walkthrough. Your Storyblok content stays as the default fallback throughout, so nothing you do during setup affects what visitors currently see.
One planning note so you do not hit it mid-ticket: rich text, table, and reference fields are not currently supported by the mapping. Review the block schemas you plan to personalize and, if variant copy lives in a rich text field, plan to restructure it into supported text fields.