SanfordWhiteman

Actually this also includes @example.com.au and suchlike. It's not a perfect solution. To get more accurate create an ALL filter CONTAINS @example.com and NOT CONTAINS .com.

@Sara M use an Opened Email filter and type in the User-Agent identifier. For example, this filter shows leads using Microsoft Outlook 2013 (part of "MSOffice 15," 15 being the internal version number for Office 2013):However, be careful to remember: these are people who read your emails with image...

@Takehiro's solution would work -- I wouldn't call one of the types "anonymous" and the other "known" though, as they both are known, one just has a First Name filled in. However a more appropriate approach IMO is to use Email Scripting (Velocity) where this kind of conditional logic is possible.

Well, you could certainly set the value to () using the Forms 2.0 JavaScript API. So final results would look like: Yes (10/20/2015)Of course if you do this you must always use the generic Text field type -- rather than Date or Yes/No (boolean) type fields -- because you're no longer using a speci...

@Ramesh I wouldn't actually "Link them to a web page" per se because then you're talking about opening or replacing a browser tab/window. Link the images to the munchkinFunction('clickLink') instead. Then the person does not leave the current page but their choice is logged just like a click.It al...

@Lisa J What do you mean by "wrap it"? The outer wrapper for the embedded form is just an HTML FORM tag. You can style it any way you like. As @Mike points out you can have custom CSS come in along with the form itself, though if the CSS selectors refer to elements that aren't inside the FORM tag ...

Sure, go ahead!It's also going to go into the Forms 2.0 Cookbook I'm working on -- but those recipes will be proof-of-concept stuff like in most of my posts rather than includeable libraries. I'll post back here so maybe you can link to the Cookbook when it's up.

@Jesse B If Admin > Email (which @Josh also referenced) doesn't pertain to your question then you need to phrase it a different way. What do you mean by "recognize" if not "include my link instead of the default one"?

I'll have to look at this later, as I don't have time this week. I will say that you don't need to hide < and > in JSON (by using \unnnn). You can, yes, but you can also use actual Unicode characters, which is quite a bit easier to read!

Yes, that technique requires a new, writable custom field. But that requirement is kind of overkill if you only want to show the Full Name on the form and split it into First and Last (i.e. you do not wish to save the Full Name in Marketo). You can quite straightforwardly add a dummy Full Name tex...