Skip to main content

How to Control Duplicate Prospects and Company Limits in a Campaign (Prospect Limitations)

Use the Prospect Limitations settings to skip prospects already in other campaigns, allow re-enrollment, exclude specific campaigns from duplicate checks, and cap how many prospects are added per company.

Written by Katie Supporté

Summary: The Prospect Limitations section in your campaign's Settings controls whether prospects who already exist in other campaigns are skipped, lets you make exceptions for specific campaigns, and caps how many prospects can be added from the same company.

Who this is for: Anyone running more than one campaign, or targeting audiences where several prospects may work at the same company.


Where to find it

  1. Open your campaign and go to the Settings step of the campaign builder.

  2. Scroll to the Prospect Limitations section ("Set limits on prospect targeting and company contacts") and click to expand it.

Skip prospects already in campaigns

The Skip prospects already in campaigns toggle is on by default. When enabled, Alta won't add prospects that are already targeted in your other campaigns — the check runs against all campaigns, so the same person is never worked by two campaigns at once.

Two refinements are available:

  • Exclude archived campaigns — when enabled, only active and paused campaigns are checked for duplicates. Archived campaigns are ignored, so a prospect from a long-retired campaign can be targeted again.

  • Manage exceptions — click this link to open the Exclude specific campaigns picker. Prospects in the campaigns you check here can still be added to this campaign; everyone else stays blocked.

How to add campaign exceptions

  1. Under "Checked against all campaigns", click Manage exceptions.

  2. Use the Search campaigns... box to find campaigns. Each row shows the campaign's status (Active, Paused, or Completed).

  3. Check the campaigns whose prospects should be allowed into this campaign. The counter at the bottom shows how many are excluded.

  4. Click Apply to save, or Clear to remove all exceptions.

Re-enroll Existing Prospects

Turn on Re-enroll Existing Prospects to allow the same prospect to be added to this campaign even if they already exist in other campaigns — useful for re-engagement plays or win-back sequences.

This setting is the opposite of deduplication, so the two can't be on together: enabling re-enrollment automatically turns off Skip prospects already in campaigns and clears any per-company limit, and turning either of those back on switches re-enrollment off.

Limit prospects per company

Turn on Limit prospects per company to control how many prospects from the same company can be added to this campaign. This prevents over-contacting a single organization.

  1. Flip the Limit prospects per company switch.

  2. Set the number in the Up to ___ prospects per company field. You can enter any value from 1 to 40 — values outside that range are snapped back automatically.

Tips and common pitfalls

  • List campaigns start with deduplication off. When you build a campaign from a List source, prospects are usually being moved from other campaigns on purpose, so Skip prospects already in campaigns defaults to off there. Turn it back on if that's not what you want.

  • ABM campaigns set the company limit in the audience step instead. For ABM sources you won't see the company-limit switch in Settings — use the Prospect limitation slider in the audience step (defaults to 20, up to 40 prospects per company).

  • Exceptions are allow-lists, not block-lists. Checking a campaign in "Exclude specific campaigns" means its prospects can be added here — it does not block them.

  • Completed campaigns still count as duplicates unless you add them as exceptions. Only archived campaigns can be skipped wholesale via "Exclude archived campaigns".

Related

  • How to Send Prospects to Another Campaign in Alta (Move or Re-Target Prospects)

  • How to Add Prospects to a Campaign

  • CRM Integration: Deduplication, Push, and Permissions

Did this answer your question?