23 Replies Latest reply on Oct 27, 2015 11:06 AM by Emily Dick

    Unsupported Date Token in Campaign?

      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

      0EM50000000RJeq
        • Re: Unsupported Date Token in Campaign?
          Hey Jonas,

          When you entered the token in the wait step, did you type the whole thing in? Did you copy and paste? How did you enter it?

          Also, what type of field is {{lead.bePART Sales Certificate Acquired_}}? Meaning is it a date field, or boolean, or something else?
          • Re: Unsupported Date Token in Campaign?
            Are you creating a batch campaign?
            I believe that as of the December release date tokens can only be used in trigger campaigns.
            1 of 1 people found this helpful
            • Re: Unsupported Date Token in Campaign?
              Hi Jeff, Cathal,

              The field is a date field. When I entered the token in the wait step I typed it, as I considered that pasting was the reason it didn't work.

              Do any of you have an idea for a work around, to tackle this issue? How can I have an e-mail sent 18 months after they passed the test for certificaition, informing our contacts that they have 6 months to renew it. Using the date field mentioned above?

              Thanks
              • Re: Unsupported Date Token in Campaign?
                Hey Jonas, 

                You are on the right track. To Cathal's point, is this a batch or trigger campaign? Also, I have noticed that Mkto can get fickle and if you don't select the token from the drop down, the system will think that the token does not exist, thus creating an error.

                One suggestion would be to create an expiration date field and use that minus 6 months for your wait step and see if the system is more agreeable to that. 

                Another suggestion would be to change 732 days to 18 months. Maybe the number of days is causing an issue.
                • Re: Unsupported Date Token in Campaign?
                  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:

                  0EM50000000RJs3


                  • Re: Unsupported Date Token in Campaign?
                    Hey Jonas,

                    Since it needs to be a trigger, could you not use a Data Value Changes trigger (at least for your new leads moving forward)?

                    To this point, you could potentially cause a Data Value Change on all of the existing leads, which would satisfy the Date token use.

                    Hope this helps.

                    Greg
                    • Re: Unsupported Date Token in Campaign?
                      Hey Jonas,

                      Yes, I would just take the date they passed and add two years to a newly created field. Is this field updated by the system or manually?

                      I really don't understand why the way you have it set up is not working. How do you have your smart list set up? I think you may want to contact support so they can take a look in your system.

                      I'm sorry I couldn't help you resolve this!
                      • Re: Unsupported Date Token in Campaign?
                        Hi Jeff, Greg, Cathal,

                        To answer your question Jeff, it is a field that is updated manually.

                        I've did some tests using a data change trigger, adding a certain amount of days (tested it with 732 days) and it seems to work, which is very positive. Only thing I need to do is an export of allt he data and re-upload it so that the campaign is triggered.

                        Don't really know why batch campaigns are prohibited from the 'date token'?

                        Thank you all for helping me think about this one.

                        Warm regards and already wishing you a joyful holiday season.

                        Jonas
                        • Re: Unsupported Date Token in Campaign?
                          Jeff Coveney
                          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?

                          0EM50000000RTdj

                           0EM50000000RTdZ
                          • Re: Unsupported Date Token in Campaign?
                            Hey Jeff,

                            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.

                            Is that your only wait step in your flow?
                            • Re: Unsupported Date Token in Campaign?
                                   Hi Jeff,
                                    
                                   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.

                                    
                              • Re: Unsupported Date Token in Campaign?
                                Jeff Coveney
                                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. 
                                • Re: Unsupported Date Token in Campaign?
                                  Jeff Coveney
                                  I wanted to confirm that I tested above and it works.  Build your campaigns with a Request Campaign trigger, NOT as a batch campaign. Remember.....

                                  Date tokens are currently not supported in batch Campaigns. 
                                  • Re: Unsupported Date Token in Campaign?
                                    Jeff Coveney
                                    As a follow, the advnaced wait token didn't work in our use case. We really need an IN THE FUTURE time constraint. Just wrote up the details and the workaround here.

                                    https://community.marketo.com/MarketoIdeaDetail?id=08750000000JeCwAAK
                                    • Re: Unsupported Date Token in Campaign?
                                      Conor Fitzpatrick
                                      Hi Jeff,

                                      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.

                                      Any help is greatly appreciated.

                                      Thanks,

                                      Conor
                                      • Re: Unsupported Date Token in Campaign?
                                        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:

                                         0EM50000000RbFL

                                        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:

                                        0EM50000000RbFQ

                                        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
                                        • Re: Unsupported Date Token in Campaign?
                                          Conor Fitzpatrick
                                          Awesome, thanks for the detailed response Jonas - I will give this a shot.
                                          • Re: Unsupported Date Token in Campaign?
                                            Hi all,

                                            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.

                                            Best,
                                            -Jamie

                                                  
                                            • Re: Unsupported Date Token in Campaign?
                                              Conor Fitzpatrick
                                              Jamie,

                                              Give this a shot:

                                              •           Click into the token with the red line
                                              •           Delete a couple characters at the end of the token
                                              •           Wait for the drop down options to show up and select the appropriate token
                                              •           Make sure the campaign auto-saves in the top right hand corner

                                              I have run into this issue a couple times and re-selecting from the drop down fixed the issue.
                                              • Re: Unsupported Date Token in Campaign?
                                                Hi Jamie,

                                                It's like Conor explains in the post above - that should work.

                                                Cheers,

                                                Jonas
                                                • Re: Unsupported Date Token in Campaign?
                                                  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
                                                  • Re: Unsupported Date Token in Campaign?
                                                    Conor Fitzpatrick
                                                    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.

                                                    0EM50000000RmMO
                                                    • Re: Unsupported Date Token in Campaign?
                                                      Emily Dick

                                                      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?