I need to trigger a welcome email for all EXISTING leads for whom "platform user" value is changed to TRUE.
However, I also need to trigger this email for all NEW leads for whom I import with "platform user" value as TRUE. The data value changed to will not apply to these folks as their platform user value will be set to TRUE from the get-go and not changed to TRUE. Also, I can't send this email to all new leads as they are all not platform users.
I'm picturing this:
Data Value Changes
Attribute: Platform User
New value: true
OR
Lead is Created
AND
Platform user = true
So this would be 1 or (2 and 3)
However, the advanced filters option remains inactive (grayed out). How can I accomplish my goal?
Solved! Go to Solution.
Advanced filters only apply to filters (the green ones). They don't apply to triggers (the orange ones). Triggers are always OR by default.
In the scenario you describe, what you're actually saying with two triggers and the one filter is "Data Value Changes (Platform User is True) and Platform User is True" or "Lead is Created and Platform User is True".
You can leave this on ALL filters. Although the filter won't actually have any impact on the Data Value Changes trigger, since that's already included in the constraint, you need it for the second one, and it doesn't cause any real harm by being there.
Advanced filters only apply to filters (the green ones). They don't apply to triggers (the orange ones). Triggers are always OR by default.
In the scenario you describe, what you're actually saying with two triggers and the one filter is "Data Value Changes (Platform User is True) and Platform User is True" or "Lead is Created and Platform User is True".
You can leave this on ALL filters. Although the filter won't actually have any impact on the Data Value Changes trigger, since that's already included in the constraint, you need it for the second one, and it doesn't cause any real harm by being there.
Kristen, thanks so much for the quick reply! I've re-read it about 7 times and I'm not sure I follow at all...although I'm pretty sure I should.
My most important takeaway is that the triggers are always OR by default. I think that ought to be enough info for me to be able to put together a system that works for me here.
So after re-reading your reply a few more times and trying to assimiliate what you said I've come to the conclusion that the way I have my trigger/filter system setup is actually already correct:
<1>Trigger
Data Value Changes
Attribute: Platform User
New value: true
<2>Trigger
Lead is created
<3>Filter
Platform user = true
So that's essentially 1 OR (2 AND 3)
Because triggers are by default OR and I've selected Use ALL filters
I think what tripped me up is I was expecting to find the ability to add the platform user = true as a constraint on my Lead is created trigger. But it appears I can accomplish that with the filter (green) and using ALL filters creating the AND relationship.
Rich Lorenzo yep you've got it figured out.
Triggers are always OR (any trigger will fire the campaign).
Filters further modify or constrain triggers subject to the filter logic.
In this case there is no constraint for platform user = true that is built into the lead trigger but you can add a separate filter (green) that will accomplish the same thing.
The filter applies to all triggers but it doesn't matter in this case as Kristen Carmean mentioned.