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

# Leads in LanderLab: Overview

> Understand how LanderLab captures, stores, and routes leads. Covers lead management, partial leads, AI insights, compliance delivery, and sending data to your CRM.

Every form submission and completed quiz becomes a lead. Leads are stored in LanderLab by default and can be pushed to your CRM, a lead buyer, or any API at the same moment they are captured.

## What a lead contains

More than the fields you asked for. Each lead carries three layers of data:

* **Your form fields**, exactly as you named them in the editor or the [quiz blocks](/features/quizzes/blocks/input-fields)
* **System data** captured automatically, including country, device, browser, and timestamp
* **Tracking data** you passed in, such as UTM parameters or a click ID, captured through [hidden fields](/features/quizzes/blocks/hidden-fields) or [URL parameter prefill](/features/quizzes/settings/prefill-url-parameters)

That third layer is what makes attribution possible later. If you are running paid traffic, set it up before you launch, not after.

## Managing leads

<Card title="View, filter, and export leads" icon="table" horizontal href="/features/leads/managing">
  Browse leads across your workspace, filter by page or date, export to CSV, and delete what you no longer need.
</Card>

## Partial leads

A partial lead is someone who started a multi-step flow and left before finishing. LanderLab captures what they entered up to that point.

This is the single most useful diagnostic in a quiz funnel. If two hundred people answered step one and forty reached step five, the problem is a specific step, and partial leads tell you which one. Pair them with [quiz drop-offs](/features/quizzes/drop-off) to see the same picture as a funnel chart.

<Card title="Partial leads" icon="chart-simple" horizontal href="/features/leads/partial-leads">
  How partial capture works, what gets stored, and how to read drop-off patterns.
</Card>

<Tip>
  [Inactivity auto-submit](/features/quizzes/settings/inactivity-auto-submit) can convert an abandoned session into a usable lead when someone has already given you contact details on an earlier step.
</Tip>

## AI lead insights

Instead of exporting a spreadsheet and looking for patterns yourself, [AI lead insights](/features/leads/ai-lead-insights) analyzes your leads and reports what it finds: quality patterns, data issues, and recommendations on where the funnel is losing value.

## Compliance and data privacy

Some verticals do not permit you to store lead data at all, or only under specific conditions. LanderLab has two answers for this.

**Compliance delivery** sends the lead straight to your destination without LanderLab retaining a copy. Nothing lands in your dashboard, which is the point.

<Card title="Lead compliance delivery" icon="shield-check" horizontal href="/features/leads/bypass-saving">
  Send data directly to your CRM or buyer without storing it in LanderLab.
</Card>

**Certification** proves consent was given. [TrustedForm](/integrations/lead-certification/trusted-form) and [Jornaya](/integrations/lead-certification/journaya) generate a verifiable record of the visitor's session, which is standard in regulated lead generation.

## Getting leads out

Storage is only half the job. Most teams push leads somewhere the moment they arrive.

<Columns cols={2}>
  <Column>
    <Card title="Send to a CRM" icon="address-book" href="/overview/integrations">
      Klaviyo, HubSpot, ActiveCampaign, GoHighLevel, Mailchimp, Pipedrive, and more.
    </Card>
  </Column>

  <Column>
    <Card title="Send to a buyer or API" icon="share-nodes" href="/integrations/lead-distribution/webhook">
      Webhook, Google Sheets, LeadsPedia, LeadProsper, Phonexa, LeadByte.
    </Card>
  </Column>
</Columns>

When one destination is not enough, or the destination depends on the lead's answers, use a [workflow](/features/workflows/getting-started) instead of a plain integration. Workflows can filter, branch, and route different leads to different places.

## Protecting lead quality

Bad leads cost money whether you paid for the click or the lead. LanderLab includes several layers you can stack:

* [Email verification](/features/quizzes/validation/email) and [phone validation](/features/quizzes/validation/phone) reject invalid contact details at entry
* [OTP SMS verification](/features/quizzes/validation/one-time-password) confirms the phone number actually belongs to the person
* [reCAPTCHA](/integrations/lead-certification/re-captcha-v3) and [Cloudflare Turnstile](/integrations/lead-certification/cloudflare-turnstile) block bot submissions

<Note>
  Each layer adds friction, so add them in response to a real problem rather than all at once. OTP in particular will reduce raw volume while raising quality.
</Note>