Megan_Koelemay

It looks like the issue wasn't that my "Member of Engagement Program" filter wasn't working. Rather, as my reply above mentions, the problem was form fills, where multiple product interests are selected. This was simultaneously firing the triggers in my engagement programs. Segmentation took care...

I'm curious what an "Engagement Router program" is! I couldn't find any documentation or examples of this in the forums. I tried segmentation for one of my triggers in my engagement programs (we have multiple triggers to enter someone into them), and after testing, it worked great! The issue, as...

Update: It turns out my variables were causing the issue. These are defined in the of my email using tags. Once I removed them and used inline styles instead, the formatting looked fine. For example: background-color:${contentblockbackgroundcolor}was replaced withbackground-color:#EFEFEF There'...

Now I'm hoping to configure my token as a whole section of HTML content so it wouldn't leave an extra space if the condition doesn't match (a la this post - though it notes unintentional line breaks can happen, which would defeat the purpose). But I tried it and ran some Email on Acid tests, and no...

Worked like a charm, just had to change <= to >=. Thanks so much, @SanfordWhiteman!

After some testing, I can get things to "work" if I change the script to == 2007. Examples: For someone whose field value is 2007, it shows up as Member since: 2007. For someone whose field value is 2004, it shows up blank.For someone whose field value is 2015, it shows up blank. #if ($lead.Member...

Thank you! This makes sense, but I tried it and it shows up blank no matter what the year value is. My token within the email is {{my.membersince}}, and I sent test emails using leads with values like 2009 and 2015.