Unsupported Date Token in Campaign? | Community
Skip to main content
December 17, 2013
Question

Unsupported Date Token in Campaign?

  • December 17, 2013
  • 23 replies
  • 3192 views
Could someone help me out here as I am in the dark about what I am doing wrong in this campaign which should be triggered by a date token (see below).

Goal of the campaign is that a lead receives an e-mail to inform that his/her Exam Certificate for one of our programs is expiring in 6 months time and urging the person to renew it.

There is a specific date field containing the date when the lead passed the exam, but when I use the date field Ias a date token in the waiting step I receive the following error:

"Smart Campaigns may not be run with an unsupported token in Wait Step:{{lead.bePART Sales Certificate Acquired_}}"
 
Could someone help me out here? Thanks


This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

23 replies

April 23, 2014
Thanks All,

I tried removing the last few letters, but then it doesn't work at all.  I am confident I have the field name right, and have tried both the API name and the standard name, just in case.

I also tried with more common fields, like SFDC Created Date, but it doesn't register either.

Best,
-Jamie
Conor_Fitzpatri
Level 5
April 23, 2014
After you remove the letters, a drop down menu should appear as in the image below. You need to select the token from the drop down menu. For some reason, the system does not always properly save the token unless you select it from the drop down - removing letters is simply a way to get that menu to appear.

October 27, 2015

I'm so annoyed that I encountered this error! It's too bad you can only use these awesome wait step tokens in Trigger campaigns. I'm trying to use more batch campaigns as there's less chance for error (especially against renewal dates which do not change often) and they don't slow down the instance the way trigger flows do.

Any updates from Marketo on this?