Improve UX when Date Token option in Advanced Wait step is used in a smart campaign

Improve UX when Date Token option in Advanced Wait step is used in a smart campaign

Smart campaigns with an advanced wait step that use a Date Token are only valid if the smart campaigns are triggered; however, the option to include a Date Token is provided when there is no trigger in the smart list.  In this case, when you try to run the smart campaign, an error message is displayed "Smart Campaigns may not be run with an unsupported token in Wait Step:{{token name}}".

This is a rather obscure restriction and one that many users are unlikely to remember.  I suggest that the Date Token option not be displayed if there is not a trigger in the smart campaign.  In addition, if a triggered smart campaign has an advanced wait step that uses a Date Token and the trigger is removed, there should be a warning and if the user proceeds, the wait step has the Date Token option removed and if the smart campaign is run, and error message would be displayed if the wait step is not redefined.

The ultimate solution would be to allow Date Tokens in wait steps regardless of whether the smart campaign is triggered or batch.

1 Comment
Community Manager
Status changed to: Open Ideas