How do I check how many prospects a Play found per company?

Last updated: June 17, 2026

When a Play runs, the prospecting node's logs tell you how many prospects it identified per company based on your configured personas.

Where to check

  1. Open the Play in the Plays tab.

  2. Go to the Logs section.

  3. Find the company you want to check — scroll through or search by name.

  4. Click into the company and scroll to the prospects-found log entry. If the node found no matches, you'll see "None found."

There is no automated notification when no prospects are found — monitoring the logs is currently the most direct way to spot it.

For aggregate monitoring across Plays

Use the prospecting analytics view: Analytics → Leading → Prospecting. Sort by Play to see how each one is performing on average across all the companies it's run on.

If you're seeing "None found" or low prospect counts

There's no single cause — work through these in order.

Persona / title configuration

Persona matching uses case-insensitive whole-word matching:

  • All persona words must appear as whole words in the candidate's title, in any order.

  • Punctuation and extra words around the match don't break it ("Vice President of Marketing" matches a persona of "Vice President Marketing").

  • A persona of "CTO" will match titles containing "CTO" — but won't match "Chief Technology Officer" unless you add that as a separate variation.

To improve coverage:

  • Add both abbreviated and expanded versions ("VP Data" and "Vice President of Data").

  • Add common synonyms ("Head of Engineering" and "VP Engineering").

  • For specialized roles, expect to add more variations than you would for generic ones.

Exclusion gotcha: exclusions take precedence over inclusions. A broad exclusion like "director" will exclude all titles containing that word, including "Executive Director" and "Director of Marketing", even when those are explicitly in the include list. Use specific exclusion terms ("Director of Operations", "Facilities Director") instead.

Prospect node settings

  • Max prospects per company — if set too low, the node fills its quota from your first persona before trying others.

  • Persona ordering — when multiple personas are in one node, they're processed in order. The first persona fills the quota first.

  • Include existing People — disabled means the node only finds new contacts not already in Unify or your CRM. Enable it if you want existing contacts to count.

Exclusions and routing

  • Org or sequence-ruleset exclusions can filter out matches the prospect node found.

  • A "No routing target" error means the persona has no matching route in the sequence enrollment node — add a route or an "Everyone else" catch-all.

  • Per-company enrollment caps can hold prospects in queue rather than enroll them.

Company data

  • Confirm the company domain is correct on the company record. Domain is the primary identifier.

  • Some companies have limited data provider coverage, especially smaller or non-standard businesses.

  • Unify uses multiple data providers but does not pull from LinkedIn directly — some prospects may not be in our database for that reason.

Alternative approaches

  • If you know a specific person should be prospected, use the Chrome extension to add them directly to a sequence without running the Play.

  • If your Play has completed all its runs, editing personas or audience filters does not automatically re-prospect previous companies. Duplicate the Play and run the new version to apply changes retroactively.

Switching to Waterfall Prospecting

If volume is consistently lower than you'd expect even after broadening personas, try Waterfall Prospecting:

  • Standard prospecting uses data already in your CRM.

  • Waterfall Prospecting queries external data providers for the freshest data, regardless of CRM coverage.

Waterfall mode often materially improves volume for specialized roles or under-covered segments.