Skip to main content

​
Analytics Views Reference

Linquid analytics is scope-based. Always confirm scope and date filters before interpreting numbers.

​
Workspace analytics

Primary tab families:
  • Clicks
  • Leads
  • Sales
  • Funnel
Workspace-level views also include:
  • geographic distribution
  • device/browser/OS breakdown
  • top campaigns
  • top links/tags/folders
  • budget and quality summaries
Workspace analytics is your top-level health view and should be used for trend and anomaly detection first. It also acts as the primary “unified” view where teams align on a single current workspace baseline before drilling into campaign/link detail.

​
Workspace tab matrix

​
Workspace cards and panels

Typical panels include:
  • KPI cards for selected tab
  • date range selector and refresh controls
  • geography, device, browser, and OS distribution
  • top campaigns and top links tables
  • tags/folders contribution views
  • quality and anomaly insight cards

​
Campaign analytics

Campaign pages generally include:
  • overview KPIs
  • campaign time trends
  • link contribution tables
  • rule contribution tables
  • funnel and conversion slices (plan-gated)
Campaign details commonly expose additional tabs for:
  • overview
  • links inventory
  • rules inventory
  • analytics
  • SDK/instrumentation (plan-gated)

​
Campaign analytics expectations by tab

Link deep-dive typically includes:
  • overview traffic and trend cards
  • geography and city-level views
  • device/OS/browser/source views
  • rules performance and routed/unrouted flow
  • conversion performance views
  • advanced flow/path views
Common link analytics tabs:
  • overview
  • traffic
  • technology (plan-gated)
  • deep links (requires deep-link enabled on the link)
  • rules
  • conversions (plan-gated)
  • security/fraud (plan-gated)
  • advanced click paths

​
Conversions, Events, and Customers pages

These pages serve different needs:
  • Conversions: aggregate conversion performance and source mix.
  • Events: event-level operational stream.
  • Customers: identity-level summaries and value history.
Page intent differences:
  • Conversions: KPI and source composition
  • Events: sortable event log for operational triage
  • Customers: person/account-level CRM-style analysis

​
Page-level operational matrix

​
Empty state interpretation

​
Affiliate analytics

Affiliate analytics focuses on:
  • partner performance
  • commission outcomes
  • payout efficiency
  • fraud/risk signals
Affiliate analytics commonly includes:
  • overview
  • partner rankings
  • ROAS/financial performance

​
Wrapped and recap-style reporting

For recap or “year in review” style summaries:
  • treat them as presentation layers over core analytics data
  • use standard exports/analytics views for reconciliation-grade validation
  • align timeframe and currency before sharing externally

​
Reconciliation order when numbers differ

  1. Confirm same date range and timezone.
  2. Confirm same scope level.
  3. Confirm same event status filters.
  4. Confirm same currency context.
  5. Use exports for final cross-check.

​
Common discrepancy causes

  • comparing workspace totals with filtered campaign/link scope
  • mixing pending and approved conversion statuses
  • mixing partner-attributed metrics with workspace-wide metrics
  • comparing different currencies without aligned conversion context
  • hidden plan-gated tabs/widgets interpreted as missing data
  • stale filters applied in one view but not another
  • scope mismatch (workspace versus campaign versus one link)

​
Export usage

Use exports for:
  • finance reconciliation
  • partner payout validation
  • incident audits
Related:
  • /user-guides/manual/data/conversions-customers
  • /user-guides/manual/data/exports-and-operational-checks