Like the rest of Marketo ops in Europe at the moment, GDPR is VERY high on my priority list.I read an interesting article recently which indicated that it was more likely for a use...
Yup, exactly, Mr Whiteman! A no-brainer as far as I'm concerned... any 'ideas' or plans to build this sort of thing? Or do you know of a Launchpoint service that does this sort of ...
As a reasonably large organisation, we generate a LOT of content. Obviously, we leverage this content in Marketo, but the same (or very similar) content is also used on our website...
I tried using the {{system.dateTime}} token, too. Same result...As you can see here, the Timestamp field is populated just fine, but as soon as you 'write' the timestamp to the tex...
Hi Mark,Thanks for the reply, chap.Yeah, I was planning to prepend to the Change Log using Sanford Whiteman's line-break token trick (http://blog.teknkl.com/dark-mkto-alleys-line-b...
Hi everyone,In preparation for GDPR next year, I'm trying to create a text field that will capture every change that our users make on our preference centre, including a timestamp....
Any response from Marketo on this one? Time to build a solution to manage preferences for GDPR is getting a bit tight... would be great if we had this functionality ahead of any tr...
Thanks, Sandford. As per Dan's reply, thanks for working on this and coming up with an interim solution.That said, I won't be retraining my marketers on how to upload using this pr...
Hi Said,Yeah, the comma-separated UTF-8 upload is always a fallback, but this could introduce extra columns into the data (which is why there is the 'Open in Wordpad/Notepad' step ...