Ability to "Null Check" In Email Varients

  • 6
  • Idea
  • Updated 5 days ago
I have a customer that would like to "null check" a text field and use that to dictate a variant be used. There are a lot of filter options but != NULL isn't one. Engineering suggested enhancement request. 

Photo of Steve Davis

Steve Davis, Employee

  • 6,610 Points 5k badge 2x thumb

Posted 2 months ago

  • 6
Photo of Dan Ahrens

Dan Ahrens, Gainster (employee)

  • 19,738 Points 10k badge 2x thumb
Agreed that a NULL option would be useful.

In the meantime, could you set your logic criteria such that the Default variant catches these individuals? 
Photo of Diane Morneau

Diane Morneau

  • 646 Points 500 badge 2x thumb
Our use case is to produce Japanese letters and eventually in other languages too. In addition to the account and contact names in "English" representation, we have fields that allow us to store these names in their native language. Let's call them Foreign account name and foreign contact name.

For Japanese customers, we have two letter variants to cover the cases when the foreign names are provided versus not provided. Our inability to test for these fields being nul within an Advanced Outreach forces us to split these into two Power lists to send out the right letter. The day that the foreign fields information will be filled, they will be picked up again and receive the other version of the letter, which is not desired either.

The lack of being able to set the logic in the AO is doubling our work by forcing us to segment unduly our mailings... and we are only dealing with one language at this point.
Photo of Abhishek Sivaraman

Abhishek Sivaraman, Senior Product Manager

  • 6,502 Points 5k badge 2x thumb
Hi Diane and Steve,

Agree with you. We will fix this soon (1 to 2 months).

Thanks
Abhishek S