The customer activation platform.Every interaction becomes a qualified contact. Book a demo

Landing Page reference

Check landing page asset guidance, section options, validation rules, and multi-language behavior.

This reference gathers the current landing page rules in one place: shared structure, asset guidance, layout behavior, and validation scope.

Shared structure

Landing page activation is intended for campaigns with at least two active Touchpoints. Once enabled, the page is built from a shared set of sections:

SectionPositionVisibility optionsDisplay style options
Header SectionFixed firstAlways shown in the landing page editorNone
Rewards SectionReorderable middle sectionCan be shown or hiddenDefault, Carousel, or List
Activities SectionReorderable middle sectionCan be shown or hiddenDefault, Carousel, or List
Games SectionReorderable middle sectionCan be shown or hiddenDefault, Carousel, or List
Interactive Totems SectionReorderable middle sectionCan be shown or hiddenNo alternate display style
Instructions SectionFixed near the endAlways shown in the landing page editorNone
CTA SectionFixed lastCan be shown or hiddenNone

Header Section always anchors the page. Instructions Section stays near the end, and CTA Section stays last. The listing sections sit between them and can be reordered.

Asset guidance

AssetCurrent guidanceRecommended formatsNotes
Header banner900 x 600 px (3:2) in the current See Specs panelJPEG, WEBP, PNGUse a landscape image and keep the file lightweight.
Instruction icon400 x 400 px (1:1)JPEG, WEBPUse a consistent icon style across every instruction item.
Advent Calendar day imagesMatching square images for every dayWeb-friendly image formatsPrepare one Closed Image and one Open Image per active day.

Header fields

The shared header controls:

  • Banner
  • Title
  • Subtitle
  • Hide Participation Button
  • Hide Rewards and Legal Buttons

Title and the banner are required for a complete landing page header. Subtitle is recommended and surfaces as a validation warning when left empty.

CTA rules

The landing page CTA is designed for external destinations, not for opening an internal Touchpoint.

FieldWhat it doesShared or translated
CTA TitleAdds context above the buttonTranslated per campaign language
CTA LabelSets the button textTranslated per campaign language
CTA URLSets the destinationShared across languages

A working CTA should include all three fields. The current validation also checks that the URL starts with http:// or https://.

Responsive behavior

LayoutBehavior
One columnStays in a single vertical flow on every screen size.
Two columnsUses the split desktop view from the current desktop breakpoint (min-width: 1224px). Below that breakpoint, it collapses to one column.
Advent CalendarUses a centered, responsive grid. The current page styling constrains the body width and the tile grid auto-fits items with a minimum tile width of roughly 100px.

Multi-language behavior

The landing page builder supports per-language content on the text fields that use the Studio language selector.

Field groupMulti-language support
Header Title and SubtitleYes
Instruction item Title and SubtitleYes
CTA Title and CTA LabelYes
Header banner, instruction icons, Advent Calendar images, CTA URL, section order, section visibilityShared across languages

Text-length guidance

The current landing page validation does not expose dedicated character-limit rules for the header, instruction items, or CTA text fields. In practice, the safest approach is to keep copy short enough to scan:

  • keep header titles to one clear line where possible
  • keep CTA labels brief enough to fit on a button comfortably
  • keep instruction titles action-oriented and use the subtitle for supporting detail

Validation groups

Landing page validation currently focuses on four areas:

AreaWhat it checks
HeaderMissing header, title, background image, and subtitle
InstructionsMissing instruction titles, subtitles, and icons
CTAMissing label or URL, invalid URL, missing title when a CTA is otherwise configured, title-only CTA
Advent CalendarMissing configuration, empty calendar, inactive calendar, missing images, missing or invalid linked Touchpoints, missing date overrides, overlapping date ranges

See Validation & publishing for the publish-time workflow around these checks.

Was this helpful?

Optional comments help us improve this page for future authors and readers.

On this page