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
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_}}"
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.
Hi Conor,
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.
See below:
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.
Hope this helps you out.
Cheers,
Jonas
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.
See below:
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.
Hope this helps you out.
Cheers,
Jonas
Was there even a resolution to this?
We want to run a nurture campaign to existing customers starting 30 days from an upgrade date. The idea is to a regularly add customers to the campaign and let the wait token do the heavy lifting.
If not below, any workarounds?
We want to run a nurture campaign to existing customers starting 30 days from an upgrade date. The idea is to a regularly add customers to the campaign and let the wait token do the heavy lifting.
If not below, any workarounds?
Hi Jeff,
Thanks for your feedback.
To answer your questions, at the moment I try to make it a batch campaign which runs daily at 9 AM in the morning. Reason being that I don't really see how to use a trigger in this case, as I want to use a date field (lead.bePART Sales Certificate Acquired_) which contains the exact date when a person passed the exam. Also, I am using data going back to 2011, when were not yet using Marketo + each value is different (people did not pass the exam on the same date).
Concerning your suggestion, what would be the best way to go at it, as it would mean creating another field in the database just for this purpose?
Also it seems that you can only add a value in number of days, see below:
Thanks for your feedback.
To answer your questions, at the moment I try to make it a batch campaign which runs daily at 9 AM in the morning. Reason being that I don't really see how to use a trigger in this case, as I want to use a date field (lead.bePART Sales Certificate Acquired_) which contains the exact date when a person passed the exam. Also, I am using data going back to 2011, when were not yet using Marketo + each value is different (people did not pass the exam on the same date).
Concerning your suggestion, what would be the best way to go at it, as it would mean creating another field in the database just for this purpose?
Also it seems that you can only add a value in number of days, see below:
.png)
- Copyright © 2025 Adobe. All rights reserved.
- Privacy
- Community Guidelines
- Terms of use
- Do not sell my personal information
Adchoices