Layout sizing and visibility
Sizes and layout
| Size | Behavior summary |
|---|---|
embedded | Inline module inside the landing grid—ideal for always-visible snippets. |
small / medium / large | Card footprints that usually navigate into deeper experiences when tapped. |
If historical data contains an unsupported size, the guest runtime may coerce layout. Re-save tiles from the dashboard when previews look inconsistent.
Embedded versus routed
Embedded modules keep guests on the landing surface (polls, FAQs, compact chats). Routed modules open focused screens when interactions need full height, cameras, or heavier media.
See each tile playbook under /product/landing-pages-and-tiles/tiles/—some tiles branch (for example pinning a single event while hiding broader toggles).
Scheduling and activity flags
Across many tiles the dashboard exposes:
showFrom/showTo— calendar windows independent of weekly opening hours.- Active mode (
yes,no,certainTimes). - Opening-hours linkage when venues need parity with physical hours.
showWhenClosedmessaging when guests should see explanatory copy instead of silence.
Support pattern: When guests say a tile vanished, compare device time zones with configured schedules before assuming content deletion.
Visibility inside grids
Tiles respect composite rules: schedule windows, inactive overlays, optional IP allowlists, administrator previews, and organization-level network restrictions that can lock modules until guests join trusted Wi-Fi or VPNs.
Document restrictions in FAQs whenever they apply (for example “Connect to venue Wi-Fi to unlock this brochure”).
Geo-fencing style locks
Some tiles support optional radius locks around coordinates, common for sponsor PDFs, onsite chats, or galleries meant only for visitors physically nearby. Treat these as proximity prompts, not cryptographic guarantees.
Incident triage quick table
| Report | Steps |
|---|---|
| Tile greyed out or inactive banner | Inspect schedule plus inactive messaging surfaced in the dashboard preview. |
| Works on mobile data but not venue Wi-Fi | Organization IP restrictions or captive portals blocking authentication cookies. |
| Desktop renders while embedded iframe stays blank | Parent site Content Security Policy or blocked third-party scripts—capture browser diagnostics sparingly and per privacy policy. |
Related: Web app model, Analytics and support, Tiles index.