Skip to main content
A
Anonymous
February 10, 2014
Question

Date field in smart campaigns

  • February 10, 2014
  • 8 replies
  • 1688 views
I'm trying to put together a smart campaign that automatically fills in the date of when an action is triggered (like opening an email) but only if that date is empty. So if someone opens an email, it will trigger the flow: "If opt in date is empty, opt in date is today." If I choose today, will it keep the date that I chose or will it update the date based on when the action took place? I don't want to add in a specific date, I want it to be the date that the action occured.
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

8 replies

A
Anonymous
February 10, 2014
Use the {{system.Date}} token for the value and block updates to that field via flow actions (Admin > Field Management > Block Field Updates). That way, it'll populate the field if it's empty but not overwrite it if it's already populated.
A
Anonymous
February 10, 2014
Hi Rebecca,
Drew is correct.

To expand on his point, we have a few different date tokens that have different formats. If you would like more options, they are all outlined in this article: https://community.marketo.com/MarketoArticle?id=kA050000000LB9WCAW

Will
A
Anonymous
February 13, 2014
I'm not sure the token working, in the results tab I see:   "Skipped Choice had one or more invalid tokens"
 
 
BUT the blocking updates in field management advice was great.  We've been looking for that solution for so long!
A
Anonymous
February 13, 2014
Hmm, and you're using this token? {{system.date}}

I think it's case sensitive.

 

A
Anonymous
February 13, 2014
Yes and in the flow it's not underlined in red like it's ignoring the rule so not sure whats going on.
A
Anonymous
February 13, 2014
What's your Smart List criteria?
A
Anonymous
February 13, 2014
Opens Emai: Email = Any
OR
Fills Out Form: Form name = Any
OR
Added to SFDC Campaign: Campaign contains "Webinar"
A
Anonymous
February 14, 2014
Hmm, that's odd. I would just try grabbing a single test lead and running a flow action to update your desired field with the {{system.date}} timestamp and see if it works.
Terms & ConditionsAccessibility statement

Loading footer...