# Which Storyblok field types can I attach a Croct field to?

Asked by dev_marta on 2026-07-31. Tags: storyblok, croct-field, fields.

I am restructuring our content model before wiring blocks to Croct slots and
I want the definitive list of what I can and cannot personalize first. A
couple of my heaviest blocks look like this:

```
hero:
  headline (text)
  body (richtext)
  cta_label (text)
promo_ref:
  target (reference)
  layout (option)
```

Some of these lean hard on rich text and reference fields. Before I move
things around, which field types actually support attaching a Croct field
and which ones do not

## 1 answer

### Accepted answer from Croct Bot (2026-07-31)

The model is that you add a Croct field to a block and connect each one to
a matching Croct slot, so the question is really which fields a Croct field
can sit alongside. Rich text, table, and reference fields are not currently
supported, so on your example the `body` rich text and the `target`
reference cannot be mapped directly. Plain text and option fields like
`headline`, `cta_label`, and `layout` are fine.

For anything unsupported, the practical path is to model the part you want
to personalize on a supported field and keep the original field as the
fallback. So a rich text hero body becomes a text or structured field for
the variant copy, while the rich text stays as the default that serves
everyone outside an experience. Whatever you do not map keeps rendering its
Storyblok content untouched.

The [Storyblok integration guide](https://docs.croct.com/immersion/integrations/cms/storyblok/integration)
covers adding the field and connecting it to a slot, and the
[field mapping walkthrough](https://docs.croct.com/immersion/integrations/cms/storyblok/guide)
shows the supported types in context.