SanfordWhiteman

I found a weird bug highlighted by our team, when clicking on "view in browser" in the web browser viewTo be clear, do you mean clicking View as Web Page to open the email in a browser tab, then again clicking the View as Web Page link in that new tab?

In addition to configuring robots.txt, yes.

2 different questions here. You don’t need to let the crawler index your Marketo LPs. But we almost always run GA because we want to see journeys that start with Marketo LPs and continue to other sites under the same domain. Also, if you’re logging GTM Data Layer events for embedded Marketo forms, i...

It’s always best to provide details about what you’ve tried, reduced to the most concise real-world example. If you mean Can I have two sibling elements, only one of which is shown based on a boolean toggle” then yes, like so:

This has come up on previous threads — it’s the standard browser behavior when you use an IFRAME! In order to break out of the IFRAME and redirect the top-level window, you need to use the Forms JS API onSuccess. There’s no setting in Form Editor that knows you want to do this, it needs to be done w...

A Soft Bounce after delivery — called an “out-of-band“ Soft Bounce in Marketo — mean: (1) the recipient’s mailserver (MX) said “OK, message accepted” when Marketo attempted to send the email ... but then... (2) some time later another server, typically deeper inside the recipient’s infrastructure, ...

Going forward, please use example.com as an example domain (that’s what it’s for). The domain you’re using as a dummy domain is actually a phishing site. Fundamentally, you can‘t have multiple rows for the same email address in the same CSV. Only one of them will end up being used — the others will ...

The shape of your data isn't quite clear. Are you saying you have multiple rows for some email addresses? (And what specifically do you mean by "IDs" –Marketo Lead IDs?)

To be clear, Boolean fields work this way 99.999% of the time! The value of the field will be integer 1/0, boolean true/false, or sometimes a stringified "true"/"false" or "1"/"0". The value won’t be the name of the field, except in very quirky circumstances like HTML Boolean attributes.

The problem with this model is doing individual lookups by cookie in response to end user activity makes you vulnerable to a trivial DoS attack. Integrations that attempt this have catastrophic effects on Marketo instances, and it’s not recommended. (Note even without anything malicious, you have a...