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
- geographic distribution
- device/browser/OS breakdown
- top campaigns
- top links/tags/folders
- budget and quality summaries
Workspace tab matrix
| Tab | Primary questions answered | Typical follow-up action |
|---|---|---|
| Clicks | How much traffic arrived, from where, and with what quality? | Open top links/campaigns and inspect source quality |
| Leads | Are lead outcomes rising/falling and from which channels? | Open conversions/events to inspect status and source mix |
| Sales | Is revenue trending with expected cost and ROI behavior? | Validate campaign cost model/currency context |
| Funnel | Where is drop-off between click, lead, and sale stages? | Open campaign/link scope to isolate bottlenecks |
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)
- overview
- links inventory
- rules inventory
- analytics
- SDK/instrumentation (plan-gated)
Campaign analytics expectations by tab
| Tab | What should be true when healthy |
|---|---|
| Overview | Campaign-level KPIs reconcile with selected date range |
| Links | Top link rows explain campaign totals directionally |
| Rules | Rule-level contribution reflects active routing logic |
| Analytics | Trends and breakdowns align with campaign scope only |
| SDK/Instrumentation | Tracking setup status matches campaign conversion strategy |
Link analytics
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
- 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
Link analytics expectations by tab
| Tab | What should be true when healthy |
|---|---|
| Overview | Link KPIs align with traffic volume and status |
| Traffic | Source, geo, and trend views are coherent with click volume |
| Technology | Device/OS/browser splits are plausible for campaign audience |
| Deep links | Deep-link intents/fallback behavior reflect link config |
| Rules | Routed versus fallback traffic distribution is explainable |
| Conversions | Conversion events and value align with ingestion sources |
| Security/Fraud | Threat signals are low or explainable with mitigations |
| Click paths | First-page path list loads quickly and matches major destinations |
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.
- Conversions: KPI and source composition
- Events: sortable event log for operational triage
- Customers: person/account-level CRM-style analysis
Page-level operational matrix
| Page | Primary cards/tables | Operator outcome |
|---|---|---|
| Conversions | lead/sale/custom counts, source mix, value context | confirm conversion pipeline health |
| Events | event timeline, status, source, value columns | triage ingestion issues quickly |
| Customers | customer list, value/lifecycle context, activity history | validate customer-level attribution and quality |
Empty state interpretation
| Surface | Empty state can mean | First check |
|---|---|---|
| Workspace/Campaign/Link analytics tab | no data in selected range or gated feature | date range, scope, plan gate |
| Conversions page | no qualifying conversion events | source integration status and event filters |
| Events page | no events ingested for filters | tracking setup and filter constraints |
| Customers page | customer identity stitching not triggered yet | event payload identity fields |
Affiliate analytics
Affiliate analytics focuses on:- partner performance
- commission outcomes
- payout efficiency
- fraud/risk signals
- 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
- Confirm same date range and timezone.
- Confirm same scope level.
- Confirm same event status filters.
- Confirm same currency context.
- 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
/user-guides/manual/data/conversions-customers/user-guides/manual/data/exports-and-operational-checks