Permalink
Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
123 lines (103 sloc) 12.4 KB

Compliance Email Reminders

Once you have determined the number of questionnaires each participant has completed, you may want to remind participants who have completed fewer than acceptable. You can use our compliance emailer Google Script. You can copy and paste the script from this page. You can also find it on GitHub. Below we will outline how to implement the compliance emailer.

This script checks will send an email to each participant if they do not meet a specific condition. This condition should be the number of questionnaires that participants should complete each day. The script will then record whether an email was sent (i.e., Email Sent) or whether compliance is met (i.e., Survey Completed) to the Compliance Google spreadsheet.

The Script

The compliance emailer consists of four sections.

Section 1

In the first section, you tell the script what each column in the Compliance Spreadsheet represents. For example, you will tell the script that the second column is the participant’s name, var name = column[1]. It is important to note that the column numbers in this section use zero-based character numbering. Thus, you have to subtract 1 from the actual column number (e.g., column 2 in the spreadsheet is referred to as column 1 in this section of the emailer script).

Section 2

The second part of the script determines whether the day that the script is being run falls between the experience sampling data collection period for a specific participant. It does this by counting the number of days since the first day of data collection. This value will be used to determine whether an email should be sent for a specific participant.

Section 3

The third section specifies the conditions that need to be met in order to send a reminder email. The condition of this if statement states that if the day the script is being executed falls within the data collection date range, and the participant has completed fewer than a certain number of questionnaires, and an email has not been sent, and a survey completed has not been posted to the spreadsheet, the compliance emailer should send an email to the participant. Because each day of the experience sampling period has its own compliance column and own email column, you will need to specify this condition multiple times, from the second day of the data collection period to the last day of the data collection period. You would not want to remind them the day the experience sampling period has ended because participants do not need to complete questionnaires on that day. If you are using ExperienceSampler for a daily diary study, you may want the script to remind participants to complete the questionnaire up until the day after the end of the data collection period.

Section 4

The final section specifies the conditions when the script should note that all the questionnaires have been completed. It is very similar to the third section, except instead of specifying that the participant has completed an insufficient number of questionnaires, you would specify that participants have completed the acceptable number of questionnaires or more. The action to be executed if this condition is met is to indicate that all questionnaires have been sent in the Email Sent column for that specific day. We programmed the script to do this so that it does not continuously email participants when they have completed the questionnaire. It also prevents the script from writing the status of the email in the wrong column.

Implementing the Script

Setting up the compliance emailer is very similar to setting up the compliance checker script. The only difference is that you have to paste in a different script and specify more values because there will be more variability in the emailer. For example, different researchers will have different acceptable numbers of questionnaires, and different researchers will collect data for different amounts of time.

  1. Go to Google Script and click on Start Scripting.
  2. Delete the following from the Script Editor: function myFunction(){}
  3. Copy and paste our Compliance Emailer script into the blank script editor.

In this code, you will have to make several changes.

First Section

  1. You will need to tell the script the Google Sheet ID of your compliance spreadsheet. Remember that the sheet id is found in the Google Sheet URL, and it is a long string of letters, numbers, and symbols that appears before /edit#gid=….
  2. You will also need to tell the script the Google Sheet ID of your spliced database.
  3. Now you will tell the script what each column in the Compliance Spreadsheet represents. This section appears after var column = data[i] line that appears inside the if (i>0) statement.
  • Remember that in this section, we use zero-based character numbering, so column 1 in the spreadsheet is referred to as column[0] in the script. You will need to declare a new variable for each column in your Compliance spreadsheet (e.g., var name = column[1]).

Second Section

At the end of the second section, you will need to customize one line (line 69 in GitHub file). This line determines which column the script should note the status of the compliance email, var complianceEmailColumn.

  • To calculate the compliance email column number, you determine the zero-based character number of the first email compliance column (e.g., column titled Compliance 1 Email Sent), and then subtract the daysFromTheFirstDataDay (i.e., days that have passed since the first day of the participant’s experience sampling data collection period).
    • For example, your first compliance email column may have a zero-based character number of 28, so your compliance email column statement would be var complianceEmailColumn = 28 – daysFromFirstDataDay.

Third Section

In the third section, you will specify the conditions that must be met to send a compliance reminder email. For our example, we will use an experience sampling design that notifies participants six times a day, but we only expect participants to complete 5 questionnaires each day for 7 days. We have six unique sets of conditions that can be met in order for an email to be sent. Because these conditions are for each day in the experience sampling data collection period, they do not all have to be met in order for the email to be sent. Instead, if any one of these sets of conditions is- met, an email should be sent. Thus, we will join each set of conditions with an “or” logical operator (i.e., ||).

Each set of conditions will have five components.

  • The first component is how many days have passed since the first day of the experience sampling period. This value will always be a negative number because we are subtracting a larger number from a smaller number. Thus, the day after the first day of the experience sampling period will have a value of -1.
  • The second component is how many questionnaires have been completed. This value should be set to be less than the minimum number of questionnaires that should be completed. In our example, we call this variable c1Met, and we will set it to be less than 5, c1Met < 5.
  • The third component states that c1Met must not be blank, c1Met !== “”. This will prevent the script from emailing participants if for some reason the compliance checker did not run.
  • The fourth component states that the compliance email column for the first day’s responses, which we will call c1Email, cannot be equal to the email sent value, c1Email !== sent.
  • The final component states that the value in the compliance email column for day 1 should also not equal Survey Completed, c1Email !== “Survey Completed”. This ensures that the emailer not email the participant if they have completed all their survey’s for the previous day.

Put all together, your set of conditions should look like this

(daysFromFirstDataDay === -1 && c1Met == 0 && c1Met !== "" && c1Email !== sent && c1Email !== "Survey Completed"). Then you repeat this for two days after the first day of the experience sampling period, || (daysFromFirstDataDay === -2 && c2Met == 0 && c2Met !== "" && c2Email !== sent && c2Email !== "Survey Completed"),

and so forth until you reach the value of 6, which is equal to the last day of the experience sampling period.

if statement.

Inside the if statement of the third section, you will specify the properties of your email message.

  1. First, we will nest another if statement inside the third section that states that an email will only be sent if the participant’s email, which we will call emailAddress, is not blank, if (emailAddress !== “”).
  2. You will then need to write your form email message in this section, which we will assign to the variable message.
  • To write your message, you will need to place it inside quotation marks. You can also insert your participant’s name into the form email by placing the variable associated with the participant’s name in your message (e.g., var message = “Hello ” + name + “, ”).
  • To create new lines in the body of your email message, you will use \n.
  • You will also notice that there is a + sign between each set of quotation marks. This let’s the script know that these sets of quotations are supposed to appear in the message together.
  1. Then you will specify the subject your of your form email, e.g., var subject = “Yesterday’s Smartphone App Surveys”.
  2. Then you will tell the app to send your email to your participant, MailApp, sendEmail(emailAddress, subject, message, {name: “Study Name”}).
  • In this case, you would specify either your lab or study name where is says Study Name. Finally, you will tell the script to indicate that an email has been sent, complianceSheet.getRange(startRow + i, complianceEmailColumn).setValue(sent).

Fourth Section

The final section is very similar to the third section, but much simpler. This section specifies when to note in the Compliance Spreadsheet that all the questionnaires have been completed, so it is an else if statement. The conditions for this statement are identical to the ones set in the third section with one exception. The number of questionnaires that must be completed should be set to be equal to or larger than the minimum number that you require. In our example, we will set this value to be equal to or greater than 5, c1Met >=5. Again, we will specify this set of condition for every in the experience sampling period. If one set of these conditions is met, then we want the script to write that Survey Completed in the appropriate email column, complianceSheet.getRange(startRow + i, complianceEmailColumn).setValue("Survey Completed").

Save Your Script

Once you have made these changes to the script, you should save your script.

  1. First, name your script. We named our script "Compliance Emailer".
  2. Then you will need to authorize the script to run by clicking on the debug icon beside the dropdown menu in the toolbar.
  3. Next, we will want to specify two time-based trigger so that the script will execute once every day. Click on the clock icon that appears beside the play icon. Then select sendComplianceEmails in the first dropdown menu, Day timer in the third dropdown menu, and then select the most appropriate time interval for the population being studied in the last dropdown menu.
  • For this script, we would advise you to select a trigger that is early in the day so that participants can actually increase the number of questionnaires they complete.

Debugging the Script

If you script is not working correctly, you can debug it by using the Logger.log function. The Logger.log function is similar to the console function in JavaScript. For example, you can check whether daysFromTheFirstDataDay is calculated correctly by including Logger.log(daysFromFirstDataDay) in your script.