Diego_Lineros2

I undestand, you do not control third party software, what you do control is your phone, if a massive part of the equation makes a change you lift your phone, call and find a solution or find an alternative, but even the MSI Outlook plugin is out of date.

This is yet another recent Marketo disappointment, this is a key functionality and Marketo failed to keep the product up to date. It's been years since Lihghtining was released, everyone knew about the issues coming in advance and nothing has beed done apart from offering a paid add on. AnneMarie Co...

This thread is not about Hubspot or Partdot or whatever, it is about Marketo and what we are not getting and we won't get. I appreciate AnneMarie Coveli response, and I must be clear, this is not to go against Marketo or be destructive, all the opposite, this is to make a wake up call for a product ...

I know some people like you are real advocates, thats fine Josh, and its good to see you back here after a deserved break, but it's also good leave passions behind and think what are you getting for your money. Your answer supports what I said, "very few critical User Ideas have launched in years", ...

I have a text token with this format 16 Jul 2019 12:00 UTC then I have a data change step like this {{my.texdatetoken}} - 2hours , then the waiting step. The calculation is correct and it works as trigger, not as batch because I get the same error than Jay Jang

This is somenthing very interesting, if it is a trigger campaign, it works for me, if it is a batch campaign doesn't take the datetime token.

Good solution, just the laguage segmentation is missing.