NovoVeja como
FirstSales
Todas as novidades
Novo5 min de leitura

See how good your lead sources really are

AI Leads and Maps Scraper now show a quality funnel from results in to verified to actually paid for, with one shared identity and credit trail across every import path.

New

See how good your lead sources really are

Contact Harvester panel with AI Leads and Maps Scraper sources

Until now, it was hard to tell how much of what a lead source pulled in was actually usable. AI Leads and Maps Scraper now show you a quality funnel: how many results came in, how many got verified, and how many you actually paid for. Every way you bring contacts into FirstSales now shares one identity, one source receipt, and one exact credit trail.

What changed

When you run AI Leads or the Maps Scraper, you now see a funnel instead of a single result count. It breaks down into three stages: results in (everything the source returned), verified (the subset that passed verification), and actually paid for (the subset you were charged credits for). Before, you saw a final number without the steps behind it, so if a source looked weak, you had no way to tell whether the problem was the source itself, the verification step, or something else entirely between those two points.

Behind this, every contact that enters your workspace, whether from AI Leads, Maps Scraper, or any other import path, now shares one identity system. That means the same person found through two different sources gets recognized as the same contact instead of creating a duplicate. Each contact also carries a source receipt, a record of exactly where it came from, and an exact credit trail showing what you were charged and why, down to the specific search or run that produced it.

The practical effect is that duplicate contacts and duplicate verification charges are no longer possible across import paths. If AI Leads and Maps Scraper both surface the same person, you are not billed twice for verifying them, and they do not show up twice in your contact list splitting your outreach history for the same prospect across two separate records.

This shared identity system also protects the integrity of your campaign history. Before, if the same prospect entered your workspace through two different sources months apart, you could end up with two separate records, each with its own partial view of whether that person had already been contacted, replied, or opted out. A split identity like that risked re-contacting someone who had already told you no, or losing track of a conversation that had already started. With one identity per person across every source, that risk goes away, and your outreach history for a given prospect stays whole no matter how many different searches or scrapes eventually touched them.

How to use it

Run a search in AI Leads or Maps Scraper as you normally would. When results come back, look at the funnel instead of just the final count. If "results in" is high but "verified" is low, the source is returning a lot of noise for that particular search. If "verified" is high but "actually paid for" is lower, check your verification settings, since that gap usually means results that did not clear your quality bar for spending credits, not a billing error.

Use the funnel to compare sources against each other over time. If one source consistently converts a higher share of its results into verified, paid contacts, that is a strong signal to lean on it more for future prospecting. If another source consistently loses most of its results at the verification stage, it may not be worth running as often, even if its raw result count looks impressive at first glance.

When you want to know where a specific contact came from, check its source receipt. This tells you which search or scrape brought that contact in, which is useful when you are deciding whether to trust a lead's context or when you are reviewing spend against a particular campaign or list, especially months after the original import.

It is worth checking the funnel regularly rather than only when a source seems to be underperforming. A source that starts strong can degrade over time as it exhausts the easy matches for a given search and starts returning weaker results, and the funnel is the fastest way to notice that shift before it quietly eats into your budget. Comparing this week's funnel against last month's for the same kind of search tells you whether a source is still worth running the way you have been running it.

Why it matters

Lead generation spend only makes sense if you know what you are actually getting for it. A raw result count told you almost nothing about quality, and without a shared identity across sources, you could end up paying to verify the same person twice without realizing it, quietly inflating your cost per usable contact. The funnel gives you a direct way to judge a source's real yield, not just its raw volume, and the shared identity and credit trail mean your spend reflects real, unique contacts rather than duplicates hiding across different import paths.

This also makes it easier to hold sources accountable. If you are deciding between running more AI Leads searches or more Maps Scraper runs, you now have the numbers to make that call based on what each source actually delivers, not a guess based on how big the initial result count looked.

For teams managing budget across several people prospecting at once, this level of detail also makes it possible to set expectations honestly. You can tell a teammate that a given search type typically converts a certain share of results into paid, verified contacts, instead of promising a raw lead count that was never a realistic measure of what would actually be usable once verification and deduplication were accounted for.

None of this requires you to change how you search. The funnel and the shared identity work in the background on every run, so the only thing that changes for you is how much visibility you have into what a source is actually delivering for the credits it costs.

Availability

The quality funnel and shared identity, source receipt, and credit trail apply across AI Leads, Maps Scraper, and other contact import paths now, for both new searches and the contacts already sitting in your workspace.