Analytics and support

Telemetry overview

Signal	Typical meaning
Landing visits	Guests opened the landing experience; use this for campaign reach and bounce patterns.
Tile interactions	Guests engaged with individual modules; use this to inspect funnels inside one landing session.

Treat analytics as potentially sensitive when combined with identifiers, coarse location, or authenticated sessions. Follow your organization's privacy policies when discussing metrics externally.

Debugging workflow

1. Reproduce guest context

Collect device type, locale, timezone, whether the guest was signed in, and whether connectivity passed through captive portals or restrictive networks.

2. Confirm published content

In the dashboard, verify tiles remain published for the intended schedule, translations exist for the languages guests expect, and linked modules (forms, quizzes, galleries, embeds) are still active.

3. Classify rendering mode

Determine whether the tile should render inline on the landing grid or navigate into a focused guest screen. A mismatch here often appears as a “layout bug” report.

4. Scheduler and visibility rules

Tiles may disappear because of schedule windows, inactive states, or visibility restrictions—not because content was deleted.

Frequently escalated symptoms

Symptom	Things to verify
Blank iframe embed	Parent site blocking scripts; embed URL or sizing mismatches
Poll or vote stuck loading	Voting module unpublished or missing configuration
Gallery uploads failing	Permissions, moderation settings, or storage limits

Escalate internally when an issue reproduces with valid publishing settings and no clear guest-device explanation. Attach timestamps, affected landing or tile identifiers, and concise reproduction notes.

Related: Layout sizing and visibility, Dashboard analytics, Dashboard landing pages.