Skip to main content

Analytics and Reporting

Linquid analytics are scope-based and purpose-specific.

Scope levels

  • Workspace analytics: global performance and trends.
  • Campaign analytics: campaign economics and comparisons.
  • Link analytics: routing outcomes and deep traffic behavior.

Scope inheritance model

Use this model when comparing totals:
  • Workspace contains all campaigns and links in the workspace.
  • Campaign is a filtered subset of workspace data.
  • Link is a filtered subset of campaign and workspace data.
If a lower scope exceeds a higher scope for the same filters, treat it as a filter mismatch and re-check view settings first.

Complementary pages

  • Conversions: outcome totals by type/source/status.
  • Events: chronological event stream.
  • Customers: identity-level value and journey context.
  • Affiliate analytics: partner/program efficiency and payouts.

Key metric families

  • Traffic: clicks, unique visitors, redirect time, quality indicators.
  • Outcomes: leads, sales, custom conversion counts.
  • Economics: revenue, cost, ROI, CPA.
  • Rankings: top links, rules, campaigns, partners, and sources.

Date, timezone, and currency discipline

Before comparing pages:
  1. lock the same date range preset or custom window.
  2. confirm timezone context is aligned.
  3. confirm reporting currency is aligned.
  4. confirm status filters are aligned.

How teams typically use each view

  • Growth operators: campaign/link trend and conversion outcomes
  • Performance marketers: cost model and ROI comparisons
  • Revenue operators: conversion status and customer value tracking
  • Affiliate managers: partner rankings, commissions, and payout readiness
  • Leadership: workspace-level trend and risk summary

Freshness expectations

Analytics surfaces may update on slightly different cadences depending on module and query depth. Operator guidance:
  • use built-in refresh controls when validating recent changes
  • expect detailed drill-down tables to lag summary cards in some windows
  • rely on exports for final reconciliation snapshots

Refresh and caching behavior in practice

Operationally, default overview surfaces are optimized for fast load and frequent refresh, while deep drilldowns may require additional processing time. Practical guidance:
  • use summary cards for rapid monitoring and anomaly detection.
  • use detail tabs for root-cause analysis.
  • use exports for finance-grade final numbers.

Plan and feature-gated surfaces

Some analytics modules are plan dependent (for example advanced revenue/fraud/deep-link surfaces). If a tab or widget is unavailable, verify:
  • current workspace plan
  • feature gate status
  • module prerequisites (for example deep-link tab requires deep-link enabled on the link)

Filter discipline

For accurate comparisons, align:
  • date range
  • timezone
  • scope level
  • event/status filters
  • currency context
  1. Start at workspace scope and capture baseline totals.
  2. Drill into campaign scope for the impacted area.
  3. Drill to link scope if discrepancy remains.
  4. Compare with conversion/events pages using the same filters.
  5. Export and finalize reconciliation.

Cross-page consistency checklist

Before declaring a discrepancy:
  1. Confirm identical preset/custom date window.
  2. Confirm identical status filters (approved/pending/refunded/etc).
  3. Confirm identical scope (workspace vs campaign vs link).
  4. Confirm identical currency display context.
  5. Confirm whether page is summary-first or event-log-first.

Common discrepancy patterns

PatternTypical reasonAction
Workspace and campaign totals driftScope/date/status mismatchReapply identical filters and compare again
Sales tab shows value but customer list is smallMissing identity stitching inputsInspect customer identifiers in conversion events
Conversion source breakdown missingSource mapping not provided by senderValidate source metadata in incoming events
ROI swings unexpectedlyCost model/currency changes during periodCompare with fixed period and export snapshot

Exports

Use exports when you need:
  • reconciliation with finance/BI tools
  • historical audit snapshots
  • partner payout verification workflows
Related:
  • /user-guides/manual/data/conversion-tracking-setup-playbook
  • /user-guides/manual/data/exports-and-operational-checks
  • /user-guides/manual/monetization/currencies-cost-models-and-fx