Josef_Lobotka

we can't add the id="mktoForm_nnn" to our existing form tag. You don't have to. You can add it to a custom attribute, e.g. data-marketo-id="mktoForm_1113". Then, after the page has fully loaded, you can use JS to pick up the value stored in `data-marketo-id` attribute and pass it to MktoForms2 method loadForm (https://developers.marketo.com/javascript-api/forms/api-reference/). This will return a virtual <form> Object that you can manipulate all you want before you append it into the page (e.g. add the ASP attributes you need to maintain). ... View more

Sure, you can wrap Munchkin initialization in that function if you want, it's harmless and will save extra traffic for affected users.  The API will not be supported in iOS nor Safari/Mac in the next release, though... so much for 98%! (That's why I didn't mention its availability in the blog post, because it's dying off.) And when you consider static tracking pixels (which can't check JS) and anti-tracking plugins (which can selectively send HTTP headers to certain sites, with no visibility to the library author) the effort would be even more wasted. (ETA: Wasted if added to the library itself, not saying you won't get something out of it on your specific site.) Yes, other analytical tools don't do it either and it almost feels like it is intentional. If you mean because the service wants to steal the anonymous data, I doubt it. Open source packages behave the same way.  Just not a priority. ... View more

As per Sanfords post below, API calls on anonymous leads return no information. If you want anonymous leads to appear in your database like old marketo days (be aware of the consequences) you could use the munchkin associate call to set a temporary unique email address (e.g. take the munchkin number string 1533412128399-11111@domain.com ) and then you'd be able to utilise API calls to get leadId by cookie. ... View more