====== External serial mail dispatch ======

If you want to send serial emails, you can create them either [[:en:survey:mailing:sosci|directly with SoSci Survey]] or with an external program. This tutorial is about how to create serial emails with such an external program. For an overview see [[:en:survey:mailing]].

There are several programs for sending serial mails, e.g. [[http://www.vwsoft.de/?sectionid=pgminfo&pgmid=3|Newsletter Genius]] or [[http://www.supermailer.de/|SuperMailer]], for Thunderbird there are plugins for sending serial mails (e.g [[https://addons.mozilla.org/de/thunderbird/addon/mail-merge/|Mail Merge]] or [[http://mailtweak.mozdev.org/|Mail Tweak]]) and even Outlook can send serial mails in combination with Word. Instructions for this can be found on the Internet.

If you want to send the invitations in an external program, you can either send the link to the questionnaire without any further information or personalize it using a access code. Personalized links allow...

  * a review of who has completed the questionnaire,
  * a restriction that each participant fills out the questionnaire only once and
  * an individual assignability of the data sets (access code only).



===== Variant Participation Links =====

Via **Invitations Mailings** -> **Access URLs** you can create links that work in the same way as the links in serial emails. These can be restricted to a specific questionnaire and (depending on your needs) allow multiple participation or not.

Set //Mailing // as [[:en:create:access|access restriction]] in the questionnaire so that the participation links work as intended, and third parties cannot access the questionnaire.

With this variant, it is not (!) traceable based on the data set to which participation link a questionnaire belongs. This can be advantageous if the data is to be collected anonymously.

You can determine the participation status for the participation links during or after the survey. To do this, download the list of participation links again under **Invitation mailings** -> **Access URLs** -> //URL Lists//. The participation status is shown in the column //Status//, the codes correspond to those for serial e-mails  ([[:en:survey:panel-download]]), whereby it is not possible to differentiate between 0 (not sent) and 1 (sent but not clicked) for participation links.


===== Variant access code =====

**Note:** Detailed instructions can be found in the instructions [[:en:survey:serials]]

For a personalized mailing, create the necessary number of valid access codes under **Invitation mailings** -> ** Access Codes** -> ** Management **. You can then assign these to the participants (e.g. in a spreadsheet) and include them in the questionnaire link in the e-mail ([[en:survey:url|]]).

Set //Access code // as [[:en:create:access|access restriction]] in the questionnaire so that each participant can only fill out the questionnaire exactly once with their access code.

**Important:** The access is stored directly in the data set (variable SERIAL). Since you have to assign the access codes manually to participants, it is your responsibility to manage the affiliation of participants (names/email addresses) and access codes (data records). Depending on organizational measures, you work with personal or pseudonymous data. This means that you have to comply with a number of requirements of the [[:en:general:dsgvo|DSGVO]].


==== Access codes ====

Access codes are beneficial if you do not want to send emails via SoSci Survey but use an external program. Serial numbers serve two functions: 

  - Ordered List ItemThe participant can interrupt the completion and continue later. (For details see [[:en:survey:resume]])
  - A questionnaire can only be filled out once with a access code (For details see [[en:survey:serials]]).


If you want to conduct multi-wave surveys with access code, you will encounter a small hurdle: The participant is told the same access code (the records are supposed to be matched, after all) and therefore can only continue the interview from the first time. The solution:  Under **Access Codes Management** there is a button //reset response status//. After that, each access code starts a new interview.