Draft · LeadScale Website 0.5.3 · S-ADV-04 · /solutions/advertisers/scaling-demand/ · not for publication

25 yearsFounded in the UK in 2001Programmes run on the LeadScale Engine™

Scaling demand without losing quality

Growing a lead programme often means adding sources. Each new source is another place where the brief can be interpreted differently, the same person can appear twice or important information can be captured in a different way.

The answer is to keep one standard across the programme. Agree what a usable record has to look like, apply the four checks before delivery and compare records across sources where the programme is configured to do so.

Where quality can drift

Adding a source does not automatically reduce quality. It does create another point where the programme can depart from the standard you intended.

One supplier may interpret a criterion differently from another. The same person may respond in two places. A new source may use a different form or capture different consent information. As volume grows, delivered lead counts can continue to rise while those differences become visible only further downstream.

That makes volume a poor quality control on its own.

If you wait until sales starts returning leads, you are already diagnosing the programme after the records have moved through it.

The more useful question is simpler: are all the sources being held to the same definition of what should be delivered?

One standard across every source

Before adding volume, write down what the programme is buying.

On a LeadScale managed programme, the client's requirements are agreed in plain words and turned into one specification that governs the sources the programme buys. Suppliers deliver against that specification.

Records are then checked before delivery. That means four checks (data hygiene, contact verification, spec and duplication, and human verification), with the criteria agreed for the programme. Where cross-source duplicate and frequency controls are included, the programme can also compare records across sources before delivery.

A lead that fails the checks is not delivered.

That does not guarantee that every lead will convert, and it does not remove the need to judge source performance. It gives every source the same starting standard.

For the underlying checking mechanism, see Lead validation. For the managed programme itself, see Managed lead generation.

What changes as you add sources

A consistent programme should make it possible to ask the same questions of each source.

What criteria is this source working to? What information is required on the record? How are duplicates across sources handled? What happens when a record does not pass the checks?

Those questions are more useful than waiting for a source to become obviously “bad”. Dropping a source is easy to say; deciding that it should be dropped requires a consistent basis for judging it.

The same applies when growth comes from adding channels rather than more suppliers. The principle is not tied to one media type. The programme needs a standard that survives the extra complexity.

Consent and provenance as you grow

More sources can also mean more capture forms and more consent wording.

That matters because a later question about consent or origin is usually a question about one particular record: where it came from, when it was captured and what was recorded at that moment.

On a LeadScale programme, the source, timestamp, consent given and record lineage are written onto the record when it is created and travel with it. Audit trails continue through delivery, and delivery is reconciled against the order.

That gives the buyer's compliance function factual evidence to review later instead of relying on a supplier name and trying to reconstruct the capture event from separate files.

A supplier collecting the data does not remove the buyer's need to know what was recorded. Whether that evidence satisfies a particular legal or regulatory obligation is a matter for the buyer's own compliance function and legal advisers.

What reaches the buyer

Delivered leads have passed the four quality checks against the same programme specification.

Where cross-source comparison is configured, the same person can be identified across sources before delivery. The record also carries its consent and provenance as data fields rather than as a legal conclusion.

The capabilities behind this include Lead validation, the LeadScale Engine™, Managed lead generation and Consent and provenance.

A CRM company that cut its cost per lead

New publishers vetted and added, existing partners managed by LeadScale, and the cost per lead fell.

Frequently asked questions

Will one standard reduce our volume?

It can reduce what is delivered if records fail our checks. ~25% of publisher records fail our checks before a client is billed for them: average across LeadScale programmes. The figure for your programme depends on its specification. The purpose of the standard is to make clear what counts as an acceptable delivered record before you add more sources.

How do we know which source is causing a problem?

Start by making sure every source is being judged against the same agreed criteria. On a Services programme we name every publisher and report how each one performs, including how many of its leads we accepted and rejected, and why.

Can we add channels as well as suppliers?

Yes, the principle is channel-neutral: the sources feeding the programme need to work to the same agreed specification. The detailed channel plan belongs to the programme itself rather than this page.

What should we ask before adding a new source?

Ask whose form is being used, what information it captures, what consent is recorded, what is written onto each record at creation and how the programme handles the same person appearing through more than one source.

Does this make the programme compliant?

No process described here can make that legal judgement for you. What it can do is preserve the source, consent and audit information your compliance function needs to review.

Is this the same as lead scoring?

No. Scoring helps prioritise records according to selected signals. This is about the state of the record before delivery and whether sources are being held to the same agreed standard.

Planning to add sources?

Book a discovery call and bring the brief your current sources work to, plus the sources or channels you are considering adding.