Skip to main content

Form: Radio element

Single-select options with the optional "Other" text field — for when only one answer is valid

Form: Radio element

The Radio element is for when you want visitors to pick exactly one option from a set. Gender, title, preferred contact method, favourite category — any question where "only one answer is valid" is where Radio belongs.

It's the single-select twin of the Checkbox element, with the added bonus of an Other option toggle that lets visitors type a custom answer if none of your pre-defined choices fit.


In this article


Quick start

  1. Place the Radio element into the Canvas.

  2. Add Radio options and name them directly in the Canvas.


  3. Edit the text with the Inline editor. Adjust colour for unchecked and checked option with the colour picker in the Inline editor. Use Style to change the design of the radio buttons and spacing.


  4. Fill out a Radio name at the top of the Design panel. The name is internal and will name the Row or Column in the Structure panel. The name of the Radio is also used in the form submit event on the profile.

  5. Open Mapping on the right, choose the Data type, and add the values that should be saved when each option is selected.


Label

Add a label name to the Radio element to enhance accessibility. It works as a group name for the alternatives, which also helps screen readers understand the content.

A good label describes the question as a whole — for example, "How did you hear about us?" — while the Radio options are the individual answers.


Style, alignment and margins

Style

In the Style section on the right, adjust space between radio buttons. Set colour for border and fill with the colour picker. Click the X icon next to the icon to make it transparent.

Margins, alignment, duplicate

  • Margins (padding) — maximum 100 pixels.

  • Alignment — align the element to the left, centre or right.

  • Duplicate — to copy the element, select it in the Canvas and click Duplicate in the left hand side menu (at the bottom).

Other option

Activate Other option to create an additional input field for a custom choice. If a visitor doesn't find any of the listed options suitable, they can pick this option and fill in their own answer as text.

This is useful when you don't want to limit the visitor but also can't list every possible answer — for example, "How did you hear about us?" with common channels listed plus an Other option for anything unusual.

Required field

Activate Required field if the field is mandatory. If toggled on, visitors will not be able to submit the Form without selecting an option.

💡 Tip. The design options work interactively. Hold an icon for a pixel value and drag left/right to increase or decrease the number of pixels. The sizes update live in the Canvas.


Visible options vs Mapping options — the two sides of a Radio

This is one of the single most-misunderstood parts of the Radio element (and it applies equally to Checkbox and Dropdown). Two separate things control what happens when a visitor picks an option:

  • The text in the Canvas — what the visitor sees and chooses from. This is the visible label on the Form itself. It can be as long and natural as you like.

  • The Option value in the Mapping section — what gets saved on the Profile (and in the Event data) when that option is selected. This is the actual data that ends up in your Audience.

The two are set independently. They can — and often should — be different. A friendly, descriptive label for the visitor, and a clean, short, structured value for your data.

Example

Visible in the Canvas (what the visitor sees)

Option value in Mapping (what gets saved)

I'd prefer she/her pronouns

Female

I'd prefer he/him pronouns

Male

I'd prefer they/them or another option

Non-binary

The Form stays warm and respectful; the Audience data stays clean and segmentable.

How to set them up — two ways

You can add options from either side of the split, and the editor keeps both sides in sync:

Method 1 — start in the Canvas

  1. Click a radio option in the Canvas and type the visitor-facing label.

  2. To add more options, click + Add option at the bottom of the Radio element in the Canvas.

  3. Then switch to the Mapping panel on the right and fill in the matching Option values.

Method 2 — start in the Mapping panel

  1. In the Mapping section on the right, click + Add option at the bottom of the options list to create a new option.

  2. Type the Option value that should be saved.

  3. Then switch to the Canvas and type the visitor-facing label for the matching radio option.

Both methods produce the same result — the choice is just about which side you want to think about first. Design-first people tend to start in the Canvas; data-first people tend to start in Mapping.

💡 Tip — when in doubt, keep Mapping values short. Segments and personalisation read the Mapping value, not the visible label. Short, clean values are almost always better for data.

If Mapping values are left blank

If you try to proceed to the next step without filling in the Option values in Mapping, Apsis One will block the activation and prompt you to go back and make the required changes before trying again. You can't publish a Form with unmapped options.

This is the system protecting your data quality.


Mapping

Open the Mapping section on the right. This is where you set the values that will be stored on the Profile that fills out the Form.

  1. In the Data type dropdown, select how to store the responses. Choose Attribute to save answers as values for the visitor's Profile Attributes, or Form response only to collect them as Event data.

  2. Add Option values in the Mapping section. Fill out the values under Option 1, Option 2, Option 3 and so on. When a visitor picks an option, the value you enter here will be added to their Profile as a value for the Attribute (or as Profile Event data, if saved as Form response only).


Results: Populated Profile

Stored as an Attribute

When the Radio element is mapped to an Attribute (for example, Gender), the selected value appears directly on the Profile — usable in Segments, for personalisation, and for branching Marketing Automation flows.

Stored as Form response only

If the Radio element is mapped to Form response only, the value is saved as Event data. Find it in Profile view under Form & Page Interactions — click the Submit activity in the timeline.


Use cases

Lead nurturing — how did you hear about us

Classic acquisition question. Four or five likely channels, plus the Other option toggle for anything unusual. Map to a Source Attribute. Over time, the pattern of answers helps you understand where your best-quality leads actually come from — which informs marketing spend.

Retention — role or segment confirmation

When Profiles visit a preference centre, a Radio asking "Which best describes you?" (e.g. Parent / Professional / Student / Other) lets you update segmentation without overwhelming the visitor. Use Required if the answer is essential for later personalisation.

Brand building — campaign-specific single-select

For a campaign Form, ask "Which product are you most interested in?" with a Radio listing your top categories. Only one answer helps the follow-up communications stay focused rather than trying to cover everything.

Loyalty — single-choice preferences

For a loyalty programme sign-up, use Radio for preferences that must be singular — preferred contact time (Morning / Afternoon / Evening), preferred language, preferred store. Map each to the right Attribute so communications can honour the preference.


Common mistakes & how to troubleshoot

Visitors want to select more than one option

Cause. You used Radio where Checkbox was the right element. Radio enforces single-select.

Fix. Swap to the Checkbox element if multiple selections should be possible.

The "Other" text field doesn't appear

Cause. The Other option toggle isn't activated.

Fix. In the Style panel on the right, switch Other option on. Visitors will then see an extra radio choice with a text field attached.

Visitors leave the question blank

Cause. Required field isn't toggled on. Radio doesn't force a selection unless you require it.

Fix. Toggle Required on if the answer is genuinely needed. Otherwise, accept that some submissions will leave it blank.

The selected value on the Profile doesn't match what the visitor picked

Cause. The visible label in the Canvas and the Option value in Mapping aren't consistent. They're set separately.

Fix. Make sure each option's visible label and its Mapping value match up.

For a wider set of Form issues, see Forms & Pages: Troubleshooting.


💡 Tips & tricks

  • Radio for single-select, Checkbox for multi-select. The single most important design call.

  • Enable Other when you can't list everything. For questions like "industry" or "how did you hear about us", Other avoids forcing visitors into the wrong bucket.

  • Keep option counts manageable. 3–6 radio options is comfortable. More than that, consider a Dropdown instead — radio with 15 options looks like a wall.

  • Align labels with Mapping values. Always double-check that the visible text matches the saved value before publishing.

  • Always name your Radio element. The internal name appears on every Profile's Form – Submit Event. A named field shows as Gender-[ID]; an unnamed one shows as the uninterpretable none-[ID]. Makes the Profile timeline far easier to read.

  • Use Required thoughtfully. Required fields increase drop-off. Make the trade consciously based on how important the answer is.


Next steps

Did this answer your question?