Skip to content

Choice

The Choice component lets the visitor pick from a list of options you define: radio buttons for one answer, checkboxes for several, or a dropdown. Typical uses are a consent checkbox, a gender or interest question, or a preferred store. When the visitor presses a button set to Submit and Go to Next Step, the Value of every ticked option is collected and sent to your integration, where the component appears under its Name in Campaign Integrations. The short code at the top of the settings panel, next to the copy icon, is the component’s id. You only need it for a button’s custom script, where {{id}} stands for the ticked values (see Button).

The settings below sit in the Choice Properties section of the panel.

The name of the component in the builder’s component list. It is only for you and is never shown to the visitor or sent with the answer.

  • Radio Buttons (single-select): the visitor picks exactly one option.
  • Checkboxes (multi-select): the visitor can tick any number of options. This is what a new Choice starts as.
  • Dropdown (single-select): the options are shown in a dropdown list.

Each option has its own block. Use Add New Value to add one and the bin icon to remove it.

  • Label: the wording the visitor sees next to the option. It can be translated per language (see Campaign Localization).
  • Enable Editor: for radio buttons and checkboxes, replaces the plain Label with a rich text editor, so the option can carry bold text, colours or a link, for example “I accept the privacy policy”. Darken Editor Background only darkens the editor in the panel so light text is easier to read while you write; it does not change the campaign.
  • Value: what is sent to your integration when the option is chosen, such as yes, newsletter or store-12. It is the same in every language.
  • Pre-Selected: for checkboxes only, the option starts ticked.

Which wording the visitor sees depends on Enable Editor. When it is ticked, the rich text is shown and the plain Label is kept but not shown. When it is not ticked, the plain Label is shown. A dropdown always shows the plain Label, because a dropdown cannot show rich text.

Tick Required Value to stop the visitor from submitting the step until they have picked something: at least one ticked checkbox, a selected radio button, or a dropdown option with a Value. Once it is ticked, Enter Error Message appears for the text shown when the choice blocks the submit, for example “Please accept the terms to continue”. The message can be translated per language.

The remaining sections control the look: Columns under Dimensions lays radio buttons and checkboxes out in 1, 2, 3 or 4 columns, and Background Properties, Border Properties and Typography Properties style the options.

When validation runs. A choice is only checked when Required Value is ticked, and only when the visitor presses a button set to Submit and Go to Next Step. If it fails, the step does not move on. After that first attempt, the choice is checked again every time the visitor changes it.

What the visitor sees. A failing choice is outlined in red and its first option is focused if it is the first problem in the step. The Enter Error Message text appears in a small dark bubble above the options while the visitor is on them. Always write an Enter Error Message for a required choice.

What is sent.

  • Checkboxes: a list with the Value of every ticked option, in the order the options are listed.
  • Radio Buttons and Dropdown: a list with the one chosen Value.
  • Each integration stores the list in its own way, as set up in Campaign Integrations.
  • Nothing is sent for a choice the visitor left unanswered: no ticked checkbox, no radio button, or a dropdown still on an option with an empty Value. The integration leaves that field of the contact untouched.

Answers from every submitted step of the campaign are collected and sent together, each component listed by its Name and type in the integration settings. Values from the DataHub can be sent alongside them.

  • To give a dropdown a prompt such as “Select your store”, make it the first option and leave its Value empty. It is shown first, cannot be picked again once the visitor moves away from it, and counts as no answer.
  • A dropdown without an option with an empty Value starts on its first option, and that option is sent even if the visitor never opened the dropdown.
  • A single required checkbox is the usual way to ask for consent: one option, Required Value ticked, and a clear Enter Error Message.
  • Pre-Selected ticks are sent like any other tick, so do not pre-select a consent box.
  • Only components with an Integration Field are sent. Leave a component unmapped and its answer stays out of the integration, whichever integration it is. This is how you collect something for the campaign’s own use, such as a consent tick that drives a later step, without it reaching your CRM.
  • An integration mapping follows the component, not its Name, so renaming the component keeps the mapping. Deleting and recreating the component loses it.
  • Translate the Label, never the Value: your integration then receives the same value whichever language the visitor saw.

On the mobile tab, tick Override Desktop Properties to change the choice for mobile visitors (see Campaign Device Customization).

  • Can be set per device: the Values list (each option’s Label, rich text, Value and Pre-Selected), Columns, and the look (Background Properties, Border Properties and Typography Properties).
  • Shared by every device, set on desktop: Choice Type, Required Value and Enter Error Message. These are hidden on the mobile tab.

If you change the options for mobile, keep each Value the same as on desktop. Otherwise your integration receives different values depending on the visitor’s device.

To place the choice in a step, see Campaign Step. To add the button that submits it, see Button.