Skip to content

Configuring the Rich Text Group module

Manage several conditional sections from one placeholder, each with its own content, conditions, and fallback.

The Rich Text Group module holds several conditional sections in a single placeholder on the landing page. Instead of dropping eight Rich Text modules onto the page and asking a HubSpot admin every time you need a ninth, you add sections inside the module — reordering, adding, and removing them entirely in Quotivity.

In HubSpot’s module picker it’s called Rich Text Group (Quotivity).

Group visibility (optional) at the top of the panel takes condition groups that hide the whole module unless the quote meets them. Leave it empty and the group always renders, section by section.

Click Add section to create one, drag sections by the grip handle to reorder them, and click a section’s name to rename it — the name is internal, for finding your way around a long list.

Setting What it does
Section type Rich text, or Custom code for LiquidJS (Enterprise)
Heading An optional heading above this section’s content
Display content or Code The section’s content, depending on its type
Conditions Condition groups that decide whether this section appears
Show fallback content when condition is false Turns on alternate content for quotes that fail the conditions
Fallback type and Fallback content The alternate content, which can be rich text or custom code

Sections render top to bottom. A section whose conditions fail and has no fallback is skipped, and the sections around it close up. If nothing in the group has content to show, the whole module is left out of the quote — the preview shows a placeholder in that case, which buyers never see.

  1. Open the module. Select Rich Text Group in the Template Modules panel.
  2. Add a section and name it after what it covers — “Renewal note”, “EU addendum”, “Onboarding”.
  3. Write the content and set the conditions that should reveal it.
  4. Add a fallback where a quote that fails the conditions still needs something in that position.
  5. Repeat for each variant, drag the sections into reading order, then preview against a few different deals and publish.

Custom code sections require an Enterprise plan.

Setting a section’s type to Custom code replaces the rich-text editor with the LiquidJS editor, including the AI assistant, an expanded editor, and syntax feedback. Tokens and filters work the same way as in the Custom Code module — see Custom Code Module (LiquidJS).

  • Group related variants in one module and keep unrelated content in its own module, so the section list stays readable.
  • Whole alternative documents still belong in separate templates. Use this module for passages, not for a second version of the quote.
  • Preview with sample data from a deal that matches each condition, so you see every branch before publishing.