Based on the article Upcoming Changes to Design Studio URLs  presented to the Marketo Community last week, I would like to get some clarification. " Existing URLs and references will continue to work after the migration to the new URL structure. However, in 2022, we will deprecate the old URLs structure in use today. More details on our deprecation timeline will be provided in March 2021." ... "Begin an audit of where you reference Design Studio assets on the web. This will help you begin a plan to update any existing references to our older URL structure before we begin deprecation in 2022. Generally this will be on non-Marketo pages, as our Landing Page editor will automatically format embedded images and forms in a compatible manner. Only references hardcoded to the old URL structure need to be updated, e.g.   http:// na-sj01.marketo.com /rs/123-ABC-456/images/cuteKitten.png. Relative references will continue to work without need changes e.g.  /rs/123-ABC-456/images/cuteKitten.png. Please work with your web developer to determine where you may need to make updates." My question would relate to a scenario like this: If I don't have a CNAME and I’ve already built emails and landing pages containing images from design studio. Once Marketo would update my Marketo instance to have a CNAME that would then change my design studio images file paths, would that leave my existing landing pages/emails with broken images? Since the image path will no longer match?  I don't see how Marketo could " automatically format embedded images and forms in a compatible manner". @Steven_Vanderb3 would you able to answer this since you've written the article. ... View more

Hi everyone, as you may know, Marketo switched off form prefill in 2019. Marketo says that prefill is still enabled if a lead would receive an email, click the tracked link in the email to arrive at a landing page with a form and then they would have prefill functionality work in a form. I tried just that, having a lead exist in Marketo, send a real email, click a button to a Marketo landing page and the form doesn’t prefill. The form field is an email field with prefill enabled and not a hidden field. I tested in two different instances with the same no prefilling results. Either something is missing from my testing scenarios, Marketo is bugging, or the prefill functionality no longer works from Marketo tracked email links. Is anyone else experiencing this problem? ... View more

Hi there, I've been using Sanford's prefill script which is very powerful and works great. The only issue is Marketo isn't fast enough to capture the form values on the follow up page after successful form submit. I always have to refresh the page in order to see the prefill form values or {{lead.tokens}} populate correctly. It's bad user experience to have to refresh the page or see empty values like Welcome _____ not you?   Is there a way we could check whether or not the form field values are coerced on the thank you page before completing page load for the thank you page? I'm not sure what to do or what approach to use. ... View more

This is a bizarre issue... An email is built with a snippet that is using segmentation. The segmentation is visible in Marketo email editor, in the email preview and upon email send. But if I click view in browser of the segmented snippet email, it reverts back to the default view of the segmented snippet.  Is this a Marketo bug? Segmentations done regularly without the use of a snippet successful show view in browser of the segmented content correctly. Can anything be done or is the only solution to not use segmented snippets in email? ... View more

Hi, I have a page with a form containing checkboxes for the user to select the email type they wish to subscribe to and the frequency. After form submit ideally they would land on a thank you page confirming their choices they just made on the form they've submitted. I understand that its possible to have their selections viewable on the thank you page if they would receive an email with a link to direct them to the thank you page that would populate their lead tokens and I have that built but I would prefer the first choice rather than an email confirmation. Secondly, if the lead would land on the page with the form for the first time, without data associated, I would like the email preferences checkboxes to be checked.  If they've already had preferences checked in their lead database, the form should be prefilled with their past selections as well as their email address. Is this possible with Sandy's prefill solution? Do they need to always be gated through an email for this case? Thank you for any possible insight, I could see how this can be useful to many scenarios down the road.  ... View more

Is there any danger in updating an email template that's associated with many emails? 1000+ emails or 5000+ emails? I once updated an email template associated with about 600 emails and it took almost an hour for Marketo to approve the updated email template. My concern is that it will begin the updating process and maybe crash and cause the template to be corrupted and unusable, is that possible? ... View more

Hi, I created meta og tags for various social media platforms. The code itself is correct, but I get an error from Twitter saying it can't load the image because the robots.txt will not allow the Twitterbot to crawl.  The image size for twitter is 300px x157px  and 129kb in weight. < meta property = " og:type " content = " ${og-type} " > < meta property = " og:title " content = " ${og-title} " > < meta property = " og:url " content = " ${og-url} " > < meta property = " og:description " content = " ${og-description} " > < meta property = " og:image " content = " ${og-image} " > < meta property = " article:published_time " content = " 2019-04-10 " /> < meta property = " article:author " content = " ${og-author} " /> < meta name = " twitter:card " content = " summary_large_image " > < meta name = " twitter:site " content = " @Company " > < meta name = " twitter:creator " content = " @Company " > < meta name = " twitter:title " content = " ${og-title} " > < meta name = " twitter:description " content = " ${og-description} " > < meta name = " twitter:image " content = " ${og-image-twitter} " > ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ Error from Twitter is: WARN: The image URL https://marketoURL.com/xx/xxx-xxx-xxx/images/twitter-image.jpg specified by the 'twitter:image' metatag may be restricted by the site's robots.txt file, which will prevent Twitter from fetching it. I think Marketo is blocking the Twitterbot from crawling the image. I know a solution would be to host the image externally. Is there any way of having the image be hosted in Marketo and allowing twitter to crawl it?  The robots.txt would look like this: User-agent: Twitterbot Disallow: I'm not sure if I feel comfortable allowing the twitter bot to crawl all of Marketo.  Any ideas? ... View more