Mailchimp has an article that explains how to track signup form locations by adding hidden fields to the mailchimp form.
All well and good, but if you put the form in a Drupal block, the location of the form suddenly becomes a variable.
I'm wondering if the token module, and a token in place of a hard-coded hidden field value that tracks location, would be a good approach? The form code for the hidden field currently looks like this:
<input id="SIGNUP" name="SIGNUP" type="hidden" value="global" />
So, the value "global" is the one that needs to change based the the page that the block is displayed with.
I'm not sure about which token to use, but thinking I'd use something like the page title or page url. In the case of a simple block, do I just need to get and enable the token filter module?
Any thoughts on token as a good option, or other ideas I should consider?
Note - this has nothing to do with the mailchimp module (http://drupal.org/project/mailchimp), which I don't have installed on this site since this site doesn't yet have any notion of user logins.
Links: token and token_filter.