View interaction groups

Documentation Index

Fetch the complete documentation index at: https://docs.go.gbgplc.com/llms.txt

Use this file to discover all available pages before exploring further.

When you create Hosted journeys, the GO platform automatically generates an interaction group based on the domain elements required by the modules in your flow. The interaction group appears as a node in the Journey builder, positioned before the first processing module. This guide explains how to view the interaction group and understand the data fields and pages it contains

​

Before you begin

Before you can view an interaction group, ensure you have a one or more modules added to your journey and that you have selected Hosted journey as the integration method. If your journey uses the API only integration method, no interaction group is generated and no interaction node appears in the flow.

​

View an interaction group

1. Open your journey in the GO Journey builder. If you haven’t created a journey, refer to Create hosted journeys to get started.
2. In the journey flow, locate the interaction node. This is the green icon positioned between the Start of journey node and the first processing module.

3. Click the interaction node.

The Interaction Group panel opens on the right side of the builder. The panel displays two sections:

• Data fields
• Pages

​

Data fields

The Data fields section lists every domain element the journey needs to collect from end users. Each field appears as a tag with the domain element name and a remove icon. For example, a journey that includes an Age Verification module displays the following data fields: FullName, DateOfBirth, CurrentAddress, SSN, PreviousAddresses, MobilePhone, and PersonalEmail. The fields shown are derived automatically from the modules in the journey. If multiple modules require the same domain element, it appears only once.

​

Pages

The Pages section shows how the data fields are distributed across individual screens. Each page groups related fields together to create a logical flow for end users. Click the list arrow next to a page name to expand it. When expanded, the page displays the cards it contains. Each card is identified by a card ID that indicates the type of data it collects. For example, expanding the Personal details page of the Age Verification module shows:

• Card ID: NameCard
• Card ID: DateOfBirthCard
• Card ID: IdentifierCardSSN

A journey collecting personal and contact information might organise its cards across four pages:

• Personal details: contains cards for name, date of birth, and identification number.
• Contact details: contains cards for phone number and email address.
• Address details: contains cards for the current address.
• Previous Addresses: contains cards for previous address history.

The number of pages depends on the domain elements required by the journey. Each page contains up to five fields.

​

What you can do from this panel

You can remove a data field by clicking the x next to a field tag to remove it from the interaction group. This applies in two scenarios:

• Partial pre-fill mode: If you already have some user data, remove those fields from the panel and supply them via the API at journey start. The end user then provides the remaining data through the hosted screens or your own frontend.
• Hosted journeys: Any data field removed from this panel will not appear on the hosted screens shown to the end user. Use this to simplify the hosted UI by excluding fields that are not relevant to your journey.

​

How interaction groups update

The interaction group updates automatically when you modify the journey flow:

• Adding a module: If the new module requires domain elements that are not already collected, then those fields are added to the interaction group and distributed across pages.
• Removing a module: If the removed module was the only one requiring certain domain elements, then those fields are removed from the interaction group. Empty pages are also removed.
• Switching to API only: If you change the integration method from Hosted journey to API only, the interaction group and all associated fields, pages, and configuration are removed from the flow.

​

Next steps