The LeadScale Engine™
LeadScale built the Engine to process lead and customer data between capture and the systems that use it. LeadScale Services uses it to run demand programmes, and the Engine can also be used without Services.
The LeadScale Engine is LeadScale's own data processing platform for lead and customer data. Records can enter by file, upload, API or a configured integration. The Engine processes them according to a flow agreed with the client, then delivers them to one or more systems.
What the Engine is for
A record rarely ends its journey where it is first captured. It may need to be checked, filtered, enriched or scored before a CRM, dialler or marketing platform can use it.
The Engine handles that work between capture and delivery. What it does depends on the requirements of the client or programme. A flow can include validation, filtering, enrichment, scoring, duplicate and frequency controls, and the recording of source, timestamp, lineage and consent information with the record. The Capabilities page explains the wider range of processing available.
Lead validation is one part of that processing. Our lead validation page explains how records can be checked at the point of capture, before delivery into the systems that will use them.
Advertisers, agencies, publishers and data controllers can use the Engine to process records between capture and their own systems. Its role today is processing and routing data; it is not a marketplace or a customer data platform. Every client gets a login to LeadScale Engine to see volumes, pacing, rejected leads and why, and engagement by account.
Where to go next
What can the Engine do? See the Capabilities page for the different kinds of processing the Engine can perform.
Will it work with our systems? See the integrations catalogue for the systems and connection routes currently documented.
Can LeadScale run the programme for us? Yes. Our managed lead generation page covers programmes run by LeadScale Services on the client's behalf.
Who connects the Engine to our workflow? LeadScale's technical team works through how the Engine should fit the systems you already use and what is required on each side. Our technical data services page explains that connection work.
How data gets in, what happens to it and where it goes
Inputs
Inputs
There are several ways to get data into the Engine.
A batch of records can be transferred to an FTP location or uploaded through an interface. Another system can submit records through the API, or a configured integration can pass them directly into the Engine.
That means the same underlying process can start in quite different places. A website form might feed a file that is uploaded manually. A HubSpot form can be configured to send a record directly. A custom-built form can call the API.
The route changes. The job of the Engine does not: receive the data and put it through the flow defined for that client or programme.
Throughputs
There is no default sequence of processing that every record receives.
Before data runs through the Engine, the required processing is defined with the client. The available checks and processes are put into the order the work requires, including the decisions that determine what happens next.
One flow might need validation and duplicate control before enrichment. Another may need different filters, scoring or additional fields. The point is that the sequence is set for the work being done rather than assumed by the software.
For example, identifying a duplicate before a paid telephone check avoids paying for the same lookup again. Once the duplicate has been identified, the flow does not need to repeat that check on another copy.
This is also where the Engine can record information that needs to travel with the record, including its source, timestamp, lineage and consent audit trail.
Outputs
Data leaves the Engine through the same kinds of routes it can arrive through: download or file transfer, API, or a configured integration.
It can be delivered to one destination or to several. Among the most common integrations are Marketo, Eloqua, HubSpot and Pardot. Salesforce and Dynamics are also used as destinations. The integrations catalogue covers the documented connections in more detail.
For many clients, delivery is simple: the Engine puts the record into one system and the job stops there.
Other workflows need orchestration. A record can be sent to one system first and, depending on what comes back, routed somewhere else. A CRM, dialler and email platform can therefore take part in the same flow without every record necessarily following the same route.
That distinction matters. Delivery answers the question, “Where does this record go?” Orchestration can also answer, “What should happen next?”
The Platform homepage brings together the technology, connections and services available for your data.
Related
- The case studies collection shows examples of LeadScale’s work.
- The About LeadScale page explains the company behind the Engine and its services.
See how the Engine would fit your workflow
If you want to understand how your data could enter the Engine, what processing it would need and where the records should go afterwards, talk to the team that works with it.