Leads

Leads turns customer interest into a shared work queue. A person can arrive from a campaign, return on another device, submit a form, and later become a Won opportunity without your team rebuilding that story in a spreadsheet.

The page is a board and a table. Both show the same pipeline, so you can move work visually or scan and filter a larger list. Open a lead to see the company, owner, value, tasks, notes, history, and known campaign context in one place.

Before you start

Leads works with known people. Install the browser SDK, then identify a person when they sign in or when you otherwise have permission to connect their activity to your own customer id. Anonymous visitors stay in analytics and do not become named lead cards automatically.

You can add people in three explicit ways:

• Identify them in your product. Their permitted activity and campaign visits can then follow the same customer id across sessions.
• Use a leadmaps form. A published form can run on a hosted leadmaps page or be embedded on an approved origin. Existing forms are never scraped from the page automatically. Form publishing is managed through the leadmaps form service today; ask your workspace owner or leadmaps support to publish the first immutable form definition.
• Import existing identified users. On the Leads page, choose Import, upload a CSV, inspect the complete create/update preview, tick the review confirmation, and then apply it. Previewing changes nothing, and retrying a confirmed import does not create duplicate active cards.

Opening Leads for the first time creates the normal six-stage flow: New, Engaged, Qualified, Opportunity, Won, and Lost. Owners and admins can adjust how the workspace is organised. Business workspaces can also create additional pipelines.

Work the pipeline

• Switch between Board and Table without changing the underlying data.
• Search by person, company, source, or campaign. Filter by owner and state.
• Move a card to another stage by dragging it, using the keyboard-friendly stage control, or updating it from the detail view.
• Assign an owner, link a company id, record expected value, and add private notes or follow-up tasks.
• Mark work Won or Lost. A later opportunity for the same person starts a new cycle, while the old outcome remains in history. One person can have only one active card in the same pipeline at a time.
• Record Won value in the pipeline currency. Historic amounts in different currencies remain separate and are never added into a misleading total.

If two teammates edit the same card at once, leadmaps rejects the stale change and refreshes the latest version instead of silently overwriting someone else’s work.

Automate follow-up

Business workspace owners and admins can choose Automation on the Leads page. Each dashboard rule combines one trigger with one local action. You can react to a new or identified lead, a stage or task change, a permitted form, an analytics event, time waiting in a stage, or a score threshold. The local action can assign or notify a workspace teammate, or move the lead to another stage. Rules can be paused or removed from the same panel.

Advanced task templates and outbound destination actions are configured with leadmaps support. They use the same asynchronous worker and retry trail as the dashboard rules.

See where a lead came from

leadmaps keeps the first touch, latest touch, and ordered visit history for a known person. Normal UTM values work with any social network, newsletter, partner, or ad platform. Major ad click ids are retained when the browser provides them, so a later conversion can still be tied back to the visit that started it.

Forms can carry the same campaign context. When the same person submits twice, leadmaps reuses the active person and pipeline card rather than counting two leads. A suspicious submission is placed in quarantine and does not enter the sales queue. The public response does not reveal the quarantine decision.

Use Sources and campaigns to compare traffic and Attribution to compare spend and conversion credit. Use Leads when somebody needs an owner and a next action.

Plans

Pro includes one working pipeline with board and table views, forms, campaign context, owners, notes, tasks, history, values, filters, and the previewed import.

Business adds multiple pipelines, behavior-based prioritisation, and workflow automation. It can react when interest arrives, activity signals intent, or follow-up waits too long. Dashboard controls can assign the right teammate, move the lead forward, or send a notification. Supported outbound destinations retry in the background and do not undo the local pipeline change.

Scores are a prioritisation aid, not a promise. leadmaps explains the outcome and confidence to customers but keeps its detailed scoring logic internal so the system cannot be gamed.

Roles and private information

Role	What they can do
Owner	Configure and work pipelines, assign work, and reveal permitted contact details.
Admin	Configure and work pipelines, assign work, and reveal permitted contact details.
Member	Work assigned leads, stages, notes, and tasks, and reveal permitted contact details.
Viewer	Read the pipeline with contact details masked; cannot change cards.

Contact fields and free-text notes or task bodies are kept in the private record vault. The analytics and workflow databases store opaque references, not those values. A permitted user must explicitly reveal private details for a lead they can already see, and every reveal is audited.

If the private record service is unavailable, leadmaps returns a retryable error. It does not save a plaintext copy as a fallback. An Article 17 erasure removes the contact and private text while retaining a redacted workflow trail such as stage changes and task completion, so the team can still account for what happened without keeping the erased content.

A practical campaign flow

1. Tag a campaign link with consistent utm_source, utm_medium, and utm_campaign values.
2. Send the visitor to a published form or identify them in your product.
3. Open Leads and assign the resulting card to a teammate.
4. Add the next task and move the card as the conversation progresses.
5. Mark the card Won with the final value.
6. Compare Won and tracked value by campaign and currency, then use the result to decide which campaigns deserve more budget.

Tips

• Agree on one spelling for each UTM value before launching a campaign.
• Use expected value for forecasting and Won value for the final outcome.
• Give every active card an owner and a concrete next task.
• Treat scores as a queue-ordering signal, then read the campaign and activity history before contacting someone.
• Use a new cycle for a genuinely new opportunity instead of reopening old revenue as though it happened twice.