Case: track multiple signup forms for one list

Is this currently possible with the Drupal MailChimp module?
MailChimp allows this with their embedded forms.
And I'm currently checking out the webform_mailchimp route, not sure if that's the way to go.

To be able to track where subscriptions came from, we should be able to add multiple blocks for one list or alterations of the basic block for a list.
Tracking 'signup source' is not enough, because that always seems to be listed as 'API - Generic' using the Drupal MailChimp module.
Tracking based on signup form (Drupal Block) allows us to segment the list based on signup form / block (merge tag value)

It can be achieved by customizing a field value per MailChimp form (or Drupal Block).
Setting a hidden field value seems to do the trick, for example:
<input type="hidden" name="FORMSOURCE" id="FORMSOURCE" value="ebook1" />
or
<input type="hidden" name="FORMSOURCE" id="FORMSOURCE" value="ebook2" />
Allows one to send the corresponding ebook in the 'Welcome email', based on conditional merge tags.

Documentation

Tracking separate forms by customizing MailChimps embedded form
http://blog.mailchimp.com/tracking-signup-pages-via-the-mailchimp-embedd...

Conditional merge tags
http://kb.mailchimp.com/article/all-the-merge-tags-cheatsheet#Conditional

Comments

silkogelman’s picture

Update: I've managed to do this with a webform_mailchimp configuration.
I'm happy to elaborate if people want to achieve the same result.

silkogelman’s picture

Issue summary: View changes

edit 1 to 'it'

amytswan’s picture

Status: Active » Closed (won't fix)

“And now our watch [for support of the 7.x-2.x version of the MailChimp module] has ended…” With the approaching deprecation of MailChimp’s API version 2.0, I’m sad to say we too must turn the page. This branch will become unsupported in early October and officially deprecated by the end of this year (2016).

Fret not! The 7.x-4.x and 8.x versions come highly recommended. Both are using Mailchimp’s new API 3.0 and are being actively maintained. If you find this issue still exists on either the 7.x-4.x or 8.x branches, let us know by opening a new ticket. “What is dead may never die, but rises again, harder and stronger!”