Skip to main content

Affiliates and Partners

Linquid includes two sides of affiliate operations:
  • Program owner side inside your workspace.
  • Partner side in the partner portal.

Operating model

SidePrimary objectiveTypical owner
Program owner workspaceAcquire and manage partners, control commissions and payoutsAffiliate manager / revenue ops
Partner portalDrive attributed traffic and track earningsPartner / affiliate

Program owner workflows

From affiliate modules you can:
  • define program settings and partner terms
  • review applications/enrollments
  • manage partner status and segmentation
  • review commissions and payout readiness
  • send direct and broadcast messages
Owner side also commonly includes group segmentation, discounts, bounties, and automation workflows for partner operations.

Program setup checklist

  1. Define partner eligibility and review criteria.
  2. Configure commission model and approval policy.
  3. Configure payout cadence and minimum thresholds.
  4. Configure partner communication templates.
  5. Define fraud review workflow before opening enrollment.

Program governance controls

Program owners typically manage:
  • partner eligibility and onboarding criteria
  • commission structures and approval policy
  • payout method rules and payout cadence
  • moderation and fraud response workflow

Marketplace and invites

You can grow partner network through:
  • public marketplace discovery
  • direct invites
  • application review and approval flow
Recommended onboarding policy:
  • publish clear eligibility requirements
  • define review SLAs for applications
  • require payout profile completeness before full activation

Enrollment states and operator actions

StateMeaningTypical operator action
AppliedPartner submitted applicationReview profile and traffic quality
ApprovedPartner can promote programSend onboarding guidance and assets
RejectedPartner does not qualifyProvide reason and optional retry path
SuspendedTemporarily restrictedInvestigate quality/fraud concerns
ClosedRelationship endedReconcile commissions and archive history

Commission and payout lifecycle

Typical flow:
  1. conversion attributed to partner
  2. commission generated
  3. commission reviewed/approved
  4. payout batch created and processed
Payout operations should also track:
  • payout status transitions
  • failed payout retries
  • partner payout profile completeness
  • currency and fee implications

Commission governance checklist

  1. Confirm attribution source before approval.
  2. Confirm refunded or disputed events are excluded as policy requires.
  3. Confirm payout eligibility thresholds are met.
  4. Confirm final payout amount and currency are expected.
  5. Confirm payout status transitions are recorded.

Fraud and risk controls

Use fraud views and grouped review workflows to:
  • identify suspicious conversion clusters
  • suppress invalid commission outcomes
  • enforce payout holds when needed

Fraud escalation runbook

  1. Flag affected partner/activity cluster.
  2. Place hold on pending commission approvals.
  3. Investigate event integrity and attribution trail.
  4. Decide approve/reject/adjust outcome.
  5. Document action for compliance and partner communication.

Partner portal

Partners can:
  • view active programs
  • track performance and earnings
  • manage payout profile
  • receive/respond to owner messages
Partner portal pages typically cover:
  • dashboard and earnings trends
  • program list and per-program performance
  • invitation and enrollment status
  • payout history and profile settings
  • partner messaging inbox

Marketplace and messaging strategy

For healthier partner growth:
  • publish clear program positioning in marketplace listings
  • define response-time targets for applications
  • segment outbound messaging by partner maturity
  • provide payout and attribution policy clarity up front

Reporting and reconciliation checks

  • compare partner-facing earnings with owner-side approved commission totals.
  • validate payout batches against approved commission status.
  • verify program-level totals with workspace conversion scope for attributed traffic.
Related:
  • /user-guides/manual/data/conversions-customers
  • /user-guides/manual/ecosystem/integrations-and-automation
  • /user-guides/manual/ecosystem/partner-portal-reference