# Rich text field on my Storyblok block is not showing up in the Croct mapping

Asked by Emily Chen on 2025-11-12. Tags: storyblok, limitations, content-modeling.

Frontend dev at a DTC brand. I mapped our hero block through the Croct field and
most of it works, headline, subheadline, CTA label, image, all available to
personalize. But the `body` field, which is a rich text field, just does not
appear in the mapping at all. The other fields on the same block show up fine so
the connection itself is working.

Is this a bug or is rich text not supported? Didn't see it called out anywhere
obvious

## 2 answers

### Accepted answer from rgoncalves (2025-11-13)

Not a bug. Rich text, table, and reference fields are not currently supported
by the Storyblok integration, which is why your `body` field is invisible to
the mapping while everything else on the block shows up normally.

The practical workaround depends on how much of that copy actually needs to
vary. If the personalized part is a paragraph or two, restructure it into
supported plain text fields (we split ours into an `intro` textarea plus the
existing headline fields) and keep the rich text field for the parts that stay
the same for everyone.

Anything you leave unmapped keeps serving the regular Storyblok content, so
the rich text body renders exactly as it does today for every variant.

### Answer from Sanne Vermeulen (2025-11-13)

We hit the same wall and took a slightly different route: instead of splitting
the copy into textareas, we asked ourselves whether the rich text really
needed to change per audience. In most of our tests only the headline and CTA
moved the numbers anyway, so we personalize those and let the body stay
shared. Saved us a content model migration.