Amrico's Lead Limiter ๐Delete # leads in the same company
Pricing
Pay per usage
Amrico's Lead Limiter ๐Delete # leads in the same company
Under maintenanceUpload 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
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:
- Groups all leads by their company domain
- For any domain that exceeds your configured limit, removes the lowest-priority leads
- 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)
| Level | Examples |
|---|---|
| 10 - C-Suite | CEO, CTO, CIO, CISO, COO, CFO, CMO, Chief Technology Officer |
| 9 - President / Owner / Founder | President, Owner, Founder, Co-Founder |
| 8 - Vice President | VP of IT, SVP, EVP, Vice President of Engineering |
| 7 - Director | Managing Director, IT Director, Director of Technology, Technical Director |
| 6 - Head / Group Lead | Head of IT, Head of Engineering, Group Lead |
| 5 - Manager / Partner | IT Manager, Managing Partner, General Manager, Principal |
| 4 - Architect / Lead / Staff | Systems Architect, Lead Engineer, Staff Engineer, Principal Consultant |
| 3 - Senior | Senior Engineer, Senior Consultant, Senior Analyst |
| 2 - Mid-level | Engineer, Specialist, Consultant, Analyst, Administrator |
| 1 - Junior / Entry | Junior Developer, Intern, Trainee, Associate, Assistant |
| 0 - Unknown | Any 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
- Upload your CSV file - the file must contain at least a domain column and a job title column
- Specify the domain column name (e.g.
domain,website,company_domain) - or leave blank to auto-detect - Specify the job title column name (e.g.
title,job_title,position) - or leave blank to auto-detect - Set the max leads per domain - for example,
2means keep at most 2 leads per company - Run the actor
- 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, anddomainall 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):
| domain | name | title |
|---|---|---|
| acme.com | Alice | CEO |
| acme.com | Bob | CTO |
| acme.com | Carol | Junior Developer |
| acme.com | Dave | Sales Director |
| acme.com | Eve | IT Manager |
| globex.com | Frank | Managing Director |
| globex.com | Grace | Intern |
Settings: max 2 leads per domain
Output (4 leads):
| domain | name | title |
|---|---|---|
| acme.com | Alice | CEO |
| acme.com | Bob | CTO |
| globex.com | Frank | Managing Director |
| globex.com | Grace | Intern |
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 3globex.com: 4 leads -> kept 2, removed 2...โ Done!Total leads in input: 1,250Unique domains: 340Max leads per domain: 2Domains trimmed: 85Leads removed: 260Leads kept (output): 990