Skip to main content

Web app model

Guest-facing web apps are built from a landing page and its ordered tiles. Published content opens in the guest experience as a responsive grid of modules.

Core concepts​

Landing page shell​

  • Holds ordered tiles, presentation and branding choices, multilingual text, optional domains or slugs, and the owning organization.
  • The guest experience turns this setup into the interactive layout shown to visitors.

Tiles​

  • Each tile has a type (see /reference/tile-types) and a size that influences grid placement and whether navigation opens a fuller experience.
  • Tiles may link to modules such as events lists, offers, recommendations, chats, media galleries, and flash screens, depending on type.

Visits and engagement​

  • Landing-level visits measure opens of the experience.
  • Tile-level interactions measure taps into deeper flows where instrumentation exists for that tile type.

Typical guest flow​

flowchart LR
  guest["Guest opens link or QR code"] --> load["Load published landing page"]
  load --> layout["Responsive tile layout"]
  layout --> modules["Tile modules"]
  1. The guest opens the published landing page from a link, QR code, embed, or short link.
  2. Scoutello loads the version that matches the guest context and language where possible.
  3. The layout engine places tiles into the responsive grid.
  4. Each tile renders either an embedded surface or navigation into a focused screen.

Some tiles keep guests inside the landing navigation context, especially nested pages or embedded modules. If a module opens the wrong destination, verify publishing, embedding settings, and allowed domains for the parent page.

Stand-alone tile embedding​

Teams can expose a single tile in isolation, for example when an external marketing site should embed one module full-width without the surrounding landing grid.

Nested landing navigation​

Landing page tiles can open another linked landing page inside the guest flow. That enables hierarchies such as Overview → Speakers → Venue map without duplicating chrome.

Cross-organization reuse has tenancy implications—only publish links your organization's policies allow.

Many discovery tiles surface map/list experiences with saved filters or anchors. Support teams should verify whether a tile is configured as embedded (stays on the landing grid) or as card-sized navigation (opens the fuller guest view), because symptoms differ when diagnosing layout or navigation issues.