Skip to main content

​
End-to-End Setup Playbooks

Use this as the primary operator runbook for launching and operating Linquid in production-like conditions.

​
Playbook 1: First workspace launch

  1. Create workspace and confirm owner access.
  2. Set workspace name, branding, default currency, and timezone.
  3. Confirm current plan and visible workspace tabs match expected entitlements.
  4. Invite core operators (marketing, growth, finance, support) with least-privilege roles.
  5. Enable account security baseline (password hygiene, 2FA where available, session review cadence).
  6. Configure billing readiness (payment method, top-up policy, alert recipients).
Launch criteria:
  • owner/admin roles assigned correctly
  • billing profile and credit policy confirmed
  • no critical setup tab left incomplete
  1. Create campaign with intended objective and naming convention.
  2. Set campaign cost model and campaign currency before traffic starts.
  3. Create links with clear labels and destination intent.
  4. Apply required link controls (expiry, password, click limit) where policy requires.
  5. Add routing rules in explicit priority order.
  6. Validate fallback behavior when no rule matches.
  7. Add tags/folders/UTM templates for reporting discipline.
Launch criteria:
  • links resolve to expected targets
  • rule order is deterministic and documented
  • campaign/link metadata enables clean analytics segmentation

​
Playbook 3: Conversion tracking readiness

  1. Decide which conversion methods are required:
    • browser/client tracking
    • server-to-server tracking
    • provider integration ingestion
  2. Define event dictionary (lead, sale, custom names and allowed statuses).
  3. Enforce identity requirements for customer stitching (email or stable customer ID).
  4. Enforce idempotency keys for retry-safe event delivery.
  5. Send controlled test events for each method.
  6. Confirm events appear in Conversions, Events, Customers, and analytics tabs as expected.
Launch criteria:
  • each conversion method passes test flow
  • status, value, and currency behave as intended
  • no duplicate-event inflation during retry tests

​
Playbook 4: Analytics validation before scale

  1. Open workspace analytics and confirm Clicks/Leads/Sales/Funnel tabs all load.
  2. Drill into one campaign and one high-volume link; verify directional consistency.
  3. Compare Conversions totals with Events stream and Customers count assumptions.
  4. Confirm selected range/timezone/currency are identical before comparing pages.
  5. Run one export and verify in-app totals reconcile directionally.
Launch criteria:
  • scope-based analytics are coherent (workspace -> campaign -> link)
  • conversion and revenue context is consistent with selected filters
  • exports are usable for finance or operations reconciliation

​
Playbook 5: Agency and enterprise scale setup (if enabled)

  1. Enable integration providers required for your stack.
  2. Configure outbound webhooks/automations and verify signature handling.
  3. If affiliate program is used, configure program policy, enrollment flow, and payout governance.
  4. Validate fraud review process before approving payouts.
  5. Validate plan-gated modules after any plan change (upgrade or downgrade).
Launch criteria:
  • integrations have active health state and tested mappings
  • affiliate lifecycle is operationally governed
  • gated features and limits match current plan

​
7-day launch stabilization checklist

Day 1:
  1. Verify no major routing misfires on top links.
  2. Verify conversion ingestion health and dedupe behavior.
Day 2-3:
  1. Review analytics discrepancies and fix filter/scope discipline gaps.
  2. Review customer stitching quality and identity payload completeness.
Day 4-5:
  1. Run payout/finance dry-run reconciliation (if affiliate and revenue modules are active).
  2. Confirm billing usage growth is expected for traffic volume.
Day 6-7:
  1. Validate invite/role model still matches operator responsibilities.
  2. Capture baseline runbook notes for ongoing operations.

​
Failure handling quick map

SymptomMost likely root causeFirst action
Links route unexpectedlyRule order/conditions mismatchRe-check rule priority and fallback target
Conversions visible but customer list sparseMissing identity fieldsEnforce customer identity in event payloads
Revenue numbers drift between viewsScope/timezone/currency mismatchAlign filters and re-check source-of-truth export
Feature missing from UIPlan gate or role restrictionCheck plan entitlements and role permission
Integration stuck in errorCredential or mapping issueRe-auth provider and re-run test event
Related:
  • /user-guides/manual/workspace/workspace-onboarding-and-governance-playbook
  • /user-guides/manual/data/conversion-tracking-setup-playbook
  • /user-guides/manual/monetization/plan-gate-validation-playbook
  • /user-guides/manual/ecosystem/provider-setup-playbooks