Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
We have an "image" program token type on the roadmap. It is no different output than a "text" token, it's just a nicer user experience for being able to select an image in your design studio, upload one, or pick one from the web. Very similar to how our image picker works in Email 2.0.
What is the underlying issue here? It's not clear from this thread. Were your template's containers and modules structured one way for a while and then you changed it to use a different structure?If so, I wouldn't recommend completely overhauling the container structure or module structure on an app...
That code won't clear the cookie, it just makes sure the form submission will not be linked to an existing cookie on the machine.Since the user may have been cookied by a separate page on the same domain earlier, what you'd want to do is:- Disable munchkin on that specific landing page (see other re...
Yes, we have things in place for both email clicks/opens as well as web page visits. If you see specific activity you think is not real, please file a support ticket so we can look into it and determine if additional IPs should be added to our list.Justin
It won't impact template structure at all. It just impacts whether you have
and
I have an enhancement ticket filed for this. I'll update you when I know more about the ETA.
Hi Pam,I'd be happy to help but I can't reproduce this problem. I tried pasting in a random image from the web -> http://farm7.staticflickr.com/6123/5943204171_57e5d12f70_z.jpg Seemed to work fine and look as expected in Litmus tests. The template should handle images of any dimensions as it locks t...
v1.0 didn't really have a syntax. Thats why we recommend v2.0! Please, please, please, switch over. Better to avoid hassles later on. Our product team will not be investing in 1.0 anymore and support will be better for 2.0 moving forward.Anyway, here were the only rules for v1.0:Any HTML element cou...
Regarding the first point, the tokens should always be replaced with values corresponding to the person being sent the email. I will take a look at the support case, not sure what happened in your specific case.Regarding the second point, Gregoire already explained a bit, but it is only the Marketo ...
I remember some other community threads that discussed it previously, but can't find them now. Search in here is painful