Tile reference
Tiles are created per landing page using the dashboard tile editor. Allowed tile kinds, labels, categories, and sizes stay aligned with the catalog described in /reference/tile-types.
Catalog concepts
| Concept | Meaning |
|---|---|
| Type | Machine name persisted with the tile—select from the picker. |
| Label | Operator-friendly name shown in authoring tools (localized where applicable). |
| Category | UX grouping such as basic, tour-centric, or advanced—helps teams browse quickly. |
| Sizes | small, medium, large, or embedded, depending on what the tile supports. |
| Navigation helper | Some tiles compute default links for card-sized modules (external URLs, exploration screens, tours, etc.). |
If historical data contains an unusual size, the guest runtime may coerce layout—re-save with an allowed size to avoid confusion.
Embedded versus routed tiles
- Embedded tiles render inline on the landing grid when the tile supports that mode.
- Card sizes typically navigate into focused guest screens or curated exploration views.
Train operators with a simple rule: embedded stays on the landing page, card sizes open the wider guest shell.
Common tile settings
Many tiles share optional controls such as:
- Schedule windows controlling when a tile appears.
- Activity states (always on, closed messaging, time-based availability).
- Visual styling options where product design exposes them.
- Geo or audience restrictions on qualifying tile kinds—see /product/landing-pages-and-tiles/layout-sizing-and-visibility.
Commercial guarantees about locks such as sponsor PDF geo-fencing still belong in contracts—not inferred solely from technical capability lists.
Type-specific notes
Deep playbooks live under /product/landing-pages-and-tiles in the Tiles section. Use those pages when guests report nuanced runtime behavior.
At a glance:
| Tile family | Dashboard focus |
|---|---|
| Text | Rich content blocks and styling. |
| External URL | Validate destinations and embedding policies. |
| Link uploads; confirm translations toggles when locales matter. | |
| Nested landing | Pick child landing experiences and thumbnails; watch geo policies when applied. |
| Tour | Bind published tours; optional shortcuts that skip detail screens. |
| Members | Ordered profiles with optional grouping tags. |
| Chatroom | Moderation posture—anonymous posting, reactions, retention. |
| Stop recommendations | Map/list defaults and pinned highlights. |
| Events | Own versus curated feeds; embedded versus navigational behavior. |
| Offers | Pinned promotions versus broad catalogs. |
| Voting | Embedding-only modules—ensure voting content is published. |
| Networking | Dating versus networking modes, profile gates, discovery windows. |
| Media gallery | Upload moderation, camera-only policies, optional geo locks. |
| Flash screens, quizzes, and specialty tiles | Each product page lists prerequisites. |
Duplicate workflows
Copying complex tiles speeds up campaigns. After duplication, scrub moderation text, legal copy, secrets, or raffle rules so clones do not inherit stale compliance language.
When to escalate
- Suspected abuse spanning organizations (phishing links, illicit uploads) → follow your organization's security escalation policy.
- Payment or tour anomalies → /product/tours/support-playbook.
Related concepts: Landing pages, Reference tile types, Product landing pages hub.