37.1 Reading Analytics Beyond Totals

After reviewing the KPI totals, use the detailed Analytics sections to understand where activity came from and how visitors accessed your campaign assets.

37.2 Performance Over Time

The performance series distributes included events across the selected reporting days. Compare peaks, gaps, and trends with your actual campaign schedule.

A spike is most useful when you can associate it with a known action such as a mailing, social post, print distribution, event, or promotion.

37.3 Top Locations

The Analytics controller builds a country breakdown from recorded event data. The interface presents this as location/country performance.

Use geography to understand where engagement is occurring, particularly for location-sensitive campaigns. Unknown or unavailable geographic values can appear when location information cannot be determined.

37.4 Devices

The Devices breakdown groups activity by recorded device type. This can help determine whether visitors are primarily using mobile, desktop, or other detected device categories.

  1. If mobile dominates, prioritize mobile-first Landing Page design.
  2. If a campaign is QR-driven, expect a strong mobile share in many use cases.
  3. Do not assume device percentages represent the entire customer base; they represent tracked interactions in the selected period.

37.5 Browsers

The Browsers breakdown groups events by detected browser. Use it to identify the browsing environments used to access your campaigns and to guide compatibility testing for high-traffic browsers.

37.6 Recent Activity

The Analytics controller returns up to 12 of the most recent included events. The recent-activity view can show information such as:

  1. Event type
  2. Asset / page name
  3. Associated workspace member email where applicable
  4. Country
  5. Device
  6. Date and time

37.7 Understanding Event Types

EventWhat It Represents
QR scanA supported public QR route was accessed and the QR scan event was recorded.
Short-link clickA Smart Short Link was accessed and the click event was recorded.
Bio page viewAn active public Bio Page was viewed.
Landing page viewA published public Landing Page was viewed.

37.8 Unknown Values

Analytics can display fallback labels such as Unknown country, Unknown device, Unknown city, Unknown member, or Unknown asset when the corresponding value is not available.

An Unknown value does not necessarily mean the interaction failed. It means that the particular reporting dimension could not be populated for that event.

37.9 Country and Device Percentages

Breakdown percentages are calculated relative to the events included by the current filters. Always check the selected range and type before comparing percentages from two reports.

37.10 Using Analytics for QR Campaigns

  1. Filter to QR Code activity.
  2. Choose the desired period.
  3. Review total scans and unique visits.
  4. Check geography and device breakdowns.
  5. Review recent activity.
  6. Compare the results with where and when the QR Code was distributed.

37.11 Using Analytics for Short Links

  1. Filter to Short Link activity.
  2. Review Short-link clicks.
  3. Check device and browser patterns.
  4. Compare performance with the digital channels where the link was shared.
  5. Review UTM strategy in the Short Link configuration when campaign attribution parameters are needed.

37.12 Using Analytics for Bio and Landing Pages

Bio Page and Landing Page filters isolate public page-view activity. Use them to compare page traffic, identify active campaigns, and determine which public destinations are receiving engagement.

37.13 CSV Export Backend Capability

When the backend export workflow is invoked by an enabled interface or integration, the queued CSV job writes these columns:

  1. occurred_at
  2. event_type
  3. country
  4. device
  5. os
  6. browser
  7. referrer

The job stores the completed file and can send an Analytics report email containing the report URL. Because the current Analytics view does not expose a normal export control, this capability should not be treated as a visible subscriber workflow unless the interface is later enabled.

37.14 Making Better Decisions with Analytics

  1. Use comparable date ranges.
  2. Separate asset types before attributing performance.
  3. Look at both total and unique activity.
  4. Connect peaks to known campaign actions.
  5. Use device data to guide page testing.
  6. Use geography when campaign location matters.
  7. Do not interpret incomplete dimensions as failed events.
  8. Avoid making major decisions from a very small sample size.
Write Your Comment