Landing Page reference

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

Look up the landing page rules in one place: shared structure, asset sizes, layout behavior across screen sizes, and what publishing checks for.

Shared structure

You can enable the landing page once a campaign has at least two active Touchpoints. The page is then built from a shared set of sections:

SectionPositionCan be hidden?Display styles
HeaderFixed firstNo, always shownNone
RewardsReorderable middle sectionYesDefault, carousel, or list
ActivitiesReorderable middle sectionYesDefault, carousel, or list
OmniLab GamesReorderable middle sectionYesDefault, carousel, or list
Interactive TotemsReorderable middle sectionYesNone
InstructionsFixed near the endNo, always shownNone
Call to actionFixed lastYesNone

The header always anchors the page. Instructions stay near the end, and the call to action stays last. The listing sections sit between them and can be reordered.

Asset sizes

AssetRecommended sizeRecommended formatsNotes
Header banner900 x 600 px (3:2)JPEG, 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.
Advent Calendar day imagesMatching square images for every dayWeb-friendly image formatsPrepare one closed image and one open image per active day.

The same banner size appears under See Specs in the header editor.

Header fields

The shared header controls:

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

The title and banner are required for a complete header. The subtitle is recommended; leaving it empty raises a validation warning.

Call-to-action rules

The landing page button is meant for an external destination, not for opening a Touchpoint inside the campaign.

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

A working button needs all three fields. Publishing also checks that the link starts with http:// or https://.

Behavior across screen sizes

LayoutBehavior
One columnStays in a single vertical flow on every screen size.
Two columnsShows the side-by-side view on wide desktop screens (about 1224 pixels and up). On narrower screens, it stacks into one column.
Advent CalendarUses a centered, responsive grid that fits the calendar tiles to the available width.

Working in more than one language

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

Field groupMulti-language support
Header title and subtitleYes
Instruction title and subtitleYes
Call-to-action title and labelYes
Header banner, instruction icons, Advent Calendar images, call-to-action link, section order, section visibilityShared across languages

Text-length guidance

The landing page doesn't enforce character limits on the header, instructions, or call-to-action text. To keep the page scannable:

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

What publishing checks

Publishing checks four areas of the landing page:

AreaWhat it checks
HeaderMissing header, title, banner, or subtitle
InstructionsMissing instruction titles, subtitles, or icons
Call to actionMissing label or link, invalid link, missing title when a button is otherwise set up, title with no button
Advent CalendarMissing setup, empty calendar, no active days, 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