Engine configuration
You know what your team needs to receive. LeadScale’s technical team turns those requirements into the checks, filters and processing rules the Engine runs before records reach your systems.
LeadScale configures the Engine for the programme you want to run. The technical team works from your requirements to specify the criteria for the four lead checks, any further filters, the processing order and where records go next. For other data work, the operations follow the requirements of those records. That processing is agreed with you before records move.
Turn an acceptable lead into rules the Engine can apply
“We need new contacts with a verified phone number, within these postcodes, and no repeated submissions.”
That is a useful starting requirement. To put it into operation, each part needs a precise meaning. What must phone verification establish? Which postcodes are included? Does “no repeats” mean no second response at all, or no second response within a particular period?
LeadScale’s technical team works through those decisions and configures the Engine to apply them, including what happens when a requirement is not met.
A postcode list, for example, can become a field-based filter. A restriction on repeat submissions becomes a frequency rule. An external phone check becomes one step in the processing flow, with its result determining whether processing continues.
Choose the processing your programme needs
The same four checks run on every lead. The work is to establish which processing serves your requirements and how the steps fit together.
The configuration sets the criteria for the lead checks and can include further field-based filters, duplicate and frequency rules, and scoring. Where additional information is needed, enrichment can be included. Every lead is reviewed by one of our team as the final quality check.
A phone number with the right format is not necessarily a verified number. The technical team needs to know which result your receiving team will rely on. Our lead validation page explains that distinction and the four checks.
Set the order of processing
The criteria and processing order need to be established together.
Suppose a record is a duplicate that the programme does not accept. Identifying it before an external verification lookup avoids running that lookup again. The record has already failed a requirement, so further checking would not change the delivery decision.
The configuration establishes which results are needed at each point and which processing follows from them.
Decide what happens after each result
A processing flow can follow different paths. The result of one step can determine the next step, rather than every record passing through an identical sequence.
LeadScale configures those conditions for the programme, including the handling of rejected or exception records under the agreed business rules. A record that fails a required check is not sent into the destination system.
The destination is also part of the setup. Once the required processing has run, the Engine needs to know where to deliver the record. For the connection work and each team’s responsibilities, see our page on technical data services.
From a requirement to configured processing
- Describe what your team needs. Establish what must be true of a record before it should be delivered, including any exclusions and repeat-response requirements.
- Translate that into processing. Set the criteria for the four lead checks, choose any further filters, then set the processing order and the conditions that determine what happens next.
- Agree the specification. Confirm the processing and destinations with you before the Engine runs the programme’s records.
A programme set up to your requirements
You receive a configured processing flow. For leads, this sets the criteria for the four quality checks, any further filters, the processing order and the destinations for accepted records. Other data work uses the operations needed by those records.
LeadScale can do this setup for a programme your own team runs using the Engine, as well as for demand activity managed by LeadScale Services.
Keep the processing connected to the record’s history
For records captured through a LeadScale programme, source, timestamp, lineage and consent audit information are recorded alongside the data. The consent and provenance page describes that history and the use of supplied consent information.
Frequently asked questions
Do we need to write technical rules before speaking to you?
Start with the requirements: what your team needs to receive and what it needs kept out. LeadScale’s technical team translates those requirements into the Engine’s processing instructions.
Does a person review every lead?
Yes. Every lead is reviewed by one of our team, and the review is specified as part of the processing.
Can we use the Engine without LeadScale running our demand programme?
Yes. Your team can run the programme while LeadScale’s technical team handles onboarding and configuration of the Engine. The processed records are delivered into the systems agreed for your team to use.
Explore related pages
- Technical data services— how the technical team connects your systems to the Engine.
- Lead validation— the four checks, their criteria and the order of processing.
- Deduplication and suppression— repeat-response rules and exclusions using client data.
- Data enrichment— what can be added to records and how they are delivered.
Bring your definition of an acceptable record
Tell us what needs to be present, what should be checked and what should cause a record to be excluded. We can work through how to put those requirements into the Engine.