For your example, it looks like you are trying to reference a token that is not a date token. I would check the Release Enablement Date field in the Field Management section of the Admin tab to double check.
If it is a date field. You received the same error as I did in the beginning, especially since I tried to paste the field token. That doesn't work well. When I entered the token in the wait step I typed it and selected the token from the drop down. Otherwise the system will think that the token does not exist and creates an error.
This should work and like Jeff above mentions, other wait steps could influence it.
Jeff S and Jonas. I did check the field type and it is a date field. I also made sure to select the token like Jonas suggested (rather than paste).
This is the answer I just got back from support. It's exactly how I have it setup for the live campaign but I was using a batch campaign to test. Will report back when we get this working.
Date tokens are currently not supported in batch Campaigns. As a work around, I would suggest to change the 00-Send Nurture Email campaign to a trigger campaign with a Request Campaign trigger. You can then create another Smart Campaign to send all the leads you want into that campaign.
Thank you for posting this idea - I am trying to build a similar campaign and am frustrated at the lack of an IN THE FUTURE constraint.
Can you explain your workaround in a little more detail? Specifically, I am trying to build a campaign that sends an email once a quarter based on their start date. We added 4 fields their start date + 90, start date + 180, etc. Where I'm getting hung up is how I can build a list of all the folks that start + 90 = today, start +180 = today, etc.
I think I might help you out here - did something similar. In our case I wanted to send out an e-mail to a series of contacts when one of their certificates expired (valid for two years). In this case we inform the contact 6, 3 and 1 month in advance to renew it + also when it expired.
The way how I set it up was the following:
- date token contained the date when the contact acquired the certificate = so the date was always in the past - each time the date token changed it triggered the flow again= so it's a campaign which does not have an end date
In the flow tab of your campaign you insert a 'wait step' with 'date token' that looks like this:
Only thing you shouldn't forget is to kick start the campaign, which means that you need to update/change the value in the date field (could be done by exporting the list of contacts you want to include in the campaign and upload it again without changing anything). From then on the campaign starts working instantly.
It's been active for over 4 months here and works perfect.
Was reading through your comments because I am running into a similar issue with the date token in Wait steps. I select the token from the drop down and it looks correct. When I click back in to edit it, the token is highlighted in red as if it doesn't recognize the date.
When I review the results in the campaign, the Wait Step says "'Do Nothing' was set for this choice."
It's not recognizing the token even though I can select it from the dropdown. Seems buggy. Were you able to resolve your issue Jonas?
All our date tokens are contained within trigger campaigns.