> ## 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.

# Key Concepts in LanderLab

> Understand the core LanderLab vocabulary: landers, variants, workspaces, global blocks, integrations, partial leads, and the difference between preview and published pages.

A short glossary of the terms you will meet across LanderLab and this documentation. Understanding these makes every other guide easier to follow.

## Landing page

A single page you build and publish. In the API and in some parts of the interface it is called a **lander**. It has one URL, one set of settings, and at least one variant.

Landing pages can be [organized into folders](/features/landing-pages/folders/create), [duplicated](/features/landing-pages/operations/duplicate), and [moved between workspaces](/features/landing-pages/operations/move-to-workspace).

## Variant

A version of a landing page used for A/B testing. Every page starts with one variant, called the **master variant**. Adding more variants lets you split traffic between designs.

The important detail is that all variants share the same public URL. LanderLab rotates them server side, which keeps your setup compliant with Google and Meta ad policies that penalize redirect-based testing.

<Note>
  Because variants are separate versions of the page, integrations and pixels are applied per variant. When you connect one, the **Apply to variants** step decides which versions get it. See [A/B testing](/features/analytics/ab-testing).
</Note>

## Quiz funnel

A multi-step flow instead of a single page. Visitors move through [steps](/features/quizzes/managing-steps) made of [blocks](/features/quizzes/blocks/input-fields), and [conditional logic](/features/quizzes/conditions/conditional-logic) can send different people down different paths.

Quiz funnels use the same domains, integrations, analytics, and lead handling as landing pages. Most of what you learn about one applies to the other.

## Workspace

A container for landing pages, domains, and team access inside your organization. Agencies typically create one workspace per client, and larger teams create one per brand or vertical.

Your **organization** sits above workspaces and owns billing, users, and integrations. See [create and manage workspaces](/features/multi-user/workspaces) and [add users and manage roles](/features/multi-user/users).

## Global block

A section such as a navbar, footer, or CTA that is built once and reused across many pages. Editing the block updates every page that uses it, instantly, with no republishing of each page one by one.

A global block can be **detached** on a specific page if you need a one-off variation there. See [get started with global blocks](/features/global-blocks/get-started).

## Component

A saved section you can drop into other pages as a starting point. Unlike a global block, a component is copied at insert time and then lives independently, so later edits to the original do not propagate. See [save and reuse components](/features/editor/how-to-save-and-reuse-components).

<Tip>
  Rule of thumb: use a **global block** when every page must stay identical, and a **component** when you want a head start that you will then customize.
</Tip>

## Integration and connection

These are two different steps and mixing them up is the most common setup mistake.

* An **integration** is an account you save once, such as your Klaviyo API key or your Meta Pixel ID. Most integration types are saved **globally** in your organization and can be reused everywhere.
* A **connection** is attaching that saved integration to a specific landing page and choosing which variants it applies to.

<Warning>
  A few integration types are configured per page rather than saved globally, including [Webhook](/integrations/lead-distribution/webhook), [LeadsPedia](/integrations/lead-distribution/leads-pedia), [LeadProsper](/integrations/lead-distribution/leadprosper), and [Phonexa](/integrations/lead-distribution/phonexa). You configure these fresh on each page that uses them.
</Warning>

## Lead

A form or quiz submission stored in LanderLab. Leads carry your form fields plus system data such as country, device, and any [URL parameters](/features/quizzes/settings/prefill-url-parameters) you passed in.

* A **partial lead** is a submission from someone who filled in part of a multi-step flow and left before finishing. These are captured so you can see where people drop off. See [partial leads](/features/leads/partial-leads).
* **Compliance delivery** sends leads straight to your CRM without LanderLab storing them, for regulated data you are not allowed to retain. See [lead compliance delivery](/features/leads/bypass-saving).

## Field mapping

The step where you tell an integration which LanderLab form field corresponds to which field on the other side, for example mapping your `email` input to the Klaviyo email property. Most CRM integrations require the email field to be mapped before you can save.

## Preview and published

Every page has two states. The **preview** reflects your latest edits and is only visible to you. The **published** page is what visitors see on your domain.

<Warning>
  Changes do not go live automatically. After editing a page, adding a pixel, or connecting an integration, you must [republish](/features/landing-pages/operations/republish) for it to take effect on the live URL.
</Warning>

## Domain

The address your pages are published on. Connect one [through Cloudflare](/features/domain/cloudflare/connect-domain) for automatic DNS configuration, or [manually](/features/domain/manual-connection) by adding records at your registrar. One domain can host many pages on different paths.

## Workflow

An automation that runs when something happens, most commonly a new lead. Workflows start with a [trigger](/features/workflows/trigger), then branch and act through nodes such as [filter](/features/workflows/conditions/filter), [if](/features/workflows/conditions/if), [switch](/features/workflows/conditions/switch), and [delay](/features/workflows/conditions/delay-node). See [get started with workflows](/features/workflows/getting-started).

## AI credits

The currency spent when you generate pages, quizzes, or copy with AI, or run [AI lead insights](/features/leads/ai-lead-insights). Organization owners can cap usage per team member with [credit limits](/features/multi-user/credit-limits).

## API key

A secret token used to authenticate REST API calls and [MCP](/mcp/overview) connections. Keys are scoped to your organization and are passed in the `X-API-Key` header. See [generate a LanderLab API key](/mcp/generate-api-key).

<Warning>
  Treat an API key like a password. Anyone holding it can read and modify your landing pages and leads.
</Warning>