Skip to main content
Open in Introw: Synced sections

​
How it works

Synced sections live alongside experiences in the experience builder. A synced section is a saved content block you can insert into any experience. You can create one from scratch or save an existing section from an experience as a synced section. Once inserted, an instance stays linked to the saved section, so editing the saved section updates every place it is used. When a single experience needs a different version, you detach that instance, which keeps a local copy and breaks the link so further edits to the saved section no longer affect it.

​
Prerequisites

  • Write access to experiences and sections.

​
Settings & configuration

Synced sections are managed under Synced sections.

​
Creating a synced section

Create an empty synced section and build it in the editor, or save an existing section from an experience as a synced section so its content becomes reusable.

​
Inserting into an experience

In an experience, add a synced section from the section picker. The inserted instance is linked to the saved section.

​
Editing

Open the saved section at its editor and edit it; changes propagate to the linked instances. A linked instance in an experience points back to the saved section for editing.

​
Detaching

Detach an instance to break its sync link and keep a local, independently editable copy in that experience.

​
Duplicating

Duplicating a section copies its content; if it embeds CRM views, those references are remapped so the copy works on its own.

​
Setup walkthrough

1

Open synced sections

Go to Synced sections.
2

Create a section

Create a synced section and build its content, or save one from an experience.
3

Insert it

Add the synced section to an experience from the picker.
4

Edit centrally

Edit the saved section and confirm the change reaches its uses.
5

Detach if needed

Detach an instance when a portal needs a one-off version.

​
How-to guides

Reuse content across portals with synced sections

Build a section once, insert it into many experiences, update it everywhere from one place, and detach a one-off when needed.

​
Limits & gotchas

Editing a saved section changes every linked instance, so review where it is used before making changes. Detaching is one-way for that instance: it no longer receives updates from the saved section. Publishing the experiences that use a section is still required for partners to see updates.

​
Troubleshooting

  • An edit did not appear in a portal - the instance was detached, or the experience was not published.
  • A change affected an unexpected portal - the section is synced across more experiences than expected.
  • A duplicated section shows wrong CRM data - confirm the CRM references were remapped on duplication.