Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Right now, there is no accurate way to determine if a file is identical, but uploaded with a different name inside a Marketo instance. While you can pull file size and try to 1:1 compare sizes to understand if a file is identical, this is an imprecise method. By storing some sort of checksum hash (M...
You're in luck--the User Management API was recently released. That said, there's not a plug-and-play integration with Okta yet, but you can at least put something together manually.
Update: As of 2020-02-28, this behavior no longer occurs! Sending samples of templates actually does exactly what this ticket suggests—it sends the code itself as expected with all mktoAddByDefault modules. Thanks, whoever fixed this.
ContentAI currently tries to generate an image (with or without content title, CTA, etc.) for placing content in an email. However, this results in the predictive content failing to have much customizability in display, and more importantly, causes the predictive content to be inaccessible. The fina...
While there's a lot of use from the mktoActive and mktoAddByDefault attributes when defining modules for email templates, there's a more common problem that hasn't been addressed with template attributes: requiring a module to be on all emails within a template. Sometimes, it doesn't make sense to i...
One of the main uses of the Get Lead Changes endpoint for the REST API is to retrieve previous value data, often when some process has gone awry and values need to be reverted. In high-activity instances, there may be several things changing a data value, however—even if you attempt to constrain by ...
Agreed with Sanford--why not use the existing link ID setup? I do something in a bit of reverse where I assign all of an email's standard links (logo, social icons, whatever) a specific link ID prefix so they may be screened out for reports, Smart List triggers, and so forth. There's an appropriate ...
Straightforward request: because mktoString variables can be referenced inside editable mktoText areas in emails, they automatically are copied into the text version of emails. However, because the text version of the email does not process email module variables, only the variable name itself shows...
Again, I'm a little confused--how is that different than the existing description aside from UX/placement? I'm not trying to be obstinate but just trying to understand how that differs from today's description, which can be added under the field name per my screenshot.
I'm a bit confused on this ask—are you referring to something separate from the existing description today on individual fields?(The UI to add descriptions and its locking of lines for multi-line descriptions is wonky, I'll give you that.)