SanfordWhiteman

If this is specifically an AEM question, it should be in that Community. Marketo logs actual Filled Out Form activities, but Marketo doesn't know which embedded forms could potentially be filled out on 3rd-party webpages, i.e. doesn't know where the embed has been deployed, page-by-page.

Cause is clear. The Custom CSS for Form ID 1873 sets the .mktoButtonRow to {display:block} without properly scoping the rule to just that form. So it applies to all forms, including 1877 which you want to be inline. Form 1873 should have: #mktoForm_1873 .mktoButtonRow{ display: block !important;} ...

Eh, @Travis_Schwartz ?

Well, there aren't that many of them. 🙂

Then they can't be hidden. I mean, there has to be some utility to having hidden fields. Not seeing them in the UI or via API is what the setting is all about.

It's not that odd as the fields are still synced and are still visible in Field Management, even while hidden. The UI export reflects what you can see in the UI. You should be using the Describe Lead API endpoint, which will not return hidden fields. It's specifically designed for this scenario; the...

You can't, in fact the notion of a "permalink" doesn't even exist in Marketo itself. When you preview an email in the context of a lead, it displays the content as it would be sent that day.

Is this possible without custom JS?No, it's only possible using JS, which is already written here: https://codepen.io/figureone/pen/5bf736062cdf6b4fa20487235abfe88a

How are you deriving the list of fields in the first place? Are you using the Describe Lead endpoint? There should not be a situation where you're trying to get fields you know in advance are hidden/nonexistent.

You can't directly include the ActLog. You can use a history field (which is a Textarea field that you continually append to) and mirror certain triggering information there. For example, write the {{system.timestamp}} {{trigger.name}} for a Filled Out Form trigger and that'll show the form name. Se...