Core concepts
Glossary
Every LeadMove term in one place, alphabetically, with a link to the page that covers it in full.
The words used across the app and this documentation, in one sentence each. If a term has its own page, follow the link for the detail.
| Term | What it means |
|---|---|
| Buyer | A company you sell leads to — created once and reusable across every pipeline. See Adding buyers. |
| Canonical field | The field name your pipeline stores a value under; incoming names are matched to it case-insensitively, ignoring spaces, underscores and dashes. |
| Condition | One test on a field (state is one of CA, OR, WA) — the building block of routing rules, spam filters, forwarding rules and price rules. |
| Credit | The compensation given when you accept a dispute: the lead comes out of your revenue figures, or the buyer gets a replacement lead. See Resolving disputes. |
| Dedup window | How far back deduplication looks for a matching lead in the same pipeline — 30 days by default. See Deduplication. |
| Deferred delivery | A delivery waiting because the buyer is outside its operating hours; it's re-checked and sent automatically when the buyer reopens. See Lead statuses. |
| Delivery method | How a buyer receives its leads — email, webhook, Google Sheets or SMS. A buyer can have several. Also called an endpoint. See Delivery methods. |
| Dispute | A buyer contesting a lead it received (wrong number, unreachable, out of area). See How disputes work. |
| Dispute window | How long a buyer has to contest a delivered lead — 48 hours by default, adjustable per account and per buyer. |
| Distribution mode | Whether a lead goes to one buyer (exclusive) or to every matching buyer at once (shared). Set per pipeline. See How distribution works. |
| Distribution method | How leads are split between buyers matching in the same tier: equal (evenly) or weighted (proportional to each buyer's quota, so bigger buyers get a bigger share). |
| Endpoint | See delivery method. |
| Forwarding | A rule that sends a lead into another of your pipelines. Copy forwards it and keeps distributing here; transfer hands it over entirely. See Forwarding. |
| Grade | The letter version of the quality score: A from 80, B from 60, C from 40, D below. Usable in routing conditions and price rules. See How scoring works. |
| Held lead | A lead parked for your manual approval before it can be distributed. It's already scored; it goes out when you approve it, or on its own if you set an auto-release delay. See Manual review. |
| Operating hours | The days and times a buyer accepts leads, in the buyer's own timezone, with a choice of what happens outside them: defer (hold and deliver at reopening) or skip (let another buyer take it). See Operating hours. |
| Pipeline | One lead flow you sell: its fields, its intake sources, its rules and its buyers. The central object in LeadMove. See Creating a pipeline. |
| Posting URL | The URL a source posts leads to, ending in /api/i/{source-key}. The key is in the URL, so no header or API key is sent. See Webhook API reference. |
| Price rule | A conditional price: the first rule whose conditions match the lead sets what the buyer pays, otherwise the flat price per lead applies. Can be set on a routing rule or on the buyer. See Lead pricing. |
| Quality score | A 0-100 score every lead gets on arrival, used for routing, pricing and reporting. See How scoring works. |
| Quota (buyer) | The maximum number of leads a buyer accepts per day, week or month. Reaching it takes the buyer out of distribution until the counter resets. See Quotas & caps. |
| Quota (plan) | What your subscription allows per month — leads, buyers and pipelines. See Plans & quotas. |
| Routing rule | The link between a pipeline and a buyer: its conditions decide which leads that buyer gets, its tier decides when it's considered. See Routing rules. |
| Source | One inbound channel into a pipeline — a vendor, a form, a CRM — with its own posting URL and its own field mapping. See Sources & posting URLs. |
| Spam filter | Per-pipeline conditions evaluated the moment a lead arrives, on the raw values. Matching leads are quarantined: never distributed, never billed. See Spam filtering. |
| Tier | A priority level in a pipeline. Tier 1 is tried first, then tier 2, and so on. Rules in the same tier share the leads they both match — the more specific condition doesn't win. |
| Wallet (prepaid balance) | The alternative to invoicing a buyer: each delivery debits a balance the buyer tops up in advance, and deliveries pause when it runs out unless you allow overdraft. See Billing modes. |
Common questions
What happened to the word "campaign"? LeadMove calls it a pipeline. If you're coming from another platform, the migration guide maps the rest of the vocabulary.
Is a tier the same as a rule priority? No. Tiers order groups of buyers: everything in tier 1 is considered before anything in tier 2. Inside one tier there's no ranking — matching buyers share the leads.
Is a source the same as a pipeline? No. A pipeline is what you sell; a source is one way leads enter it. One pipeline usually has several sources, one per vendor.
Deferred, held, pending — which is which? Held is before distribution and waits for you. Deferred is after distribution and waits for the buyer's hours. Pending just means it's in flight. Full table: Lead statuses explained.