A fundamental overview of the main components of LeadExec and how they work together.

LeadExec is enterprise lead distribution software developed by ClickPoint Software for lead generation companies, lead sellers, lead buyers, affiliate networks, lead marketplaces, and enterprise organizations.

LeadExec accepts inbound leads from websites, affiliates, lead providers, APIs, and other sources, then validates, qualifies, routes, and delivers those leads to buyers, branches, dealers, sales teams, CRMs, and other endpoints.

The platform supports both straightforward and advanced lead distribution workflows, including buyer qualification, Ping/Post, lead validation, geographic routing, buyer management, and multiple distribution strategies.

Two of the most important concepts when configuring LeadExec are Lead Types and Automation Preferences.

A Lead Type defines the structure and fields associated with a lead.

The first step in configuring a new LeadExec account is typically to create a Lead Type and define the lead fields to be captured and distributed.

Organizations can create multiple Lead Types when operating across different products or verticals. For example, a lead generation company may maintain separate Lead Types for insurance, mortgage, solar, legal, or home services.

Many LeadExec features—including qualification, validation, routing, delivery, and reporting, depend on the Lead Type, making it a foundational component of the platform.

Automation Preferences:

Automation Preferences define the default delivery automation behavior used throughout LeadExec.

These settings are located within Client Settings in Account Settings and establish how lead distribution automation should operate by default.

Automation Preferences can also be overridden at the Lead Source Campaign level when a specific campaign requires different distribution behavior.

The primary sections of LeadExec represent different stages of the lead distribution lifecycle.

At a high level:

Lead Source → Campaign → Lead Qualification & Validation → Routing & Distribution → Client / Buyer → Delivery → Reporting

The destination can represent an external lead buyer or an internal branch, dealer, franchise, sales organization, CRM, or other endpoint.

The Leads section provides access to lead data and distribution reporting.

Two of the primary screens are:

These screens provide visibility into leads processed through LeadExec and their distribution activity.

The Inbound section controls how leads enter LeadExec and provides access to Lead Sources and Campaigns.

A Lead Source identifies where a lead originated.

Common Lead Sources include:

Lead Sources allow organizations to track the origin, volume, quality, cost, and performance of incoming leads.

A Campaign is a receiving avenue within a Lead Source and provides more granular control over incoming leads.

For example, if your website is a Lead Source, individual forms or landing pages can be configured as separate Campaigns.

Campaigns can also separate leads based on criteria, vertical, geography, lead cost, or other requirements.

For example, an affiliate might be paid $35 for California leads and $15 for Nevada leads. Separate Campaigns and qualification criteria can determine which leads are accepted and which pricing rules apply.

This structure allows organizations to analyze both overall Lead Source performance and individual Campaign performance.

The Outbound section controls where leads go after entering LeadExec and qualifying for distribution.

LeadExec can distribute leads to external lead buyers as well as internal branches, dealers, franchises, sales teams, CRMs, and other destinations.

The primary concepts are Clients, Delivery Methods, and Delivery Accounts.

A Client represents the destination where a lead will ultimately be delivered.

Depending on the organization, a Client may represent:

For lead sellers and marketplaces, Clients commonly represent external lead buyers.

For enterprise organizations, Clients may instead represent internal branches, dealers, locations, or other destinations. LeadExec therefore supports both lead-selling workflows and enterprise lead distribution workflows.

Delivery Methods:

Delivery method settings are found in the Client Details screen and determine how a lead will be delivered to a client.

LeadExec supports delivery methods including:

Delivery methods can include field mapping, authentication, qualification requirements, retry logic, timeouts, and response handling depending on the destination.

A Delivery Method determines how LeadExec sends a lead to a Client.

LeadExec supports multiple delivery methods, including:

Delivery Methods provide the technical connection between LeadExec and the system receiving the lead.

Where a Delivery Method determines how a lead is delivered, a Delivery Account determines what leads the Client is eligible to receive.

Delivery Accounts can use criteria to qualify leads for a Client and define distribution and lead quantity rules.

This makes Delivery Accounts an important part of LeadExec buyer management and routing because they help determine which Clients are eligible for each lead before distribution occurs.

LeadExec supports both straightforward and advanced lead routing strategies.

Routing options include:

LeadExec can also evaluate buyer coverage, schedules, capacity, pricing, lead quality, validation results, and delivery responses before determining where a lead should be delivered.

This allows organizations to build lead distribution workflows ranging from simple assignment rules to complex lead marketplaces and multi-buyer routing environments.

LeadExec can evaluate lead quality before distribution.

Organizations can use validation and compliance information to determine whether a lead should be distributed, rejected, rerouted, or sent to Quality Control.

LeadExec supports workflows involving:

For example, a lead with a low quality score or an unverified phone number can be prevented from entering normal distribution and instead sent to Quality Control for review.

A Channel identifies what type of lead is entering LeadExec and can determine how that lead is processed for distribution.

LeadExec supports four primary Channel types.

Web Leads are the most common type of lead processed by LeadExec. These typically originate from websites, landing pages, affiliates, publishers, or third-party lead providers.

Phone Leads enter LeadExec through the LeadExec IVR system.

Chat Leads are created through supported website or landing-page chat workflows.

Ping/Post Leads use a two-step lead distribution process.

Partial lead information is first pinged into LeadExec to determine whether buyer coverage exists and whether configured revenue requirements can be satisfied.

When an eligible opportunity is identified, the complete lead can then be posted for delivery.

Ping/Post is commonly used by lead sellers, aggregators, performance marketers, affiliate networks, and lead marketplaces that need to evaluate buyer eligibility and monetization opportunities before transferring the complete lead.

The easiest way to understand LeadExec is as a connected lead distribution workflow:

Lead Source — Where the lead originates

↓

Campaign — How incoming leads are categorized, qualified, and managed

↓

Lead Type — Defines the data associated with the lead

↓

Qualification & Validation — Determines whether the lead meets configured requirements

↓

Routing & Distribution — Determines which Clients or buyers are eligible and how the lead should be distributed

↓

Client — The buyer, branch, dealer, organization, or destination receiving the lead

↓

Delivery Method & Delivery Account — Determine how the lead is delivered and which leads the Client is eligible to receive

↓

Distribution Results & Reporting — Provide visibility into what happened to the lead

Together, these concepts allow LeadExec to automate enterprise lead distribution, lead routing, buyer management, Ping/Post, and lead-selling workflows from initial lead capture through final delivery.