Skip to main content

Web app model

Guest-facing web apps are built from a landing page record together with its ordered tiles. Published content loads as one payload for the guest shell, then renders 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 relationships to the owning organization.
  • The guest experience turns this payload 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_browser] --> route["Guest route"]
  route --> load["Load published landing payload"]
  load --> layout["Responsive tile layout"]
  layout --> modules["Tile modules"]
  1. The guest opens the landing URL (paths are shaped like /landing/{landingPageId}; locale handling follows your deployment configuration).
  2. The guest shell loads the published landing payload with the caller context appropriate for anonymous or signed-in guests.
  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 adjust links so guests remain inside the landing navigation context (nested shells, embedded roots, or absolute hosts for iframe-style embeds). If a module appears to open the wrong host or path, verify publishing, embedding settings, and the parent page allowed domains policy.

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) versus card-sized navigation (opens the fuller guest shell), because symptoms differ when diagnosing layout or routing issues.