Tours — landing pages & tiles

Landing page association

In the tour editor, teams can bind a landing page so branding, accent colors, and navigation context stay consistent when guests jump between tours and hosted web apps.

Tour tile

See /reference/tile-types for the authoritative catalog row. In practice:

• Choose the linked tour record inside the tile editor.
• Prefer card sizes (large, medium, small)—embedded hosting is uncommon for tours.
• Paths from tour tiles resolve to /tours/{tourId} in the guest app (additional segments appear when a guest continues an active session). When the guest started from a landing page, URLs may be nested under /landing/{landingPageId}/…—compare the preview link from the dashboard with printed collateral if a mismatch is reported.

Optional skip details configuration sends guests deeper into the runtime when the experience needs a faster path than the standard storytelling screen.

Companion tiles

Tour-heavy landing stacks often pair with:

• Site plan tiles for indoor orientation.
• Stop tiles for curated place browsing aligned with recommendations.
• Event, offer, media gallery, quiz, chatroom, networking, alerts, or newsletter tiles for engagement or conversion—each documented under /product/landing-pages-and-tiles/tiles/.

End screens

Tour end screens can surface offers, polls, related tours, or recommended stops so a guided session can finish with commerce or feedback prompts without custom engineering per customer.

Support notes

If a tour tile appears blank, confirm the tile still references a published tour with compatible visibility. If links differ between tile entry and manual URLs, compare the preview link from the dashboard with what marketing printed on collateral.

Related: Tile types reference, Landing pages dashboard guide, Tours overview.