Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
We do the same thing - keep many of our general operational and alert emails stored centrally in DS:And then these can be used across programs: lead lifecycle, all of our 'website content' programs (where we send both a tokenized confirmation email with a direct link to download the file, and a toke...
There’s been a long-standing issue with the way Marketo sees CRM users (in both MS Dynamics and SFDC) in that it will display all users – active, inactive, deleted – as available users to sync leads to from within Marketo. Many companies like us never delete user records - instead, we deactivate th...
I take it these are stand-alone smart campaigns and not part of a program? Simple solution, if so: create a program and you can include as many smart campaigns and emails as you want.
Obviously this isn't documented anywhere in Marketo. Did you ever think about writing a book about all of the undocumented information that's stored in your head (and some of it sprinkled here on the community and on your blog)?!
I thought this was already part of the AdBridge solution. I guess not.
Completely agree, Greg - and thanks for clarifying. I was just offering up another data point on how "unmarketable" our databases may become as a result of this "right"; and how your idea here would possible allow us to keep the "anonymized" records intact.
I think we may be underestimating the impact GDPR will have on our marketing database:In a February 2018 survey of 1,050 UK internet users conducted by The7stars, nearly 60% of respondents said GDPR is making them question how much data companies have on them. And about a third of those polled plan ...
Here's some more detail around anonymization/pseudonymization - which is the basis for Greg's idea (and a piece of core functionality that's needed in Marketo to help us marketers continue to report accurately and prove our value to the business):Looking to comply with GDPR? Here's a primer on anony...
Folder-level permissions were announced at Summit 2016 - and still don’t exist. I wonder if this will finally be available when the new UI is released.For large, global instances, this is critical.
Agree - we're very event-heavy and leverage these events to further grow our opt-in/consent database. This would be yet one more option to gather this consent - and expand the capability of the app.