SanfordWhiteman

Jamie, I assume we're talking about unique IDs per referred lead (which can be tied to the referrer via a static prefix like ReferrerCo-129873254) but not the same field for all leads. If one just wants one field to ident ReferrerCo, then you could look for Filled Out Form constrained by a Referrer...

Storing the values submitted from that same browser in a cookie (or, even better, in the browser's LocalStorage, but same idea) is easy. But that doesn't duplicate the functionality of prefill, since if someone uses a new device or clears cookies there's no longer a source for that data -- compared...

Using the Forms 2.0 JS API, add a randomly generated ID to the form as a hidden field. That ID becomes a unique "job ID" for the form fillout. Note that if you're not keeping a history of that field, then it will be overwritten if the same lead gets referred again, so you should block updates to i...

I don't know anything about RTP (we don't have the module, either) but it seems unlikely.Checking the Referer wouldn't make any difference, as a malicious user would just fake the Referer. The direct problem is the tight coupling of one form post = one API call. Like I said to another user, if the...

Pls check my comment here: Re: SPAM from Lead Form

To me, that fake ReCAPTCHA 2 looks far worse than a real ReCAPTCHA 2. Two mutually exclusive checkboxes? I don't care if the question is purposely absurd, the UI needs to make sense.Plus it's effortlessly fakeable if someone targets your particular form (a little human special sauce + a bot = jus...

Sure. An easy approach is by having a regular Rich Text widget in addition to the hidden text field. Copy the value into the widget so you can style it however you want.Just takes a little line of JS:MktoForms2.whenReady(function(form){ form.getFormElem()[0].querySelector('#showEmail').innerHTML =...

No worries about the accuracy/isolation of Anonymous Leads.However, you can consider the leads in your case Pending Leads -- as distinguished from Anonymous and Named Leads. A Pending Lead uses the Munchkin cookie as a placeholder email address, and as such is a real lead that can be added to progr...

You need to remove the _mkto_trk cookie / _mkt_trk field from the form as well, not just remove Munchkin (because staff will already have a Munchin cookie).

Unless you mean leaving it encrypted all the way to the back end (necessitating a custom, very complex back-end workflow that I don't know that anybody is actually doing in reality) then you can already post the form on behalf of whomever you choose.