This article covers:
• What the ‘Exclude Contacts With Active Opps’ setting does
• How the managed app determines whether an opportunity is closed
• How exclusion works for multi-property organizations sharing Salesforce instance
• Configuration requirements for multi-property clients
• Verification steps and frequently asked questions
Overview
When pushing a segment from StellarAlgo to Salesforce Sales Cloud, the managed app can optionally exclude contacts who already have active (non-closed) opportunities. This prevents sales reps from receiving duplicate leads for fans they are already working.
The setting is called ‘Exclude Contacts With Active Opps’ and appears as a checkbox during segment push configuration. When checked, the managed app evaluates each contact's opportunities before including them in the push.
The exclusion logic handles two scenarios that are important to understand: how the managed app determines whether an opportunity is closed (relevant if your organization uses custom stage names), and how the managed app scopes the check for multi-property organizations sharing a single Salesforce instance.
How It Works
When ‘Exclude Contacts With Active Opps’ is checked, the managed app:
Retrieves the list of contacts in the segment being pushed.
For each contact, checks whether they have any active opportunities in Salesforce.
Excludes contacts who have at least one active opportunity. Contacts with only closed opportunities (or no opportunities at all) are included in the push.
ℹ️ If the checkbox is not checked, all contacts in the segment are pushed to Salesforce regardless of their opportunity status. The exclusion logic only applies when the setting is enabled.
Closed Stage Recognition
The managed app determines whether an opportunity is closed by checking the opportunity's Stage Name. Any stage that begins with ‘Closed Won’ or ‘Closed Lost’ is treated as a closed stage.
This means custom stage names that include a suffix after the standard prefix are fully supported. For example, all the following are recognized as closed:
Stage Name | Recognized As |
Closed Won | Closed |
Closed Lost | Closed |
Closed Won - Season Renewal | Closed |
Closed Lost - No Response | Closed |
Closed Lost - Invalid Opportunity | Closed |
Negotiation | Active (contact may be excluded) |
Proposal Sent | Active (contact may be excluded) |
If your organization uses custom stage names, no additional configuration is needed if closed stages follow the ‘Closed Won’ or ‘Closed Lost’ prefix convention.
⚠️ Important: If your organization uses stage names that do not begin with ‘Closed Won’ or ‘Closed Lost’ for terminal stages (for example, using entirely different naming conventions), contact your StellarAlgo CSM. Alternative approaches such as matching on the Salesforce Stage Type field may be available.
Multi-Property Organizations
Some organizations operate multiple properties (e.g., two teams or lines of business) within a single shared Salesforce instance. For these organizations, the exclusion logic supports property-aware scoping so that opportunities for one property do not affect segment pushes for another.
Why This Matters
Without property-aware scoping, the exclusion check evaluates all active opportunities on a contact's account, regardless of which property they belong to. A contact with an open opportunity for Property B would be excluded from a Property A segment push, even though the two sales processes are unrelated.
In practice, this can result in significant contact loss. For example, if an organization pushes a segment of 600 contacts for Property A and 400 of those contacts have open opportunities for Property B, only 200 would appear in Salesforce - even though none of those 400 have active Property A opportunities.
How Property-Aware Exclusion Works
When property-aware exclusion is enabled, the managed app adds a property-matching step to the opportunity check:
Identifies which property the segment belongs to by reading the property identifier from the StellarAlgo segment name.
For each contact, checks for active opportunities - but only evaluates opportunities that belong to the same property as the segment being pushed.
Excludes the contact only if they have an active opportunity for the matching property. Opportunities for other properties are ignored.
ℹ️ Single-property clients: If your organization has only one property in Salesforce, the exclusion behavior is the same whether property-aware scoping is enabled or not. No action or configuration is required.
Configuration
Standard Setup (All Clients)
The ‘Exclude Contacts With Active Opps’ checkbox is available during segment push configuration. No additional setup is required for single-property clients. The closed stage recognition logic (pattern matching on ‘Closed Won’ and ‘Closed Lost’ prefixes) is applied automatically.
Multi-Property Setup
Property-aware exclusion requires two things to be configured by your StellarAlgo CSM
Feature flag: Your CSM will enable the property-aware exclusion feature for your Salesforce instance. This is a setting within the StellarAlgo managed package.
Property field mapping: The managed app needs to know which Salesforce field identifies the property on an Opportunity. This varies by organization - the field may live directly on the Opportunity object or on a related object such as the Campaign. Your CSM will configure a mapping that connects each StellarAlgo tenant name to the corresponding value in the Salesforce property field.
What Your Salesforce Admin Needs to Provide
API name of Salesforce field that indicates which property an opportunity belongs to. This could be a field directly on Opportunity (e.g., Line_of_Business_c) or on a related object (e.g., Campaign.Team_c). Your CSM can help identify the right field.
The values stored in that field for each property (e.g., ‘Team A’ and ‘Team B’, or the specific names your organization uses).
Confirmation that this field is consistently populated on Opportunity records, including both existing and newly created Opportunities.
⚠️ Important: The property field must be populated on your Opportunity records for property-aware exclusion to work correctly. Opportunities without a property value cannot be matched to a specific property. Work with your Salesforce admin to ensure the field is populated before enabling the feature.