Loading tutorials…
Loading tutorials…
Apollo's database is 275M+ contacts — meaningless without precision filters. This walks the persona builder, Boolean title logic, and the signal filters that separate qualified prospects from credit drain.
Who this is forB2B sales operators using Apollo Search who are burning credits on contacts that sales rejects. If your list-to-meeting ratio is below 0.5%, your filters are the problem — not your sequences.
What you'll need
Step 1
Write the ICP on paper first: industry, size, geo, titles, signals to include, signals to exclude. Apollo filters are the implementation — not the strategy.
Open a doc. Write your ICP across 6 dimensions: Industry (specific NAICS or Apollo industry), Company size (employee count range), Geography (countries/regions/states), Buyer titles (decision maker + influencer), Tech stack signals (do they use X?), Intent signals (hiring for Y, recent funding).
Example tight persona: "B2B SaaS, 50-500 employees, US/Canada/UK, Director+ in Marketing or Demand Generation, uses HubSpot, posted job for Demand Gen role in last 60 days."
Define disqualifiers explicitly: industries to exclude (lookalike competitors, agencies if you sell to brands directly), company-size limits (below 20 employees often = solo founders, above 5,000 = enterprise cycle too long for current capacity).
Validate the persona with sales: 'If we hand you 100 contacts matching this exactly, can you book at least 5 meetings?' If sales says no, the persona is wrong — fix it before exporting a single contact.
Most Apollo waste happens because the persona was never written down. The first filter setup is exploratory, not committed — refine after 100 contacts of sales feedback.
Step 2
Apollo → Search → Companies. Stack Industry + Employees + Revenue + Country. Save as a named search before adding contact filters.
Open Apollo → top nav → "Search" → "Companies" tab.
Industry: use the multi-select. Apollo industries are taxonomically broader than NAICS — "Computer Software" includes both consumer apps and enterprise SaaS. Stack 2-3 if needed. Use the "Keywords" filter to narrow further (e.g., Industry = SaaS, Keywords = "vertical SaaS" or "manufacturing software").
Employees: pick a range. 1-10 = solos and very small startups (low intent buyers). 11-50 = early stage (often no budget). 51-200 = sweet spot for most B2B SaaS sellers. 201-1,000 = mid-market with proper procurement. 1,000+ = enterprise (long cycles, gatekeepers).
Annual revenue: cross-reference with employees. Companies with high revenue per employee = services/agencies; low rev/employee = product companies or hardware.
Country: avoid stacking too many. Each country has different legal compliance for cold outbound (GDPR in EU, PIPEDA in Canada, CASL stricter than CAN-SPAM). Start with one tier-1 country.
Save the company search: top right → "Save Search" → name it "[Persona Name] — Companies." You will reuse this across multiple contact searches.
Step 3
Apollo title field accepts Boolean: OR, AND, NOT, quotes for exact match. This is the single biggest filter precision lever — and it is invisible by default.
Switch from Companies tab to People tab. Apply your saved company filter.
In the "Title" field, type your title query as Boolean. Click "Use Advanced Title Search" toggle (it switches between literal and Boolean mode).
Example Boolean: ("VP Marketing" OR "Vice President Marketing" OR "Head of Marketing" OR "Director of Marketing" OR "Director of Demand Generation" OR "VP Demand Gen") AND NOT ("Field Marketing" OR "Product Marketing" OR "Brand Marketing")
Quotes = exact phrase match. OR = any of these. AND NOT = exclude these. Combine to capture every variant of your target role while excluding adjacent-but-wrong roles.
Pro tip: search LinkedIn for 20 real people in your target role. Note every title variant they use. Build the Boolean string from real data, not assumption.
After Boolean: layer Seniority filter (Director, VP, C-Suite) as a second precision layer. Title + Seniority + Department is the 3-axis precision stack.
Step 4
Apollo signals: Technologies used, Job postings, Funding events, Recent news. These convert prospect lists from cold to lukewarm.
Technologies: in the People search → "Technologies" filter. Apollo detects ~6,000+ tools via website scraping. Filter for companies using your competitor (high intent — they have budget for this category) or your complement (your tool fits their stack).
Job postings: filter "Posted job in [department] in last [30/60/90 days]." A company posting a Demand Gen role is actively investing in demand gen — they need tools to make that role successful.
Funding events: filter "Raised funding in last 90 days." Post-funding companies are spending. Specifically: Series A is hiring growth, Series B-C is scaling operations.
News mentions: "Mentioned in news for [keyword] in last 30 days." Use for trigger-based outreach (mentioned product launch, leadership change, expansion).
Layer 1-2 signal filters maximum. Stacking 4+ collapses your audience to under 50 contacts — too narrow to validate the persona.
Signal-filtered contacts cost the same Apollo credits as cold contacts but typically reply at 3-5x the rate.
Step 5
Apollo → top right → "Save Search" → name it like a persona. Saved searches power Sequences, Plays, and weekly refresh exports.
Click "Save Search" in the top right of the People search. Name by persona, not by query.
Name format: "[ICP Name] — [Geography] — [Seniority]." Example: "B2B SaaS Marketing Leaders — US — Director+."
Saved searches re-run live every time you open them. New contacts matching the criteria appear automatically as Apollo updates its database (weekly).
Set up notifications: Saved Search → bell icon → "Notify me when new matches." Apollo will email you weekly with new prospects matching the persona.
For each persona, save ONE search. Multiple semi-overlapping searches for the same persona create contact-sequencing conflicts (the same person enters two sequences).
For Plays (Organization plan): Plays trigger off saved searches with intent signals. "Notify rep when contact at HubSpot-using company posts a Demand Gen job."
Step 6
Apollo → Settings → Suppression Lists. Upload customers, closed-lost, do-not-contact, and competitors. Auto-exclude from every persona search.
Apollo → Settings → "Suppression Lists" → "Create Suppression List."
Build at least 4 suppression lists: Current Customers (from CRM), Closed-Lost (last 12 months), Active Opportunities (do not double-prospect), Do-Not-Contact / Unsubscribed.
Format: CSV with one column "Email." Upload. Apollo matches against any prospect in your searches.
For company-level suppression (no one at Acme should be contacted): upload a CSV with "Domain" column instead. Apollo excludes everyone at the matching domain.
Refresh suppression lists monthly. CRM data drifts — last month's closed-lost is this month's opportunity; last month's customer churned.
Without suppression, you will prospect your own customers, embarrass your sales team, and trigger 'I'm already a customer' replies that destroy reply-rate metrics.
Common mistakes
Literal title matching instead of Boolean
What goes wrong: Typing "VP of Marketing" literally matches only that exact string. You miss "Vice President, Marketing," "VP Marketing & Growth," "Head of Marketing" — collectively 40-70% of your target audience. Export quantity is small AND quality is skewed.
How to avoid: Toggle "Advanced Title Search" to Boolean mode. Build a (OR | OR | OR) AND NOT (OR | OR) string covering every real-world title variant. Refresh quarterly as titles evolve.
Apollo industry filter without keyword refinement
What goes wrong: Apollo "Computer Software" includes everything from consumer mobile apps to enterprise SaaS. Without keyword refinement, you prospect across 10 unrelated verticals and reply rates collapse below 0.5%.
How to avoid: Always pair Industry filter with Keywords filter for vertical precision. "Industry: Computer Software" + "Keywords: vertical SaaS" or "Keywords: HR tech" narrows correctly.
No suppression lists configured
What goes wrong: You prospect existing customers, closed-lost accounts, and active opportunities. Sales team complaints, embarrassing replies, and waste of 5-15% of your monthly Apollo credits. Reply rate looks worse than reality because angry "already a customer" responses count as replies.
How to avoid: Set up 4 suppression lists at minimum: Customers, Closed-Lost, Active Opps, DNC. Refresh monthly from CRM.
Too many filter layers (over-narrowing)
What goes wrong: Stacking 8+ filters (Industry + Employees + Revenue + Country + Title + Seniority + Tech + Job Posting + Funding) collapses your audience to 30-50 contacts. Too small to test the persona; sequencing this audience is a 1-week experiment with no statistical signal.
How to avoid: Stack 4-5 filters maximum: Industry + Employees + Country + Boolean Title + 1 signal. Target audience size: 500-5,000 for a meaningful test. Below 200 = too narrow.
Not validating personas with sales before sequencing
What goes wrong: You build a persona, export 1,000 contacts, send them through a sequence, get 8 meetings, hand them to sales. Sales says 6 of 8 are unqualified. You burned $500-1,000 in credits + sequence time on a wrong-fit audience.
How to avoid: After building the persona, export 25 contacts and walk them through with sales rep manually. "Would you accept a meeting with this person if booked?" Validate fit before sequencing scale.
Stale saved searches that never refresh
What goes wrong: Saved search built 6 months ago still pulls contacts. But your ICP shifted, your tech-stack signal changed (competitor pivoted), or your geography expanded. You burn budget on a persona that no longer reflects who you want.
How to avoid: Quarterly persona review. Re-open every saved search, re-validate criteria, update Boolean strings, refresh suppression. 30 minutes per persona per quarter.
Recap
Done — what's next
How to set up an Apollo.io account the right way
Read the next tutorial
Hand it off
Filter quality is where Apollo accounts succeed or fail. A demand generation specialist will build 3-5 personas with Boolean logic, signal stacking, and validated sales-team fit in 4-6 hours. From $14-16/hr — most ongoing engagements include weekly persona refresh and refinement. Compare to burning $1K/month in Apollo credits on a wrong-fit audience.
See specialist rates
Sweet spot: 500-5,000 contacts per persona. Below 200 = too narrow to test. Above 10,000 = persona is too loose. If you are below 200 after filter stacking, remove the weakest filter. If above 10,000, add a signal filter (tech, job posting, funding).
Apollo personas are search-time queries against the Apollo database. CRM personas are tagging on contacts already in your CRM. Use Apollo personas for prospecting (finding new contacts) and CRM personas for nurture/scoring (segmenting contacts you already own). Both are needed.
Cold outbound benchmarks: 1-2% reply rate is poor (filter or copy issue). 3-5% is the typical SMB B2B baseline. 5-10% is well-targeted with strong subject lines. Above 10% is exceptional and usually requires both tight filters AND personalized first lines.
Yes — Apollo accepts CSV imports of contacts (emails or LinkedIn URLs). Then use Apollo for sequence sending. But you lose Apollo's data refresh and signal layering on imported contacts. Best practice: use Apollo Search as your primary prospecting source and CSV import only when you need a specific external list.
Quarterly minimum. Sooner if your ICP shifts, you launch in a new vertical, or sales feedback shows persona drift. Apollo data refreshes weekly automatically — but your filter criteria need human refresh.
Apollo.io
Apollo has the cheapest entry into B2B sales intelligence, but the default account configuration will silently torch your domain reputation. This walks the exact setup order that keeps your inbox warm and your credits efficient.
Apollo.io
Sequences are where Apollo earns its $99/seat. They are also where most operators destroy their sender reputation. This walks the right step structure, cadence, personalization layer, and reply handling that books meetings without burning inboxes.
Apollo.io
Apollo + CRM is where most B2B teams shoot themselves in the foot. Wrong sync direction, missing dedup, mapping mistakes — and within 30 days your CRM has 4,000 duplicate contacts. This walks the safe integration order.
Apollo.io
DIY Apollo is a fine idea — until it isn't. This is the honest framework: when the cost of self-managing exceeds the cost of hiring, and how to tell which side you're on.