Amrico's Lead Limiter ๐ŸŒŸDelete # leads in the same company avatar

Amrico's Lead Limiter ๐ŸŒŸDelete # leads in the same company

Under maintenance

Pricing

Pay per usage

Go to Apify Store
Amrico's Lead Limiter ๐ŸŒŸDelete # leads in the same company

Amrico's Lead Limiter ๐ŸŒŸDelete # leads in the same company

Under maintenance

Upload a CSV of leads, set a max number of leads per domain, and the actor removes the excess, starting from the lowest job-title seniority and prioritizing tech-sector titles. ๐ŸŒŸPrivate use for Amrico's partners (amr@amrico.net)

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Mando

Mando

Maintained by Community

Actor stats

2

Bookmarked

3

Total users

3

Monthly active users

3 days ago

Last modified

Categories

Share

๐ŸŽฏ Domain Lead Limiter

Limit the number of leads (rows) per company domain in your CSV. When leads must be removed, the actor keeps the most senior people and prioritises technology-sector job titles.


๐Ÿ“Œ What it does

You upload a CSV containing leads scraped from various sources. Many of those leads share the same company domain - for example, 7 employees from one company. You only need 2 or 3 contacts per company, not all 7.

This actor:

  1. Groups all leads by their company domain
  2. For any domain that exceeds your configured limit, removes the lowest-priority leads
  3. Outputs the remaining leads with every column preserved in the exact same order as the input

๐Ÿ† How leads are prioritised (what gets kept vs removed)

Seniority hierarchy (highest to lowest)

LevelExamples
10 - C-SuiteCEO, CTO, CIO, CISO, COO, CFO, CMO, Chief Technology Officer
9 - President / Owner / FounderPresident, Owner, Founder, Co-Founder
8 - Vice PresidentVP of IT, SVP, EVP, Vice President of Engineering
7 - DirectorManaging Director, IT Director, Director of Technology, Technical Director
6 - Head / Group LeadHead of IT, Head of Engineering, Group Lead
5 - Manager / PartnerIT Manager, Managing Partner, General Manager, Principal
4 - Architect / Lead / StaffSystems Architect, Lead Engineer, Staff Engineer, Principal Consultant
3 - SeniorSenior Engineer, Senior Consultant, Senior Analyst
2 - Mid-levelEngineer, Specialist, Consultant, Analyst, Administrator
1 - Junior / EntryJunior Developer, Intern, Trainee, Associate, Assistant
0 - UnknownAny title not matching the above - removed first

Tech-sector priority (tiebreaker)

This actor is built to prioritise technology-sector job titles.

When two leads have the same seniority level, the tech-related title is kept and the non-tech title is removed. For example:

  • Director of Technology (level 7, tech) is kept over Director of Sales (level 7, non-tech)
  • IT Manager (level 5, tech) is kept over Marketing Manager (level 5, non-tech)
  • CTO (level 10, tech) is kept over CFO (level 10, non-tech)

Tech-related titles are identified by keywords such as: IT, technology, engineering, software, infrastructure, cloud, security, cyber, data, DevOps, systems, network, CTO, CIO, CISO, and many more.

When titles are unrecognised

If a job title does not match any known seniority pattern, it is assigned level 0 and will be the first to be removed. Among multiple unknown titles, the original CSV row order is preserved (earlier rows are kept).


๐Ÿš€ How to use it

  1. Upload your CSV file - the file must contain at least a domain column and a job title column
  2. Specify the domain column name (e.g. domain, website, company_domain) - or leave blank to auto-detect
  3. Specify the job title column name (e.g. title, job_title, position) - or leave blank to auto-detect
  4. Set the max leads per domain - for example, 2 means keep at most 2 leads per company
  5. Run the actor
  6. Export the results - the output has the same columns in the same order as your input, minus the removed leads

Column name matching is not case-sensitive. Domain, DOMAIN, and domain all work.


๐Ÿ“ค Output

The output dataset contains exactly the same columns as your input CSV, in the same order. The only difference is that excess leads have been removed. No columns are added or modified.


๐Ÿ“‹ Example

Input CSV (5 leads, 2 domains):

domainnametitle
acme.comAliceCEO
acme.comBobCTO
acme.comCarolJunior Developer
acme.comDaveSales Director
acme.comEveIT Manager
globex.comFrankManaging Director
globex.comGraceIntern

Settings: max 2 leads per domain

Output (4 leads):

domainnametitle
acme.comAliceCEO
acme.comBobCTO
globex.comFrankManaging Director
globex.comGraceIntern

From acme.com, Carol (Junior, level 1), Dave (Sales Director, level 7 non-tech), and Eve (IT Manager, level 5 tech) were candidates for removal. Carol is removed first (lowest level), then between Dave and Eve - Dave is removed because Eve has a tech title. Alice (CEO) and Bob (CTO) are kept as the top 2.


๐Ÿ“Š Log output

The actor logs a clear summary:

๐Ÿ“„ CSV loaded: 1,250 total leads
๐ŸŒ Domain column: "domain"
๐Ÿ’ผ Job title column: "title"
๐Ÿ”ข Max leads per domain: 2
๐Ÿ“Š Found 340 unique domains
โš ๏ธ 85 domains have more than 2 leads (430 leads total in those domains)
โœ‚๏ธ Trimming to 2 lead(s) per domain (keeping highest seniority, prioritising tech titles)...
acme.com: 5 leads -> kept 2, removed 3
globex.com: 4 leads -> kept 2, removed 2
...
โœ… Done!
Total leads in input: 1,250
Unique domains: 340
Max leads per domain: 2
Domains trimmed: 85
Leads removed: 260
Leads kept (output): 990