Answers.Body: <p>You can daisy-chain webforms using checksums, so on form 1 you set up your fields to collect contact detail data, then set up a second webform which actually adds them to your private email group, and having set the second webform up you can find the url with checksum on the CiviCRM tab of the webform, and then set that as the link that goes out in the email from the first webform.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-29T10:11:21.597Z
Answers.Text: To be sure I understand: So the user would end up on the second "confirm" webform, but would still have to click on the submit button to properly register?
Answers.UserDisplayName: Xavier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-29T17:56:48.077Z
Answers.Text: Yes true. We haven't used this approach for what you are doing. we have used it where we are signing people up and on the second form getting extra info, giving them a drupal account etc.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-30T16:00:17.190Z
Answers.Text: by checksum. you mean the one from {contact.checksum}? how can I access this from within a mail sent by webform?
Answers.UserDisplayName: Xavier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-30T18:50:47.417Z
Answers.Text: AH true i think I have skipped a step. You need to add the checksum field on the form 1, hidden, and set it in to the path in the email that will take them to form2. Then in form2, in the vertical tabs on the civicrm tab of the webform is a section called Additional Options, if you click on that you should see something like "To have this form auto-filled for anonymous users, enable the "Existing Contact" field for New Member and send the following link from CiviMail:
  <site>/<path>/<node-title>?cid1={contact.contact_id}&{contact.checksum}". Does that make more sense, if so i will update answer
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-30T21:25:39.420Z
Answers.Text: should have mentioned i tried it and works fine when you send the email from civi. but doesn't when you send it from webmail directly. when you chained the two forms. did you send an email between the two steps?
Answers.UserDisplayName: Xavier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-01T19:12:16.370Z
Answers.Text: THe link i have go out from Form 1 linking to Form 2 is something like this Please visit this page to confirm your registration:
  
  http://<site>/node/<id>?cid1=[submission:values:civicrm_1_contact_1_fieldset_fieldset:civicrm_1_contact_1_contact_contact_id:nolabel]&cs1=[submission:values:civicrm_1_contact_1_fieldset_fieldset:civicrm_1_contact_1_contact_cs:nolabel]
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-02-08T10:02:50.557Z
Answers.Text: In fact, if you add the 'contact id' and 'checksum' values for the contact in the civicrm tab, and edit the webform components that it creates, there are instructions there on how to do this.
Answers.UserDisplayName: commonpike
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-02-14T17:30:04.840Z
Answers.Text: This sounds like a method for avoiding the default opt-in confirmation message, and thereby enabling a more customisable approach, such as having different emails for different groups etc. I guess you could also get the webforms to create activity records so you have an explicit record for the sign up and confirmation? Maybe more GDPR-friendly.
Answers.UserDisplayName: Graham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-02-14T21:30:13.737Z
Answers.Text: sure the webform can create an Activity for every form submission
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-29T09:47:49.163Z
Answers.LastActivityDate: 2015-10-29T09:47:49.163Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>I've seen the option to double opt-in (send a confirmation email) when choosing a public group in webform, but I'd like to be able to:</p>
  
  <ul>
  <li>customise the confirmation email sent</li>
  <li>have a double opt-in for private emails</li>
  </ul>
  
  <p>Is there a way to do that in webform civi?
  I tried to find a checksum token to be used in a custom email, does it exist?</p>
  
  <p>Alternatively, is there a webform specific confirmation page that I could use? eg. <a href="https://www.drupal.org/project/webform_confirm_email" rel="nofollow">https://www.drupal.org/project/webform_confirm_email</a></p>
  
Tags: <webform-civicrm>
Title: How to create custom opt-in email for webforms
ThreadText: # How to create custom opt-in email for webforms
  
  (Asked by: username_0 on 2015-10-29)
  
  I've seen the option to double opt-in (send a confirmation email) when choosing a public group in webform, but I'd like to be able to:
  
  * customise the confirmation email sent
  * have a double opt-in for private emails
  
  Is there a way to do that in webform civi?
  I tried to find a checksum token to be used in a custom email, does it exist?
  
  Alternatively, is there a webform specific confirmation page that I could use? eg. <https://www.drupal.org/project/webform_confirm_email>
  
  **Tags:** webform-civicrm
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-10-29. Score: 3
  
  You can daisy-chain webforms using checksums, so on form 1 you set up your fields to collect contact detail data, then set up a second webform which actually adds them to your private email group, and having set the second webform up you can find the url with checksum on the CiviCRM tab of the webform, and then set that as the link that goes out in the email from the first webform.
  
  > **Comments:**
  > **username_0**: To be sure I understand: So the user would end up on the second "confirm" webform, but would still have to click on the submit button to properly register?  
  > **username_1**: Yes true. We haven't used this approach for what you are doing. we have used it where we are signing people up and on the second form getting extra info, giving them a drupal account etc.  
  > **username_0**: by checksum. you mean the one from {contact.checksum}? how can I access this from within a mail sent by webform?  
  > **username_1**: AH true i think I have skipped a step. You need to add the checksum field on the form 1, hidden, and set it in to the path in the email that will take them to form2. Then in form2, in the vertical tabs on the civicrm tab of the webform is a section called Additional Options, if you click on that you should see something like "To have this form auto-filled for anonymous users, enable the "Existing Contact" field for New Member and send the following link from CiviMail: <site>/<path>/<node-title>?cid1={contact.contact_id}&{contact.checksum}". Does that make more sense, if so i will update answer  
  > **username_0**: should have mentioned i tried it and works fine when you send the email from civi. but doesn't when you send it from webmail directly. when you chained the two forms. did you send an email between the two steps?  
  > **username_1**: THe link i have go out from Form 1 linking to Form 2 is something like this Please visit this page to confirm your registration:  http://<site>/node/<id>?cid1=[submission:values:civicrm_1_contact_1_fieldset_fieldset:civicrm_1_contact_1_contact_contact_id:nolabel]&cs1=[submission:values:civicrm_1_contact_1_fieldset_fieldset:civicrm_1_contact_1_contact_cs:nolabel]  
  > **username_2**: In fact, if you add the 'contact id' and 'checksum' values for the contact in the civicrm tab, and edit the webform components that it creates, there are instructions there on how to do this.  
  > **username_3**: This sounds like a method for avoiding the default opt-in confirmation message, and thereby enabling a more customisable approach, such as having different emails for different groups etc. I guess you could also get the webforms to create activity records so you have an explicit record for the sign up and confirmation? Maybe more GDPR-friendly.  
  > **username_1**: sure the webform can create an Activity for every form submission  
  
  ---
  
  