Collection-and-campaign street taco

What is a simple way to generate a campaign target list based on collection criteria? My collection shows information about "feature requests" submitted by my customers. I want to send a celebration notification to my customer champion the first time one of the company's requests makes it to the roadmap.

Ingredients:

• 1 custom collection with data already populated
• 1 account segment with 1 collection filter
• 1 ongoing campaign

Preparation:

1. Create a new account segment.
   
   
2. Add ONE filter for the collection data point you want to target. In our example, we added a collection filter for the status we want (Planned). 
   
   Note: If you add more than one collection filter, you may get unintended results because the conditions are looking at individual rows within a collection rather than between account objects. For example, any account that meets the first collection criteria OR the second would qualify in the result set of accounts—even if you used an AND operator between the collection conditions.
   
3. Save the segment within the same SuccessBLOC from which you plan to send your campaign.
   
   
4. Within the same BLOC, create a new campaign. Keep in mind that custom collection data cannot be leveraged as dynamic data in a campaign, so the message may be simple with a CTA to go elsewhere for more details.
   
5. Within the campaign targets, add a new filter for "Is in Segment (Account)" and choose the new segment you created.
   
   
6. In this example, all users under the matching accounts will become targets. We suggest adding additional user filters to narrow the list based on your available user attributes, such as only users who are Key Contacts on the account and who have a specific Account Role (e.g., Champion). 
   
   Heads up! In this example, whenever a *new* user on the account gets denoted as a "Champion" and a "Key Contact" in the future, that person will receive this email—even if the account itself has been in the qualifying segment for awhile. Keep that in mind when you craft your message, as it may not always get sent relative to when the account moved into the segment. (For more campaign trigger options, consider setting a custom date attribute when the account enters the segment.)
   
   
7. Set the schedule for "Ongoing," and then save and activate the campaign.

Cook's note:

Even if the custom collection contains user emails (e.g., the person who submitted the feature request), this approach cannot leverage that data point. Outside of the "Is in Segment" option for account objects, using custom collection data is not supported in user segments, campaigns, teams, or health designer (see wishlist item).