How to use collected fields in newsletter

hi

i am also interested how this works. were you able to figure it out?

in addition i would like to let the user subscribe to multiple newsletters at once (checkboxes): #884496: subscribe to multiple newsletters at once

thanks

lukas

Without this information this module seems to be useless, isn't it? So how do you use collected data for a personalized newsletter?

Ok, there is an error in the table component display, you can still download the data with the email address informed, but in the "table view" it doesn't appear.
I'll apply a patch shortly to fix this.

Fixed in the last dev version

First of all, thanks for the module!

I would like to know the same thing. I do not understand how the final answer is related to the question. Could you perhaps give some clues as to how one could use webform fields (with, let's say, the names "name" and "firstname") field for a personalised e-mail campaign. I see all the fields in the table of the webform, and I see the e-mail address being added to the simplenews newsletter subscription list, but I do not know how a newsletter could use the additional fields such as "name", "first name" and "company".

Thanks!

Indeed. What I would expect is 2 things - 1) people who subscribed to newsletter via Webform would show up in subscribers list of newsletter and 2) webform field tokens would show up in token list in newsletter node form. That does not happen with latest release and -dev seems older than release.

I am looking at the code and it does nothing, it just adds component but there is no connection with simplenews at all. How do simplenews get to use webform submissions?

Update: Oh, there it is, in function _webform_submit_newsletter_email.

Original post and my point 2) is still valid.

Hi

The module already accomplish point 1 of comment #7 but it would be great to have the tokens for customized mails.
Patches are welcome!

Wonder how would one add tokens if newsletter ID is not known while node form is filled in. Some wired UX coming this way.

Afaik this happens as well with CCK i.e. since you can put tokens of all fields even if they are not part of the current content type when you create a node.
The ideal thing will be to include all the webform "fields" as tokens for the newsletter, when you create the newsletter is when the token placeholders get replaced by its real values.

*subscribe*, interested in using tokens in the newsletter emails.

*subscribe*, interested in using webform tokens in simplenews subscription confirmation email.