TL;DR
If you're a multi-property client sharing one Salesforce instance, the ‘Exclude Contacts with Active Opportunities’ setting now checks only opportunities for the property you're pushing from. A contact with an open opportunity for Property B won't be excluded from a Property A push anymore. This requires managed package version 1.456 or later and a one-time configuration by StellarAlgo.
What This Means
The Salesforce Sales Cloud managed app has an ‘Exclude Contacts with Active Opportunities’ setting. When enabled, contacts with open (non-closed) opportunities are excluded from segment pushes to avoid duplicate outreach.
Previously, this exclusion checked all opportunities across all properties. For multi-property clients sharing a single Salesforce instance, this meant a contact with an open opportunity for one property would be excluded from a segment push for a completely different property; even though the two are separate sales processes.
Starting in version 1.456, the exclusion logic is property aware. It only considers opportunities belonging to the same property as the segment being pushed.
Who This Affects
This feature is relevant if you meet all three criteria:
You are a multi-property client with two or more properties
You share a single Salesforce instance across properties
You use the ‘Exclude Contacts with Active Opportunities’ setting
Single-property Salesforce clients are unaffected. The feature is behind a feature flag and only activated after configuration.
How It Works
The managed app uses a configurable field mapping to determine which property an opportunity belongs to. When a segment push runs with the exclusion toggle enabled, the app:
Parses the property (tenant) name from the StellarAlgo segment name
Looks up the corresponding value in the configured Salesforce field
Excludes only contacts whose open opportunities match that property value
The Salesforce field used for property identification varies by client. Common options include:
Campaign > Team_c -Team_c
Opportunity > Line_of_Business_c - Line_of_Business_c
Your StellarAlgo team will work with you to identify the right field and configure the mapping during setup.
Before and After
Here's how the behavior changes for a multi-property client:
Same-property: Contact has an open Property A opportunity → Property A push with exclusion on → Excluded. Same behavior as before.
Cross-property: Contact has an open Property B opportunity → Property A push with exclusion on → No longer excluded. Previously, this contact would have been incorrectly excluded.
Single-property clients: No change. Behavior is identical to previous versions.
Relationship to Stage Matching
This feature is separate from the stage matching improvement delivered in version 1.454. That change updated how the app recognizes custom closed stages (e.g., ‘Closed Won - Season Renewal’ is now correctly treated as closed instead of active).
Setup instructions
The settings that control property-aware exclusions are:
Custom Settings -> StellarAlgo Job Settings -> Property Filter Opportunity Field
This is the field from Opportunity that establishes the property i.e. Line_of_Business_c
Custom Metadata Types -> Property Exclusion Mapping
Segment Tenant Prefix: the prefix for segments from CDP
Opportunity Field Values: value of the "Property Filter Opportunity Field" that corresponds to the specific property
Create a mapping for each property
Custom Settings -> StellarAlgo Job Settings -> Enable Property Based Opportunity Filter
Checkbox to enable/disable the feature
The property-aware exclusions feature will only be enabled is the 'Property Filter Opportunity Field' is set, at least one 'Property Exclusion Mapping' exists, and 'Enable Property Based Opportunity Filter' is checked.
Validation Steps
After your StellarAlgo team deploys and configures this feature, validate with these steps:
Confirm cross-property contacts are no longer excluded. Identify a contact whose account has an open opportunity for a different property. Push a segment from your property with ‘Exclude Contacts with Active Opportunities’ checked. The contact should appear in the generated opportunities - previously they would have been excluded.
Confirm same-property exclusion still works. Identify a contact with an open opportunity for the same property. Push a segment from that property with the exclusion toggle on. The contact should still be excluded.
Compare counts. Push a test segment with and without the exclusion toggle. The gap between counts should be smaller than before; only contacts with open opportunities for the same property should be excluded.
Setup Requirements
To enable this feature for your organization, StellarAlgo needs:
The Salesforce field that distinguishes properties on your Opportunities
A mapping of your StellarAlgo tenant names to the corresponding field values
Deployment of managed package version 1.456 or later to your Salesforce instance
Contact your StellarAlgo Customer Success representative to get started.
Still Have Questions?
If something doesn't look right after this feature is enabled, or if you're unsure whether your Salesforce setup qualifies, reach out to StellarAlgo support with the specific behavior you're seeing.