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:
| Section | Position | Can be hidden? | Display styles |
|---|---|---|---|
| Header | Fixed first | No, always shown | None |
| Rewards | Reorderable middle section | Yes | Default, carousel, or list |
| Activities | Reorderable middle section | Yes | Default, carousel, or list |
| OmniLab Games | Reorderable middle section | Yes | Default, carousel, or list |
| Interactive Totems | Reorderable middle section | Yes | None |
| Instructions | Fixed near the end | No, always shown | None |
| Call to action | Fixed last | Yes | None |
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
| Asset | Recommended size | Recommended formats | Notes |
|---|---|---|---|
| Header banner | 900 x 600 px (3:2) | JPEG, WEBP, PNG | Use a landscape image and keep the file lightweight. |
| Instruction icon | 400 x 400 px (1:1) | JPEG, WEBP | Use a consistent icon style across every instruction. |
| Advent Calendar day images | Matching square images for every day | Web-friendly image formats | Prepare 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.
| Field | What it does | Shared or translated |
|---|---|---|
| Title | Adds context above the button | Translated per campaign language |
| Label | Sets the button text | Translated per campaign language |
| URL | Sets the destination | Shared across languages |
A working button needs all three fields. Publishing also checks that the link starts with http:// or https://.
Behavior across screen sizes
| Layout | Behavior |
|---|---|
| One column | Stays in a single vertical flow on every screen size. |
| Two columns | Shows the side-by-side view on wide desktop screens (about 1224 pixels and up). On narrower screens, it stacks into one column. |
| Advent Calendar | Uses 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 group | Multi-language support |
|---|---|
| Header title and subtitle | Yes |
| Instruction title and subtitle | Yes |
| Call-to-action title and label | Yes |
| Header banner, instruction icons, Advent Calendar images, call-to-action link, section order, section visibility | Shared 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:
| Area | What it checks |
|---|---|
| Header | Missing header, title, banner, or subtitle |
| Instructions | Missing instruction titles, subtitles, or icons |
| Call to action | Missing label or link, invalid link, missing title when a button is otherwise set up, title with no button |
| Advent Calendar | Missing 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.