> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linquid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting Started

> First-day setup from account creation to a fully measurable campaign

# Getting Started

This flow gets you from zero to a measurable live campaign.

## Before you begin

Confirm:

* workspace owner/admin responsibilities are clear
* billing method is configured for expected launch volume
* naming conventions for campaigns, links, and events are agreed
* analytics and finance stakeholders agree on reconciliation process

## Recommended setup owner roles

| Step                | Primary owner         | Secondary reviewer       |
| ------------------- | --------------------- | ------------------------ |
| Workspace setup     | Workspace owner/admin | Security/admin reviewer  |
| Campaign setup      | Growth operator       | Analyst/finance reviewer |
| Link and rule setup | Campaign operator     | QA reviewer              |
| Conversion setup    | Technical operator    | Analyst reviewer         |
| Launch verification | Analyst               | Workspace owner          |

## Step 1: Set up your workspace

In **Workspace Settings**:

* Confirm workspace name and logo.
* Confirm default currency for reporting.
* Invite teammates and assign roles.
* Review plan capabilities before launch.

Validation checklist:

1. Workspace branding is correct.
2. Default currency matches finance preference.
3. Required admins are invited and active.
4. Plan gates for intended features are available.

## Step 2: Create a campaign

In **Campaigns**:

* Create a campaign with clear naming.
* Choose cost model and reporting currency.
* Confirm campaign-level objectives and ownership.

Validation checklist:

1. Campaign naming follows your taxonomy.
2. Cost model reflects commercial reality.
3. Currency is intentionally selected.
4. Campaign owner is assigned.

## Step 3: Create links

In **Links**:

* Add destination URL and short-link metadata.
* Assign campaign/folder/tags.
* Configure expiration, password, and click limit if required.
* Generate QR variants if needed for offline channels.

Validation checklist:

1. Short URL path naming is consistent.
2. Destination opens correctly on desktop and mobile.
3. Security controls (password/expiry/click limit) match intent.
4. Campaign/folder/tag assignment is complete.

## Step 4: Add routing rules

In **Rules** or link rule editor:

* Add conditions (geo, device, browser, OS, referrer, query, time, and quality signals).
* Set rule priority and fallback behavior.
* Test with representative traffic scenarios.

Validation checklist:

1. Priority order is intentional and documented.
2. Fallback destination always resolves safely.
3. Test cases cover geo/device/browser permutations.
4. Conflicting rules are resolved before launch.

## Step 5: Configure conversion tracking

In **Conversions** and **Integrations**:

* Decide which conversion types to track (lead, sale, or custom events).
* Set event naming standards.
* Validate attribution payload quality.
* Confirm customer identity fields for stitching.

Validation checklist:

1. Event names and types are standardized.
2. Transaction IDs are present where dedupe is required.
3. Customer identity fields are populated consistently.
4. Test conversions appear in expected scope views.

## Step 6: Validate analytics

In **Analytics**, **Conversions**, **Events**, and **Customers**:

* Confirm clicks and uniques match test traffic.
* Confirm conversion totals by type.
* Confirm sales/revenue align with expected currency behavior.
* Confirm dashboards and scoped analytics (workspace, campaign, link) are consistent.

Validation checklist:

1. Workspace, campaign, and link scope totals are coherent.
2. Date ranges/timezone are aligned for comparisons.
3. Revenue/cost values are in expected reporting currency.
4. Event and customer pages reflect the same ingestion test set.

## Step 7: Production readiness checks

Before launch:

* Verify team permissions and workspace defaults.
* Verify plan-gated features behave correctly.
* Verify integration delivery and retry outcomes.
* Verify export files and reconciliation workflow.

## Day-0 launch checklist

1. Execute final click and conversion smoke tests from real devices.
2. Confirm webhook/integration destinations receive expected payloads.
3. Confirm key dashboards load without missing widgets.
4. Save baseline exports for first-day reconciliation.

## Week-one stabilization

After launch, run these checks daily:

* credit balance and billable-event mix
* link/rule behavior on top traffic paths
* conversion status quality (pending/approved/refunded/fraud)
* affiliate partner and payout pipeline health (if enabled)

## Common launch issues and fixes

| Symptom                                | Typical cause                                 | First action                                          |
| -------------------------------------- | --------------------------------------------- | ----------------------------------------------------- |
| Clicks visible but conversions missing | Incomplete conversion identity/payload fields | Re-run conversion test with validated payload         |
| Revenue appears inflated               | Currency mismatch in event payloads           | Verify event currency and campaign reporting currency |
| Partner commissions not progressing    | Status workflow not approved                  | Review commission status and payout configuration     |
| Team cannot access expected pages      | Role assignment mismatch                      | Re-check user role and workspace membership           |

Next:

* `/user-guides/manual/foundations/end-to-end-setup-playbooks`
* `/user-guides/manual/workspace/workspaces-and-access`