Landing pages and tiles
A landing page in Scoutello is a configurable guest web app: a localized page assembled from ordered tiles (modules). Teams publish landing pages behind short links or QR flows; guests open them in a mobile browser for the typical journey.
Each landing page is stored as structured content together with its tiles. The dashboard exposes authoring controls, and guests receive a responsive layout that loads the published modules together.
Concepts
Guest web app (landing page)
- Landing page: organization-scoped experience shell with its own slug or domain options, visuals, multilingual text, tiles, presentations, analytics, and optional assistant context.
- Runtime: Guests open landing pages in the browser-first guest app—for example paths shaped like
/landing/{id}—which loads the published payload and lays out tiles in a responsive grid. - Distribution: Typical entry is URL, QR code, or share link; teams may tie landing pages to widgets, marketing pages, or other entry points documented in /reference/routes.
Tile
Each tile has:
- A type that selects behavior (for example events, stops, tours, quizzes—see /reference/tile-types).
- A size (
small,medium,large, or embedded for inline modules). Size affects layout on the landing grid and whether navigation opens a fuller screen experience where relevant. - Optional links to backing content such as a quiz, chatroom, voting view, site plan, or gallery—depending on tile type.
Tiles can behave as:
- Click-through cards that navigate to dedicated experiences (quiz, site plan, explore-style lists, external URLs, and similar).
- Embedded surfaces that render inside the landing grid (embedded events, chat snippets, FAQs, newsletters, polls, and more).
Tile interactions can record engagement for analytics where that tile type supports it.
Nested landing (landingPage tile type)
Tiles of type landing page can navigate to another published landing page inside the same guest experience. That supports multi-section navigation and sub-experiences without rebuilding the outer shell.
Single-tile embed
Teams can share a standalone tile URL so only one module appears fullscreen. This is useful when an external site should embed a single capability (poll, newsletter signup, gallery, and similar) without the full landing grid.
Relationships to other product areas
| Area | Relation |
|---|---|
| Tours | Tour tiles bridge into the tour experience from the landing grid. |
| Events | Event tiles surface calendars or pinned events and tie into explore-style discovery where configured. |
| Places / stops | Stop tiles surface recommendations (“places”), often paired with site plans or tours. |
| Offers, contact forms, site plans | Dedicated tile types link into offer flows, contact submissions, or site plans. |
| CRM / newsletters | Newsletter tiles surface subscription flows tied to CRM and mailing lists. |
| Permissions | Dashboard authoring is organization-scoped; see /reference/permissions. |
Where to read next
- Architecture and authoring flow: /product/landing-pages-and-tiles/web-app-model, /product/landing-pages-and-tiles/authoring-and-publishing
- Layout, sizes, schedules, restrictions: /product/landing-pages-and-tiles/layout-sizing-and-visibility
- Visits and support: /product/landing-pages-and-tiles/analytics-and-support
- Per-tile notes: /product/landing-pages-and-tiles/tiles/text and sibling pages under Tiles (one page per active tile kind where documented)
- Compact catalog: /reference/tile-types
- Dashboard guides: /dashboard/web-apps-and-tours/landing-pages, /dashboard/web-apps-and-tours/tile-reference
Related concepts: Browser-first guest app, Multilingual content, Dashboard landing pages.