Use this learning path to find the current Forms and Interactive components and to apply a safe, repeatable configuration workflow.
What is the Ion Palette and how does it work?
Open Add elements, choose a component, and drag it onto a valid page target. Select the new element, then configure its Design and Settings panels. Verify the intended viewport before styling.
Forms: components
The Forms group contains form containers, choices, input controls, and submit controls. Use the component that matches the data and interaction requirement; do not collect fields that the launch does not need.
Forms: creating a form in Ion
Add the form container first, then add fields and the submit control. Map each input to the intended data field, mark required fields deliberately, and provide clear labels and error text.
Forms: advanced settings
Review validation, behaviors, actions, rules, integrations, conversion logic, consent, and the success destination. Test valid, invalid, duplicate, and edge-case submissions in every intended viewport.
Forms: using Choice for engagement
Use Choice when respondents should select from controlled values. Keep the displayed label, saved value, data mapping, and any rule conditions aligned.
Interactive components
The current Interactive group includes Lightbox, Reveal, Flow, Accordion, Tabs, Video, and other components. Choose the simplest component that delivers the intended behavior.
Lightbox and Reveal
For Reveal, select overlay or toggle behavior, choose click or hover deliberately, and verify mobile behavior. For Lightbox, test open/close controls, focus movement, keyboard access, and responsive size.
Flow and inherited Rotator experiences
For Flow, review navigation, auto-play, looping, fixed height, and step behavior. If an inherited creative still uses a legacy Rotator, test it in place before replacing it; do not assume the current Flow settings are identical.
Accordion and Tabs
Give every item a meaningful label, confirm the intended initial state, and test keyboard, tracking, and responsive behavior. Do not hide required information behind an inaccessible interaction.
Video and full-page interactions
Use an approved video source and verify playback, captions, poster/fallback behavior, and mobile sizing. If an inherited experience uses a full-page slider, test its navigation, focus order, and escape path before launch.
Final verification
Preview the experience, then test the final public URL with representative devices and data. Confirm interactions, submissions, integrations, accessibility, analytics, and rollback before opening traffic.
