Two events go live on the same day. One gets 250 people scrolling past it in your embedded calendar. The other gets 40 people arriving straight from a shared link. Which one is doing better?

A standard calendar plugin or a default Google Analytics setup can’t answer that, because it reports a single number — views, or hits, or visits, whatever it’s called. That number can’t tell you whether someone scrolled past a poster and clicked, or arrived with intent from somewhere else entirely. Those are different behaviours, and treating them as the same thing means optimising blind.

Revisual’s event engagement reporting splits that number apart automatically. No setup, no custom tracking, no analytics configuration — it’s on by default for every event, on every plan. This article walks through the event metrics behind the report and how to read them.

The Core Event Metrics: Impressions and Views, Defined

Impressions count every time someone clicks or opens an event’s card inside an embedded calendar widget on your website. This is browsing behaviour — someone was scrolling your calendar, a title or image caught their eye, they opened it.

Views count every time someone lands directly on an event’s own page from anywhere else: a direct link, a QR code scan, or an email click. This is arrival with more specific intent — someone already knew, at least roughly, what they were coming to look at.

Neither number is “better.” They measure different things. An impression tells you how well an event performs inside your calendar. A view tells you whether the event is moving through channels independent of the calendar altogether.

Engagement Ratio: The Event Metric That Actually Tells You Something

Ratio is views divided by impressions, shown as a percentage. It answers one specific question: of the people who saw this event in your widget, how many went further?

• A ratio between 50–100% is generally healthy — a solid share of the people who noticed the event went on to look closer, or arrived independently too.
• Below 50% suggests the event is getting seen but not generating much follow-through — worth a look at the title, image, or description doing the “stopping the scroll” work.
• Above 100% isn’t a bug. It means views are outpacing impressions, which happens when direct links, email, or QR traffic are doing real work independent of the widget.
• Zero impressions shows ratio as “—”, since there’s nothing to divide.

Event Communication Reporting by Channel: Widget, Direct, QR, Email

Every impression or view is attributed to exactly one source:

• Widget — clicked from an embedded calendar widget (an impression)
• Direct — visited via a direct link (a view)
• QR — visited by scanning a QR code (a view)
• Email — visited via a link in an email (a view)

This is where the report earns its keep. High impressions with low views on a specific event usually points to a presentation problem — the event is being surfaced well but isn’t compelling enough to drive click-through on its own. Low impressions with meaningful views means the event is being found through other channels more than through your embedded calendar — worth checking whether it’s actually included in the widget you think it’s in. A views spike tied to a specific day often lines up with a campaign — a newsletter send, a social post — and is worth cross-referencing against your own send calendar.

Reading the Event Engagement Chart

By default, the chart shows your combined total across every event in whatever date range you’ve selected, stacked and colour-coded by source.

Click any event in the table below the chart, and its own numbers overlay on top of the aggregate — a dimmed background for everyone, a highlighted line for the one you picked. If that event’s numbers are too small to read clearly against the total, Focus view splits it into two separate charts on their own scales instead.

One detail worth knowing before you draw conclusions: the date range filters by when the engagement happened, not by when the event itself is scheduled. An upcoming event can already show engagement if people are viewing or sharing it early. A long-past event can show nothing if the window you’ve selected doesn’t cover when anyone actually looked at it. If a number looks wrong, widen the range before assuming something’s broken.

The Event Metrics Table: Impressions, Views, and Status

Every event gets a row: impressions, views, ratio, a status pill (Ended, Ongoing, or Upcoming), and a small trend sparkline showing the shape of its activity across the range. Sort by any column — sorting and pagination apply to your full filtered dataset, not just what’s on screen.

The status pill is based on today’s date against the event’s own schedule — it’s tracked separately from whatever date range you’ve picked for the report. That’s deliberate: engagement and event timing are two different questions, and conflating them would hide exactly the pattern worth noticing — pre-event interest building on something that hasn’t happened yet.

Event Engagement Reporting, Built In, Not Bolted On

None of this requires more effort on your part. The split is the default, on every event, the moment it’s published. What changes is what you can actually see: not just that people showed up, but whether they were browsing or arriving on purpose — and which of your channels is doing the work to get them there.

You can find the full report from your dashboard’s Event engagement widget, or directly under Reports → Event Engagement in the main navigation.