AceLeads
Verified B2B leads, on demand
Skip to content

The standard, in full

What we accept,
and what we reject.

A lead is accepted when five things are true: the contact details are well formed and usable, the enquiry was made knowingly by the person named, the consent evidence travels with it, it fits the brief it was sent on, and it is not a duplicate. AceLeads screens every lead the moment it arrives and decides it within 48 hours. It is accepted, held for a person to look at, or rejected with a named code from the published list, and every outcome can be appealed.

This is the policy, not a summary of it. Disputes are what kill affiliate programmes, and they start wherever a standard is left to judgement, so every rule below is written to be checkable by you: before you send a lead, and again after we decide one.

  • A named code on every decision
  • Decision within 48 hours
  • Every decision is disputable
  • Your acceptance rate shown back to you

One lead, end to end

Receipt to decision, inside 48 hours

  1. Received and timestamped

    Every submission gets a receipt carrying our timestamp. That timestamp is what the duplicate rule and the decision window both run on, and it is the artefact a dispute is settled with.

  2. Screened on arrival

    Contact details are validated for form and the record passes the junk filter: placeholder names, disposable mailboxes, keyboard walks and impossible phone numbers.

  3. Matched against the brief

    Geography, the qualifying criteria the brief publishes, the consent trail, and the duplicate window across every affiliate on the programme.

  4. Decided within 48 hours

    Accepted, held for a person to look at, or rejected with a named code. A held lead is still decided inside the window, and any outcome can be appealed.

The universal minimum

Five things every lead has to be, whatever the brief.

Briefs differ on what they buy and where. They do not differ on these. A lead that clears all five and carries what its brief asks for is an accepted lead, and it goes on the board at the fee its brief publishes. What you are paid does not move with whether the buyer wins the work.

Contact details that are usable

A validly formed UK phone number that is not in a reserved or placeholder range, and a properly formed email address that is neither a disposable mailbox nor a shared office inbox. The check is on the record rather than on the line: we do not dial the number or probe the mailbox before a lead lists, so validate both on your own form where a typo can still be corrected. A number that rings out, goes to voicemail or is not picked up three times is a working number, and it is never a rejection.

A genuine enquiry, made knowingly

The person filled the form in themselves, on a page you control, knowing they had asked about this thing and that somebody would be in touch about it. That rules out records typed on somebody else’s behalf, prize draw and free-gift entries, and anything harvested rather than submitted.

Consent evidence attached to the record

The form URL, the exact wording that was shown, the timestamp and the IP address, travelling with the lead rather than sitting in a system we cannot see. It is what makes the enquiry lawful for a buyer to work, and it is required on every brief without exception.

Inside the brief it was sent on

Each brief publishes the fields to send, the geography it covers and the qualifying detail that separates an enquiry it buys from one it does not. The brief is the standard. Nothing is judged against a general sense of quality, because a rejection you cannot act on is worth nothing to either of us.

Not a duplicate

Not one we already hold from you, and not one another affiliate reached us with first. Matching runs on the normalised phone number and the lower-cased email address, across the whole programme, for 90 days back from the moment we receive your submission.

A brief adds, it never subtracts. Each of the published briefs sets out the fields to send, the geography it covers and the qualifying detail that lifts a lead a tier. None of them can waive one of the five above, and none of them can invent a sixth.

Three outcomes, and the codes behind them

Accepted, held, or rejected with a named code.

There is no fourth outcome and no unnamed one. Every decision quotes the codes that produced it, and the code you see is the code stored against the submission. The list is published in your portal and versioned, a brief may narrow the part of it that applies, and nothing can widen it in the moment: the codes are enforced in the screen and in the database together rather than in a policy document somebody could edit.

Accepted

The lead clears the screen and goes on the board for buyers. Acceptance closes the screening window: after 48 hours no screening ground can be applied to that lead at all.

Held

A person looks at it, because the evidence is suggestive rather than conclusive. Most of the plausibility and near-match codes hold rather than refuse, deliberately, so that a real seller is never silently binned by a rule. A held lead is still decided inside the 48 hours and you are told the code holding it.

Rejected

The lead comes back to you with the code and the fix. Nothing is charged, nothing is earned, and the lead stays yours to place elsewhere. You can appeal any rejection.

Format and deliverability

The record cannot be worked as it stands

  • email_invalid
  • email_undeliverable
  • email_disposable
  • phone_invalid
  • phone_fake_range
  • phone_voip
  • postcode_partial
  • postcode_unknown
  • name_placeholder
  • not_uk

An address that is malformed, disposable or a shared office inbox nobody reads. A number that is not a valid UK number, or sits in a reserved range that cannot be dialled. A name that reads as placeholder text. An outcode where the brief needs a full postcode. An enquiry that is positively not in the UK. A VOIP number is flagged rather than refused, because buyers do work them.

How to avoid it. Validate the number, the address and the full postcode on your own form. Most of this layer is one validation attribute away from never happening again, and a typo caught at the form is a lead instead of a refusal.

Self-dealing

The contact details are your own

  • self_dealing
  • self_dealing_near

The details match, or closely resemble, the records of the business sending them. An exact match is refused. A near match is held for a person, because a genuine collision does happen and the cost of binning a real seller silently is higher than the cost of an hour.

How to avoid it. Nothing to fix if it was a coincidence, and a held lead gets looked at by a person who can say so. Appeal it and say what the overlap is.

Duplicates and suppression

We already have this person, or cannot contact them

  • duplicate_own
  • duplicate_platform
  • recycled
  • suppressed

You have sent them before, somebody else reached us with them first, they were listed inside the last 90 days, or they have asked not to be contacted at all. Matching runs on the normalised phone number and the lower-cased email address, across every seller rather than across your own submissions only.

How to avoid it. Normalise phone numbers and lower-case email addresses before you post, and never send an empty string for a field that might be matched on. Omit the key instead.

Consent evidence

The evidence did not arrive, or it is not this enquiry’s

  • consent_missing
  • consent_not_unique

All four consent fields or none: the form URL, the wording shown, the timestamp and the IP. A partial consent record is not weaker evidence, it is unusable evidence. Separately, evidence byte-identical to other leads you have sent is held rather than refused, because identical evidence across a batch evidences none of it.

How to avoid it. Send all four fields on every record, and store the wording verbatim per submission rather than a boolean. The compliance page sets out each field in full.

Plausibility

The pattern does not look like a person filling in a form

  • geo_mismatch
  • velocity
  • too_fast

A submission IP a long way from the postcode given. An unusual number of leads from one source inside a short window. A form completed faster than a person can type. Every code in this layer holds the lead for a person rather than refusing it, because each has an innocent explanation often enough to matter.

How to avoid it. Usually nothing, and a held lead is reviewed rather than binned. If a campaign is going to produce a burst, tell us beforehand and it stops being unusual.

The brief itself

A genuine enquiry the brief cannot take

  • missing_required
  • stale

A field the vertical requires is missing, the vertical is not one we buy, or the enquiry is older than the brief accepts. Freshness is most of what a buyer pays for, and the refusal states the age it arrived at and the age the brief allows, so there is nothing to work out.

How to avoid it. The required fields and the qualifying question are written on every brief before you send anything. Ask them on the form rather than hoping a free-text box covers it, and send leads as they arrive rather than in a nightly batch.

Most of these are fixable at the point of capture, usually by adding or validating one field on a form, which is why the fix matters more to you than the refusal does. Your reason mix in the portal splits them the same way, so you can see which layer a source is failing at rather than only that it is. What an accepted lead is worth once it clears all of this is on the what we pay page.

Duplicates

The rule that causes the most suspicion, in full.

Duplicate is the one rejection you cannot verify from your side, because you cannot see anybody else’s inventory. So here are the mechanics: what is compared, how far back, who it is compared against, and which submission wins.

How the programme works
What is compared
The phone number, normalised, and the email address, lower-cased, against the brief the lead was sent on. Nothing else. A shared surname, a shared household or a shared IP address is not a duplicate.
How far back
90 days, counted back from the moment we receive your submission rather than from when you captured it. The same window applies on every brief, and a brief that needs a shorter one says so on its own page.
Against whom
Every affiliate on the programme, not only you. That is worth knowing before you buy a data set or work a channel somebody else is already working, and it is why an enquiry you have placed with another network often comes back to us as a duplicate.
Which one wins
The first one we received, on our receipt timestamp. Not the earliest capture date, not the more complete record, and not whoever raises it first. The later submission is the duplicate even when it is the better lead.
Your own retries
A double click, or a retry after a timeout, is the commonest duplicate of all and it is entirely avoidable. Send the same idempotency reference on a retry and it is treated as one lead arriving twice rather than as two leads.
On any duplicate rejection
You are told the date the matching record reached us. Somebody who cannot say what they matched cannot really say it is a duplicate, so we say it up front instead of on request.

The false positive nobody warns you about. If a field used for matching arrives as an empty string, it can collide with every other empty string in the table and genuine leads get refused in a batch. Omit a key you have no value for. Never post it blank.

Not a rejection

What we do not reject for, which matters just as much.

A closed list of reasons is only worth something if the things outside it are named too. Every item below has been used by somebody, somewhere, as a reason not to pay a lead generator. None of them is a reason here, and none of them quietly becomes one later.

Short names, single names, no surname

Bo, Li and Al are real people, and plenty of forms only ask for a first name. A name on its own is not evidence of anything.

Lower case, capitals throughout, odd spelling

A form filled in one-handed on a phone looks exactly like this. So does a name our spell-checker has never met. Neither is a quality signal.

A free email provider

Gmail, Hotmail, Yahoo and iCloud addresses are what most of the UK uses, including most of the people buying the jobs behind these briefs.

A missing postcode where the brief does not need one

Postcode is required only on briefs that route buyers by area, and those briefs say so on the page. We do not fail a lead for a field the brief never asked for.

A customer who later goes quiet

Once we accept a lead, chasing it is our problem. Somebody who answered a form and then stopped answering the phone is ordinary, and it is not a fault in the lead you sent.

A buyer who fails to convert

Not on the list, and it never will be. Reaching back into a payment because somebody downstream did not close is the commonest way a programme quietly stops paying.

An awkward hour or an uneven volume pattern

Leads arriving at three in the morning, or twenty at once, are a reason to talk to you about the source. They are not a reason to reject anything.

A source you tested that turned out to be small

We would far rather see a channel tried and stopped than never tried at all. Nothing about testing counts against you anywhere in your record.

There is no hidden scoring model behind any of this, and no quality score that quietly moves what a lead is worth. A lead is accepted, held for a person, or rejected with the code named, and an accepted one carries the tier its brief publishes. The tiers, and the point at which the money is actually yours, are set out on the what we pay page.

Automated screening

The junk filter, described honestly.

Every submission passes an automated check before a person sees it. It exists because a fabricated record satisfies commercial criteria exactly as easily as a real enquiry does, and one obvious fake reaching a buyer undoes a lot of goodwill. Here is precisely what it looks for.

Placeholder names and addresses

Words no genuine enquiry contains: test, testing, dummy, fake, sample, unknown, firstname, yourname, John Doe. The same short word given twice as a first and last name. A name with fewer than two letters in it.

Disposable mailboxes

Throwaway providers whose addresses are built to stop existing shortly after they are created, along with the domains set aside for testing. A real person’s free webmail address is a different thing entirely and is never touched.

Keyboard walks and letter runs

qwerty, asdfg, zxcvb, 12345, and the same letter three or more times in a row. This is what a required field gets filled with when somebody is trying to get past it.

Impossible phone numbers

A single digit repeated the whole way, a straight sequential run, and the well-known placeholder ranges. A merely wrong or mistyped number is not caught here, because binning a real customer is worse than passing on a bad number.

The bar is deliberately set too high. Every rule is one a genuine UK enquiry cannot trip, and anything merely odd is left alone. A real customer binned by a filter is invisible to everybody, including us, so we would rather let an unusual record through and judge it against the brief instead.

It does not judge whether a lead is any good. Clearing the filter is not acceptance, and a record that passes still has to meet the brief. A record that fails comes back under the format code that caught it, usually name_placeholder, email_disposable or phone_fake_range, and the refusal names the pattern it tripped rather than leaving you to guess.

The window

When we can reject, and how you push back.

The decision window is the reason an acceptance can be final. All the verification happens while it is open, so nothing has to be reopened once it closes.

A lead can be rejected for 48 hours from the moment we receive it, and the clock runs on our receipt timestamp rather than on your capture time, so a lead you held back for a day does not lose any of its window. Inside it, the lead is accepted, held for a person, or rejected with the code named. Outside it, no screening ground can be applied to that lead any more.

After that, the only route back into an accepted lead is the reversal list, which runs to five grounds, is published in full on the what we pay page in the same words as the agreement, and does not grow. Each needs evidence, and each is disputable. A buyer failing to convert is not on it and cannot be added to it.

A held lead is not a lead left pending. It is one a person is looking at, you are told which code is holding it, and it is still decided inside the 48 hours. If the window passes with no decision reaching you, the lead has not been rejected: tell us and it is decided the same working day. What has to be true about consent before any of this applies is set out on the compliance page.

01

Raise it

Reply to the decision notice, or open the submission in your portal and dispute it there. You have 30 days from the decision, and raising one costs you nothing.

02

Send the artefact, not the argument

The dialler log or recording showing the number connected. The consent record with its form URL and timestamp. On a duplicate, your own timestamped receipt. Disputes carrying evidence get upheld; disputes carrying annoyance do not.

03

Somebody else looks again

A rejection appeal is acknowledged within one working day and decided within five, by a person who did not make the original call. A dispute of a reversal after acceptance takes longer and is decided within ten business days, because there is usually a third party to go back to.

04

You get the outcome and the reasoning

Upheld, and the lead moves to accepted and goes on the board, earning its fee at the tier it qualifies for if it sells. Not upheld, and you get the evidence we relied on, including, on a duplicate, the date the matching record reached us.

Raising a dispute costs you nothing and there is no limit on how many you raise. The act of disputing is not held against you anywhere and a programme that treats appeals as friction is a programme relying on you not bothering. Be clear about one thing though: the rejection itself does count towards your rejection rate while it stands, and an upheld dispute takes it back out, which is the practical reason to raise one rather than let it go. The contractual wording that governs decisions, reversals and the rejection-rate pause sits in the affiliate agreement, that agreement is a draft pending solicitor review, and where this page and the signed agreement ever differ it is the agreement that governs.

Your acceptance rate

A number you can recalculate yourself.

Most programmes will not tell a lead generator what share of their leads are being taken. Seeing it, broken down by the code that moved it, is the fastest way to find a channel that is quietly costing you money.

Apply to send us leads
The calculation
Accepted leads divided by decided leads, where decided means accepted plus rejected. That is the whole formula, and there is nothing weighted hiding inside it.
What is left out
Anything still inside the decision window sits in neither half. A batch you sent this morning cannot pull the figure down before it has been judged, and it cannot flatter it either.
Over what period
Month to date by default, and over any range you choose. Nothing is smoothed, averaged across months, or carried forward from an earlier period.
Broken down by
Reason code and source, so a rate that moves arrives with the reason it moved. brief_closed and cap_reached show separately, because that part of the number is ours rather than yours.
What it is not
It is not a league table. Your portal holds no programme average and no comparison against another affiliate, because your rate is a property of your sources rather than a score we grade you on.
If it drops
We come to you with the code that is driving it, and the point of showing you the number is that you can act on it before we need to. Above one threshold that stops being a conversation: see the row below.
The one automatic consequence
If your rejection rate goes above 15% over any rolling 30 days, listing pauses on its own while we review it with you. It is not a penalty and no fee is charged, but it is automatic and it happens before anybody rings you, so the live figure in your portal is the thing to watch rather than your inbox.

Non-negotiable

Two things every lead has to clear.

These apply to every brief on this page and every brief we run. They are not preferences, and a lead that misses either is rejected whatever else is right about it.

Your capture pages meet the standard

Every page you generate from has to be built to UK GDPR and PECR standards, not close to them. That means a real privacy notice, consent that is specific, informed and freely given, no pre-ticked boxes or bundled permissions, and AceLeads or a clearly described category of recipient named at the point of capture.

Consent evidence travels with the lead: the timestamp, the IP, the page URL and the exact wording the person was shown. Consent you cannot produce is consent you do not have.

What we require, in full

Every lead is verified before it counts

Leads are verified on the way in, by you before you send and by us on receipt. Contact details are checked, duplicates are caught across every affiliate rather than just your own, and known junk patterns are filtered automatically.

This protects your earnings as much as our buyers. A verified stream gets a higher acceptance rate, and a clean sender gets the briefs with the best rates first.

How a lead is judged

We audit capture pages, and we will ask to see one before your first lead is accepted. This is not box-ticking: under the Data (Use and Access) Act 2025 the maximum PECR penalty is a matter of public record, and a lead sourced from a bought list puts both of us in front of it.

FAQ

Acceptance and rejection, settled.

The questions that turn into arguments later if they are left open now. Ready to pick a vertical? Read the briefs.

What makes a good lead?

Usable contact details, an enquiry the person made knowingly and recently, consent evidence attached to the record, everything the brief asks for, and no earlier copy of the same person anywhere on the exchange. Those five are the universal minimum and they apply to every brief we publish. Each brief then adds its own qualifying detail, which is what lifts a lead from the raw tier to the qualified one, and that detail is written on the brief before you send anything.

Why was my lead rejected?

Because it tripped one of the published screening codes, and the notice names which. The codes fall into six layers: format and deliverability, self-dealing, duplicates and suppression, consent evidence, plausibility, and the requirements of the brief itself. Each layer is explained on this page with the codes inside it and what to change at the point of capture. Nothing outside the published vocabulary can be recorded against a lead, because the code has to exist in the screen and in the database before the decision can be written at all.

What does it mean when a lead is held?

That a person is looking at it. Some codes refuse a lead outright and some hold it, and the split is deliberate: where the evidence is suggestive rather than conclusive, a human decides. Near-matches to your own business records, an unusual burst of volume from one source, a form filled in faster than a person can type and consent evidence that is identical to other leads you have sent all hold rather than refuse, because each of them has an innocent explanation often enough to matter. A held lead is still decided inside the 48 hours and you are told the code holding it.

Can you reject a lead after you have accepted it?

Not on a screening ground. After 48 hours no screening ground can be applied to a lead at all. What can still happen is a reversal, on five grounds that are published in full on the what we pay page in the same words as the agreement: the enquiry is denied or the consent evidence does not stand up, the same enquiry went to somebody else as well, it duplicates a lead already sold here within 90 days, it came from a prohibited source or a detail was invented, or a complaint or investigation is raised about it. That last one can cost you a fee with nothing found against you, which is why it is on the page rather than only in the document. All five are disputable, and a buyer who fails to convert is on none of them.

What counts as a duplicate, and whose submission wins?

A duplicate is the same person on the same brief inside 90 days, matched on the normalised phone number and the lower-cased email address. The window runs across every affiliate on the programme rather than across your own submissions, so an enquiry you have already placed with another network tends to come back to us as a duplicate. The first submission we received wins, judged on our receipt timestamp rather than on capture date or on who raises it first, and every submission carries that timestamp so you can check where you were in the queue.

Do you reject leads for having a Gmail address or only a first name?

No. Short names, single names, no surname, lower case, capitals throughout, unusual spellings and free email providers are all specifically not filtered, because real people do all of them constantly. Nor do we reject for a missing postcode on a brief that does not route by area, or for a customer who later stops answering the phone. The screening is built to catch records that cannot be genuine, not records that look untidy.

How do I dispute a rejection?

Reply to the decision notice, or dispute the submission from your portal, within 30 days of the decision. Send evidence rather than an argument: the dialler log showing the number connected, the consent record with its form URL and timestamp, or your timestamped receipt on a duplicate. We acknowledge within one working day and decide within five, and the person deciding is not the person who made the original call. If it is upheld, the lead moves to accepted and goes on the board. Disputing a reversal after acceptance uses the same route but takes longer: that one is decided within ten business days, and a reversal successfully disputed is reinstated in the next payment run.

How is my acceptance rate worked out?

Accepted leads divided by decided leads, where decided means accepted plus rejected. Anything still inside the decision window is left out of both halves, so a batch you sent this morning cannot drag the figure down before it has been judged. It runs month to date by default and over any range you pick, and it is broken down by reason code and by source so you can see which channel is moving it.

Does a rejected lead still belong to me?

Yes. A rejected lead stays yours, we make no claim on it, and it is never released to a buyer or placed anywhere. We keep the submission record itself, because that record is what a dispute is settled with and what proves the decision we made. You are free to place the lead elsewhere.

Test it on one lead

Standards are only worth what they do on a real submission.

Apply, take a brief, send a single lead, and hold the decision up against this page. Everything here is checkable inside 48 hours, which is exactly how long you should give us before deciding whether any of it is true.