SanfordWhiteman

You don't need a different form, just change the text when the form loads.For example: http://jsfiddle.net/sanford/3yzxa7m7/5/show/?My%20Labelhttp://jsfiddle.net/sanford/3yzxa7m7/5/show/?Another%20Label Same form is embedded both times, reading the button text out of the URL.

It doesn't have to impact testing. Just program a way to override the exclusion. For example, if you set a certain cookie, then your browser gets tracked even if you're coming from one of the known IPs.

The best way is to defuse internal web activity from being tracked at all. Have your webserver not initialize Munchkin if the client's IP address and/or PTR is in one of your known ranges.

I wouldn't worry about length limits unless your client imposes one for some reason. On the server side it's going to end up in the same (dynamic string) variable so it should have the same processing limit.Also even with a low limit like 8K you're still going to be able to send 100 80-character e-...

That endpoint is supposed to be used via GET. As the documentation states, if you use POST (which presumably you would only do if your client was hard-coded to use POST only), you have to add _method=get override. Obviously it's easier to just use GET.

I would have everyone use the standard means of author attribution in the head of each page: (this won't be entered automatically, though once they enter it, if they clone previous content it would already be there).Then have Munchkin (in your template code, again a one-time entry) send a custom pa...

@Sarah seconding Justin, a lead may have a a Munchkin cookie set by your website ExampleCorp.com or EC and be associated with a known lead there... but that cookie isn't going to be sent to a standalone social property, call it SarahGram.com or SG. Even if SG supports custom scripts, so it can load ...

@Rajesh I can understand working on millions at once may not be feasible, but you can straightforwardly divide them into 36 already-unique buckets -- where mail contains @a, @b, @c... @8, @9. Then aggregate across all the buckets. Kind of a hack, of course, but don't know of another way.

Around midyear we're planning to package our internal reply-to-Marketo service as a SaaS app.We do write inbound replies to Marketo and require no special setup in your receiving e-mail client.

@Kenny E if you're trying to keep the QS and pass it verbatim to another page, your approach isn't correct:String::split() returns an array and by defintion does not include the "?" character.It's not necessary to parse location.href at all: location.search already contains the query string.Using sc...