Accounts in Segments

If you're starting with a fresh campaign, you can set up a dynamic shell segment to target against, this will allow you to better manage accounts for targeting and establish priority targeting models. It's helpful when working with static list uploads and campaigns that you may want to manage for a longer period of time.

List upload segments are fairly static and difficult to transform, so a shell segment is a way to quickly uplevel the features you can utilize without much work.

To set this up the way you're asking you'd build:

Segment A - Your List Upload Segment (Static)

Segment B - "Shell" Segment
- Add "Accounts in Segment" filter and select "Equal To" Segment A
- Add "Accounts in Segment" filter and select "Not Equal To" Segment C
— This is your exclusion rule to split out certain accounts into another program

Segment C - New Campaign Segment
- Define this however you need to in order to ID the accounts for your other program (e.g. accounts in Segment A with Open Opportunity flag in SFDC)

When setting up your first campaign - build it with targeting for Segment B and your Pipeline Acceleration campaign targeted to Segment C. This will establish the dynamic exclusion cascade for your two programs with Segment C receiving priority targeting and sets the ability for both to adjust in real time as accounts move to Segment C from A.

Another benefit of this model is that you can layer other adjustments on to Segment B easily, join other audiences or connect it to a new static list if you upload a new segment to replace Segment A in the future - all without having to disassemble all of your other program elements.

Note: If you already have a campaign running against Segment A's static list, you'll have to stop that program and build out a new one above to insert the dynamic shell, segment's can't be swapped out mid-flight.