Today, we can store various types of assets in a program, but we cannot stores files and images.
When creating a gated content program, for instance, the file itself has to be located in the design studio. Same for email or landing page images.
Enabling to store them in the program, with a name that would be prefixed with the program name, would make users life much easier when designing or cloning programs. After cloning, if you want to change the image, you would just go to the image asset and replace it, and automatically, all the emails and landing pages that use it would be updated, without need to edit them. When replacing an image, Marketo would check and enforce the fact that the image size remains the same.
This could also be done with a "File/image" type or program token. This could drive to an even more powerful feature since we could imagine that with a token, the program designer would be able to set the min and max size of the image, which would also reduce the risk of errors. When populating the token, the user would have the choice between loading a new image from his laptop, capture an image from the web or use an image that is already in the design studio.
The workaround would obviously to use the rich text token, but reason why we do not want to use rich text tokens for this is because it's error prone, especially in conjunction with responsive templates. People can too easily temper with size, style, etc...
Another use cases would be to render the image URL in a CSS or HTML background, and it would be much easier to pick the image in the image library than having to look for it in the design studio and copy and paste it's URL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.