Skip to main content

Linquid User Manual

This manual explains Linquid from an operator perspective: what each feature does, where to find it in the dashboard, what settings change behavior, and how outcomes appear across reports.

What Linquid is built for

Linquid combines four connected systems:
  • Link and campaign operations for traffic routing.
  • Conversion and customer intelligence for lead/sale outcomes.
  • Affiliate and partner operations for program growth and payouts.
  • Workspace controls for team access, billing, and governance.

Operator personas this manual supports

  • Growth operators: traffic routing, campaign optimization, link hygiene, and analytics interpretation.
  • Marketing analysts: attribution checks, conversion quality validation, and reporting/export workflows.
  • Affiliate managers: partner onboarding, commission governance, and payout operations.
  • Workspace administrators: member permissions, identity controls, billing, and security settings.
  • Technical operators: integrations, webhooks, keys, and API-connected automation.

How to use this manual

  1. Start with workspace setup and access.
  2. Configure campaigns, links, and routing rules.
  3. Define conversion tracking and customer identity behavior.
  4. Validate analytics and exports.
  5. Connect integrations, automation, and payout operations.
  • Use global dashboard search to jump directly to campaigns, links, rules, and pages.
  • Use workspace switcher/default workspace settings to avoid editing in the wrong workspace.
  • Use page-level filters and date presets consistently before comparing metrics.

Typical lifecycle in Linquid

  1. Create campaign strategy with cost model and reporting currency.
  2. Create links and apply routing rules, deep-link options, and security settings.
  3. Add tracking methods for conversions (pixel, S2S, integrations, or API-based ingestion).
  4. Validate behavior in analytics tabs and reconcile with exports.
  5. Scale acquisition via affiliates, partners, and outbound automation.
  6. Govern usage with plan limits, retention policy, and role-based access controls.

Core entities

EntityWhat it representsManaged from
WorkspaceYour operating container for users, billing, and data scopeWorkspace settings
CampaignStrategy layer for a group of linksCampaigns
LinkRedirect object that handles trafficLinks
RuleConditional routing logic on top of linksRules
ConversionTracked outcome (lead, sale, or custom event)Conversions
CustomerIdentity record stitched from conversion activityCustomers
PartnerExternal affiliate participant in your programAffiliates
IntegrationConnected external provider for ingest or deliveryIntegrations

Data flow model (high level)

StageWhat happensWhat users usually verify
Traffic inVisitors hit links and routing rules evaluate conditionsDestination, redirect behavior, and click quality
Event captureClick events and conversion events are ingestedEvent status, source tagging, and dedupe behavior
Identity stitchingConversion events map into customer recordsCustomer profile consolidation and repeat-event behavior
Cost/revenue modelingCampaign/link cost model and event value produce economic metricsRevenue, cost, ROAS/ROI consistency
Analytics servingDashboard cards/tables/charts render by scope and date windowCross-page consistency and trend interpretation
Exports/reportingTeams export data for finance and BI workflowsReconciliation to in-app totals

Scope hierarchy and how to read numbers

  • Workspace scope: all campaigns and links in the workspace.
  • Campaign scope: subset of workspace data for one campaign.
  • Link scope: subset of campaign/workspace data for one link.
  • Affiliate scope: partner-program perspective with commission and payout context.
Best practice:
  1. Confirm filters/date ranges are aligned.
  2. Compare workspace to campaign, then campaign to link.
  3. Reconcile final values with exports for billing or payout decisions.

What this manual intentionally excludes

  • Internal implementation details not needed for customer operations.
  • Sensitive or infrastructure-specific deployment data.
  • Internal-only support/debug procedures not relevant to operators.

Manual sections

  • /user-guides/manual/foundations/customer-doc-coverage-checklist
  • /user-guides/manual/foundations/getting-started
  • /user-guides/manual/foundations/end-to-end-setup-playbooks
  • /user-guides/manual/foundations/feature-map-by-page
  • /user-guides/manual/foundations/platform-module-coverage-index
  • /user-guides/manual/foundations/search-support-and-legal-reference
  • /user-guides/manual/workspace/workspaces-and-access
  • /user-guides/manual/workspace/workspace-onboarding-and-governance-playbook
  • /user-guides/manual/workspace/workspace-settings-and-governance-reference
  • /user-guides/manual/workspace/workspace-tabs-and-plan-gates-reference
  • /user-guides/manual/workspace/embeds-and-public-stats-reference
  • /user-guides/manual/workspace/api-access-and-scopes
  • /user-guides/manual/growth/campaigns-links-rules
  • /user-guides/manual/growth/links-and-settings-reference
  • /user-guides/manual/growth/bulk-link-operations-reference
  • /user-guides/manual/growth/rules-conditions-and-operators-reference
  • /user-guides/manual/growth/campaigns-cost-and-budget-reference
  • /user-guides/manual/growth/tags-folders-utm-reference
  • /user-guides/manual/data/conversions-customers
  • /user-guides/manual/data/conversion-tracking-setup-playbook
  • /user-guides/manual/data/conversion-methods-and-event-types-reference
  • /user-guides/manual/data/events-and-customers-operations-reference
  • /user-guides/manual/data/analytics-and-reporting
  • /user-guides/manual/data/analytics-views-reference
  • /user-guides/manual/growth/deep-links-and-qr-reference
  • /user-guides/manual/ecosystem/affiliates-and-partners
  • /user-guides/manual/ecosystem/affiliate-program-operations-reference
  • /user-guides/manual/ecosystem/partner-portal-reference
  • /user-guides/manual/ecosystem/integrations-and-automation
  • /user-guides/manual/ecosystem/provider-setup-playbooks
  • /user-guides/manual/ecosystem/workspace-integrations-reference
  • /user-guides/manual/ecosystem/integrations-and-webhooks-reference
  • /user-guides/manual/monetization/billing-plans-and-credits
  • /user-guides/manual/monetization/plans-pricing-and-limits-reference
  • /user-guides/manual/monetization/plan-gate-validation-playbook
  • /user-guides/manual/monetization/currencies-cost-models-and-fx
  • /user-guides/manual/data/data-retention-and-lifecycle
  • /user-guides/manual/workspace/security-and-compliance
  • /user-guides/manual/workspace/settings-and-preferences
  • /user-guides/manual/data/exports-and-operational-checks
  • /user-guides/manual/foundations/glossary
RoleSuggested first chapters
Growth operatorgetting-started -> campaigns-links-rules -> links-and-settings-reference -> analytics-views-reference
Analystanalytics-and-reporting -> analytics-views-reference -> conversion-methods-and-event-types-reference -> exports-and-operational-checks
Affiliate manageraffiliates-and-partners -> affiliate-program-operations-reference -> billing-plans-and-credits
Workspace adminworkspaces-and-access -> workspace-settings-and-governance-reference -> security-and-compliance