Skip to main content

Currently when building a Program, we are able to select if a Participant with the same email address can enter once in e.g. 90 days. In some cases this is not sufficient as a criteria. Example: An external consultant / partner works for multiple customers & he should be notified when these customers are close to their seat limit.

If I select “Participant with same email address can enter once in 90 days”, the consultant will be informed for one customer, but if the next customer reaches their limit within the next 90 days, he won’t be notified. If I don’t tick this box, he’ll be notified for the same customer every single day.

As a workaround, I currently have to add the AO Participants in the query while building the Program. Ideally, this could be avoided by having a checkbox “Participant with same unique criteria can enter once in X days”.

Hi @abeck0625. Great use case here.

You do pick up some configuration options inside your Program in the Uniqueness Criteria. In the picklist title Filter participants by, you can configure which combination of criteria are unique. Anytime a record representing a Participant arrives which a unique set of criteria, the Program would have that Participant re-enter the program.

To be more specific, you could declare uniqueness criteria as Recipient Email Address and Company ID. In this case, the Program could add a new Participant having the same email address as a previous Participant, so long as the Company ID is also unique from any previous Participant fetches. Thus, your consultant can receive one email for each Company ID without using the Participant with same unique criteria can enter once in X days configuration option.

@matthew_lind Absolutely, the solution works well for one-time outreaches or Programs where the email trigger can be tied to a date (e.g. end of onboarding).

For Programs where this is not the case (i.e. you sync Participants every day), the consultant would get an email every day for each Company ID in your example, right? Unless you do a workaround & add the AO Participants in the query.

This setting here prevents people from re-entering based on the value you enter.

 

 

Mis-read,

 

To Matthew’s point, you are selecting additional fields in your uniqueness criteria.

 

 

So if you only have recipient email it ignores company id. So if the same email is across 5 different accounts it won’t re-enter for other accounts. But once you add that it now looks to see if it was sent to a person for a particular company. 

@Wayne Correct, but I still can’t build a Program that sends the email every 6 months to the same unique participant. As you suggested, I included the Company Id in the uniqueness criteria, so the participant will be a unique participant for each customer. But then if I run the Program every day, it’ll sync the participant every day and will keep sending the email daily (unless I can tie the trigger to a date which I cannot in my use case). To avoid this, I’d have to select “Participant with the same email address can enter once in … days”. And then my uniqueness criteria doesn’t help me, because the Program will only look at the email, keep the participant with one Company id, but won’t consider the rest.

Terms & ConditionsCookie settingsAccessibility statement