Analytics

The Analytics screen shows how visitors interact with your Showcase walls. You can track sessions, individual leads, content engagement, and export the underlying data to CSV files or to an external webhook for integration with CRM and automation tools.

Data is captured by the Showcase player as visitors use personal markers, open widgets, view PDFs, play videos, and submit contact forms. Each event is attached to the visitor's identity (if known) and to the active application session, so you can reconstruct an entire visit from start to finish.

The Analytics Overview

Click Analytics in the left-hand menu to open the dashboard. Four summary cards at the top show the current totals: Leads (identified or anonymous visitors), Sessions (application runs), Events (all captured interactions), and Contacts (submitted contact forms).

Four tabs below the summary cards let you drill into the data:

• Leads — one row per visitor, with expandable event history.
• Sessions — one row per application run, with expandable timeline.
• Content — aggregated engagement per widget and event type.
• Export — CSV downloads and webhook configuration.

Use the Refresh button in the top right to reload all data on demand.

Browse Leads

The Leads tab lists every visitor the system has seen, sorted by activity. Registered visitors (those who submitted a contact form) show a name and email; visitors who only used a personal marker appear as Anonymous.

Analytics screen, Leads tab. Summary cards along the top; lead table below with filter controls.

Follow these steps to investigate a specific lead:

1. Use the filter dropdown above the table to show All identities, Registered only, or Anonymous only.
2. Select the Hide staff checkbox to exclude identities that have been flagged as internal staff. Staff visits typically come from testing, setup and demo walkthroughs, and will skew public-facing metrics if left in.
3. Click any row to expand it. The expanded view shows every event the visitor triggered — the time, event type, the widget or asset involved, and the application where the interaction happened.

Leads tab with a lead expanded to show the full event history, including widget views, PDF page views and email submissions.

1. To mark a visitor as staff, click the dash (—) button in the Role column and choose Staff. The lead will be hidden whenever the Hide staff filter is active.

Tip

Flag your own testing marker as Staff as soon as your wall goes live. This stops rehearsal runs and setup-day activity from inflating your engagement numbers.

Browse Sessions

The Sessions tab shows one row per application run. A session starts when the Showcase player launches an app and ends when the app is closed or switched.

Analytics screen, Sessions tab. Each row is one application run on one device.

Each row shows the application name, the device that was running it, the start and end times, and the number of events captured during the session.

Click a row to expand the session timeline. The timeline lists every event in chronological order, together with the widget involved and — where a personal marker was used — the identity of the visitor.

Session expanded to show its timeline: widget openings, asset views, video play/stop markers and identified visitors.

Tip

Use session timelines to understand a single visit end-to-end, for example during a scheduled demo or customer meeting. They are also useful for diagnosing content that visitors open but never interact with.

Analyse Content Engagement

The Content tab aggregates events across all sessions to show which content is being used and how often.

Analytics screen, Content tab. Event type breakdown across the top, content engagement table below.

The Event Type Breakdown cards show how often each kind of event has occurred across the whole wall — for example, how many widgets have been opened, how many PDFs have been viewed, or how many videos have been started.

The Content Engagement table lists each widget together with the event types it has generated. For each row you see:

• Widget ID — the reference for the widget or asset.
• Event Type — the kind of interaction.
• Count — total number of events.
• Unique Markers — how many distinct visitors produced the events.
• First Seen and Last Seen — the time range over which the events were captured.

Tip

The gap between Count and Unique Markers is useful signal. A widget with a count of 12 from 12 unique markers is broadly interesting; a widget with a count of 30 from two markers is usually being driven by staff or by a single returning visitor.

Export Data

The Export tab lets you download captured data as CSV files or push it to an external system via a webhook.

Analytics screen, Export tab. CSV download buttons at the top, webhook configuration below.

Download CSV Files

CSV files can be opened directly in Excel, Numbers, Google Sheets, Tableau or PowerBI, and they can be imported into most CRM systems.

Three downloads are available:

• Download Leads — one row per identified or anonymous visitor, with totals and the most recent activity time.
• Download Events — the full event log, one row per event.
• Download Sessions — one row per application run.

Click a download button to save the corresponding file to your computer.

Configure a Webhook

You can POST every new event to an external URL as it happens. This is the fastest way to connect Showcase to automation platforms such as Zapier, HubSpot, Salesforce or a custom CRM.

Follow these steps:

1. Enter the destination URL that will receive the POST requests.
2. (Optional) Add an Authorization Header — for example, Bearer your-token-here — if the receiving service requires authentication.
3. Click Save to store the configuration.
4. Click Send Test to POST a sample payload and verify that the receiving service is reachable. A success or failure message is shown directly on the screen.
5. When you are ready to start delivery, select the Enable webhook delivery checkbox and click Save again.

Tip

Always run Send Test before enabling delivery. A misconfigured URL or a missing authorization header is the most common reason for a newly-connected webhook to silently drop events.