Chapter 17 - Revision history

152.78.222.128 at 14:41, 24 August 2010

2010-08-24T14:41:20Z

← Older revision		Revision as of 14:41, 24 August 2010
Line 1:		Line 1:
	=~~= Chapter 17:~~ Sending e-mails ==		= Sending e-mails =
	=== How to automatically send an e-mail to your end-user or to yourself ===		=== How to automatically send an e-mail to your end-user or to yourself ===
	==== The formula for sending e-mails ====		==== The formula for sending e-mails ====

Aco at 08:49, 27 July 2010

2010-07-27T08:49:06Z

← Older revision		Revision as of 08:49, 27 July 2010
Line 86:		Line 86:
	There may be times when you need to cancel an e-mail that you may have set up. For example, if you have a number of sessions in your intervention and you wanted to send an e-mail to remind people if they do not log on to the next session, then you may set up an e-mail reminder to ask them to do so. However, if they do log onto the session before the reminder is sent out then you can set the logic up to cancel the email.		There may be times when you need to cancel an e-mail that you may have set up. For example, if you have a number of sessions in your intervention and you wanted to send an e-mail to remind people if they do not log on to the next session, then you may set up an e-mail reminder to ask them to do so. However, if they do log onto the session before the reminder is sent out then you can set the logic up to cancel the email.

	The logic for cancelling an e-mail includes the command cancelemail followed by the unique e-mail name and the e-mail address. A basic written example of this logic would be:		The logic for cancelling an e-mail includes the command <code>cancelemail</code> followed by the unique e-mail name and the e-mail address. A basic written example of this logic would be:

	<code>after login2 cancelemail(unique name for e-mail, e-mail address) goto page1session2</code>		<code>after login2 cancelemail(unique name for e-mail, e-mail address) goto page1session2</code>

Aco at 08:19, 27 July 2010

2010-07-27T08:19:56Z

← Older revision		Revision as of 08:19, 27 July 2010
Line 95:		Line 95:
	A demo accompanying this example can be found on the LifeGuide Community site entitled '''Email Example 3'''. Note that for testing purposes the time for sending the e-mail has been set to 10 minutes (600 seconds).		A demo accompanying this example can be found on the LifeGuide Community site entitled '''Email Example 3'''. Note that for testing purposes the time for sending the e-mail has been set to 10 minutes (600 seconds).

	<code>show welcome~~</code>~~		<code>show welcome
			show signin</code>
	~~<code>~~show signin</code>

	* Show end-users the first page of the intervention which has been given the unique name welcome. This page consists of a link to either a signin page for new end-users to sign up for the intervention or a login page for registered end-users.		* Show end-users the first page of the intervention which has been given the unique name welcome. This page consists of a link to either a signin page for new end-users to sign up for the intervention or a login page for registered end-users.
Line 106:		Line 105:
	* This logic would be written all on one line or can be broken up into two lines using …		* This logic would be written all on one line or can be broken up into two lines using …

	<code>show page1~~</code>~~		<code>show page1
			show page2
	~~<code>~~show page2~~</code>~~		show page3</code>

	~~<code>~~show page3</code>

	* These pages represent the first session (of course one session is likely to be much longer than this).		* These pages represent the first session (of course one session is likely to be much longer than this).
Line 118:		Line 115:
	* This is the last page of the session that encourages end-users to close the site and work on their goals for the week. Alternatively, users have a chance to skip straight to session 2 by clicking on a jump button that takes them to the '''sess2p1''' page.		* This is the last page of the session that encourages end-users to close the site and work on their goals for the week. Alternatively, users have a chance to skip straight to session 2 by clicking on a jump button that takes them to the '''sess2p1''' page.

	<code>show login~~</code>~~		<code>show login
			show sess2p1</code>
	~~<code>~~show sess2p1</code>

	* If end-users select the login button on the '''welcome''' page they will go straight to the '''login''' page. Once logged in they will then go to '''sess2p1'''.		* If end-users select the login button on the '''welcome''' page they will go straight to the '''login''' page. Once logged in they will then go to '''sess2p1'''.

	<code>after sess2p1 if cancelemail ("reminder", login.email2) goto sess2p2~~</code>~~		<code>after sess2p1 if cancelemail ("reminder", login.email2) goto sess2p2
			show sess2p2</code>
	~~<code>~~show sess2p2</code>

	* If an end-user visits the '''sess2p1''' page before the time specified on the sendemail command, then the e-mail will be automatically cancelled. This is the logic for cancelling the e-mail (again, this should be written on one line). The unique e-mail name is the same as the unique name in the sendemail command above and the e-mail address is taken from the interaction on the '''signin''' page.		* If an end-user visits the '''sess2p1''' page before the time specified on the sendemail command, then the e-mail will be automatically cancelled. This is the logic for cancelling the e-mail (again, this should be written on one line). The unique e-mail name is the same as the unique name in the sendemail command above and the e-mail address is taken from the interaction on the '''signin''' page.
Line 132:		Line 127:

	==== Example 4: Cancelling e-mails when the e-mail address needs to be taken from an earlier session of the intervention ====		==== Example 4: Cancelling e-mails when the e-mail address needs to be taken from an earlier session of the intervention ====
	<code>show welcome~~</code>~~		<code>show welcome
			show signin</code>
	~~<code>~~show signin</code>

	* Show end-users the first page of the intervention which has been given the unique name '''welcome'''. This page consists of a link to either a '''signin''' page for new users to sign up for the intervention or a '''login''' page for registered users.		* Show end-users the first page of the intervention which has been given the unique name '''welcome'''. This page consists of a link to either a '''signin''' page for new users to sign up for the intervention or a '''login''' page for registered users.

	<code>after signin if and (sendemail ("reminder1", signin.email, "Stress Less: Session 2", "This is your one week reminder for the Stress Less intervention", 600),		<code>after signin if and (sendemail ("reminder1", signin.email, "Stress Less: Session 2", "This is your one week reminder for the Stress Less intervention", 600),
	...~~</code>~~		...
			savevalue (signin.uname, "email", signin.email)) goto page1</code>
	~~<code>~~savevalue (signin.uname, "email", signin.email)) goto page1</code>

	* After the end-user has signed up to the intervention a logic command is then set up to send an e-mail to them 1 week (or 352800 seconds) after they first visited this page to remind them to go back to the intervention for the next session. The unique name for this e-mail consists of the end-user’s username appended to the string reminder1. The e-mail address is taken from an interaction on the signup page that is uniquely named email.		* After the end-user has signed up to the intervention a logic command is then set up to send an e-mail to them 1 week (or 352800 seconds) after they first visited this page to remind them to go back to the intervention for the next session. The unique name for this e-mail consists of the end-user’s username appended to the string reminder1. The e-mail address is taken from an interaction on the signup page that is uniquely named email.
	* Here the savevalue command is used to save the e-mail address of the end-user against their username so that the e-mail address can be loaded in subsequent places in the logic.		* Here the savevalue command is used to save the e-mail address of the end-user against their username so that the e-mail address can be loaded in subsequent places in the logic.

	<code>show page1~~</code>~~		<code>show page1
			show page2
	~~<code>~~show page2~~</code>~~		show page3</code>

	~~<code>~~show page3</code>

	* These pages represent the first session (of course one session is likely to be much longer than this).		* These pages represent the first session (of course one session is likely to be much longer than this).
Line 158:		Line 149:
	* This is the last page of the session that encourages end-users to close the site and work on their goals for the week. Alternatively, users have a chance to skip straight to session 2 by clicking on a jump button that takes them to the sess2p1 page.		* This is the last page of the session that encourages end-users to close the site and work on their goals for the week. Alternatively, users have a chance to skip straight to session 2 by clicking on a jump button that takes them to the sess2p1 page.

	<code>show login~~</code>~~		<code>show login
			show sess2p1</code>
	~~<code>~~show sess2p1</code>

	* If end-users select the login button on the welcome page they will go straight to the login page. Once logged in they will then go to sess2p1.		* If end-users select the login button on the welcome page they will go straight to the login page. Once logged in they will then go to sess2p1.

	<code>after sess2p1 if cancelemail ("reminder", loadvalue (signin.uname, "email")) goto sess2p2~~</code>~~		<code>after sess2p1 if cancelemail ("reminder", loadvalue (signin.uname, "email")) goto sess2p2
			show sess2p2</code>
	~~<code>~~show sess2p2</code>

	* If an end-user visits the sess2p1 page before the time specified on the sendemail command then the e-mail will be automatically cancelled. This is the logic for cancelling the e-mail (again, this should be written on one line). The unique e-mail name is the same as the unique name in the sendemail command above, and the e-mail address is loaded from the information that has been saved as email which was taken from the interaction on the signin page.		* If an end-user visits the sess2p1 page before the time specified on the sendemail command then the e-mail will be automatically cancelled. This is the logic for cancelling the e-mail (again, this should be written on one line). The unique e-mail name is the same as the unique name in the sendemail command above, and the e-mail address is loaded from the information that has been saved as email which was taken from the interaction on the signin page.

152.78.65.22 at 15:43, 26 July 2010

2010-07-26T15:43:22Z

← Older revision		Revision as of 15:43, 26 July 2010
Line 19:		Line 19:
	The best way get around this problem is to use the <code>append</code> command to attach the end-user’s username onto the unique name you have given to the e-mail message. You will then have a unique name for that e-mail.		The best way get around this problem is to use the <code>append</code> command to attach the end-user’s username onto the unique name you have given to the e-mail message. You will then have a unique name for that e-mail.

	So, in the example below, the username that the end-user provided on the login page of the intervention has been appended to the string ~~“sessionfinish”~~ to create a unique name for each of these emails that are sent out.		So, in the example below, the username that the end-user provided on the login page of the intervention has been appended to the string <code>"sessionfinish"</code> to create a unique name for each of these emails that are sent out.

	<code>append (login.uname, "sessionfinish")</code>		<code>append (login.uname, "sessionfinish")</code>
Line 29:		Line 29:
	When sending e-mails to end-users, the e-mail address will be different for each person. The e-mail address will probably come from a previous interaction in the intervention. Therefore putting the page name and interaction name in this section of the logic will mean that this is the e-mail address that will be used (e.g. '''login.email''' (where '''email''' is the unique name of the interaction that asked end-users to type their e-mail which can be found on the page called '''login''')).		When sending e-mails to end-users, the e-mail address will be different for each person. The e-mail address will probably come from a previous interaction in the intervention. Therefore putting the page name and interaction name in this section of the logic will mean that this is the e-mail address that will be used (e.g. '''login.email''' (where '''email''' is the unique name of the interaction that asked end-users to type their e-mail which can be found on the page called '''login''')).

	For sending e-mails to a fixed person such as a researcher, therapist or healthcare professional who is managing the intervention, the e-mail address can be typed as a string (e.g. "j.smith@uni.ac.uk")		For sending e-mails to a fixed person such as a researcher, therapist or healthcare professional who is managing the intervention, the e-mail address can be typed as a string (e.g. <code>"j.smith@uni.ac.uk"</code>)

	==== Subject and e-mail content ====		==== Subject and e-mail content ====

Aco at 15:34, 26 July 2010

2010-07-26T15:34:56Z

← Older revision		Revision as of 15:34, 26 July 2010
Line 13:		Line 13:
	==== Unique Name for the e-mail and email address ====		==== Unique Name for the e-mail and email address ====

	When the e-mail name is paired with an email address, it has to be unique for every single e-mail that you want to send out. So, if you are sending the same e-mail to every end-user, you can just choose a name for that email, like ~~“welcomeemail”~~ and when it is paired with an email address, this combination will be unique.		When the e-mail name is paired with an email address, it has to be unique for every single e-mail that you want to send out. So, if you are sending the same e-mail to every end-user, you can just choose a name for that email, like "welcomeemail" and when it is paired with an email address, this combination will be unique.

	It becomes more complicated, however, if you want to send an email to a researcher, or other fixed person, relating to each end-user (e.g. if you need to send an e-mail each time an end-user finishes a session or if an e-mail needs to be sent out each time an end-user responds to an interaction in a certain way (e.g. if their responses indicate that a health condition is getting worse). This is because the researcher has a constant email address, so if three end-users all reach the same point in the intervention, meaning that three e-mails will need to be sent to the researcher, the email name and email address combination will be the same in each case.		It becomes more complicated, however, if you want to send an email to a researcher, or other fixed person, relating to each end-user (e.g. if you need to send an e-mail each time an end-user finishes a session or if an e-mail needs to be sent out each time an end-user responds to an interaction in a certain way (e.g. if their responses indicate that a health condition is getting worse). This is because the researcher has a constant email address, so if three end-users all reach the same point in the intervention, meaning that three e-mails will need to be sent to the researcher, the email name and email address combination will be the same in each case.
Line 39:		Line 39:
	For example:		For example:

	<code>~~”For~~ your chance to be entered into a prize draw for 100 pounds, please click on the link below or copy and paste it into the address line of your internet browser.\n http://www.virusdefence.org.uk/login \n Thank you.”</code>		<code>"For your chance to be entered into a prize draw for 100 pounds, please click on the link below or copy and paste it into the address line of your internet browser.\n http://www.virusdefence.org.uk/login \n Thank you."</code>

	The e-mail text will be presented as plain text which means you cannot use bold, underline or italic text and cannot change the size or font type. Also, some symbols cannot be included into the text such as pound signs (£) or ampersands (&). At present, these symbols will need to be written as words.		The e-mail text will be presented as plain text which means you cannot use bold, underline or italic text and cannot change the size or font type. Also, some symbols cannot be included into the text such as pound signs (£) or ampersands (&). At present, these symbols will need to be written as words.
Line 64:		Line 64:
	* Show end-users the first page of the intervention which has been given the unique name login		* Show end-users the first page of the intervention which has been given the unique name login

	<code>after login if sendemail("~~welcomeemail”~~, login.uname, "Welcome to the Lifestyle Study", append ("Thank you for registering for the study\n\n", login.uname, "\n\n Please remember to chart your daily progress.\n\n If you have any questions contact the researcher"), 30) goto page1</code>		<code>after login if sendemail("welcomeemail", login.uname, "Welcome to the Lifestyle Study", append ("Thank you for registering for the study\n\n", login.uname, "\n\n Please remember to chart your daily progress.\n\n If you have any questions contact the researcher"), 30) goto page1</code>

	* This is the logic command for sending out the e-mail. Once the end-user has clicked on the button on the login page an e-mail will be sent out. This logic needs to be written on one line (or broken up using ... – see [[chapter 14]]). This second append has been used to put the person’s username into the message that is being sent out to make it more personalised. This has been taken from the text entry interaction on the login page of the intervention.		* This is the logic command for sending out the e-mail. Once the end-user has clicked on the button on the login page an e-mail will be sent out. This logic needs to be written on one line (or broken up using ... – see [[chapter 14]]). This second append has been used to put the person’s username into the message that is being sent out to make it more personalised. This has been taken from the text entry interaction on the login page of the intervention.

Aco at 13:28, 26 July 2010

2010-07-26T13:28:58Z

← Older revision		Revision as of 13:28, 26 July 2010
Line 139:		Line 139:

	<code>after signin if and (sendemail ("reminder1", signin.email, "Stress Less: Session 2", "This is your one week reminder for the Stress Less intervention", 600),		<code>after signin if and (sendemail ("reminder1", signin.email, "Stress Less: Session 2", "This is your one week reminder for the Stress Less intervention", 600),
	...		...</code>
	savevalue (signin.uname, "email", signin.email)) goto page1</code>
			<code>savevalue (signin.uname, "email", signin.email)) goto page1</code>

	* After the end-user has signed up to the intervention a logic command is then set up to send an e-mail to them 1 week (or 352800 seconds) after they first visited this page to remind them to go back to the intervention for the next session. The unique name for this e-mail consists of the end-user’s username appended to the string reminder1. The e-mail address is taken from an interaction on the signup page that is uniquely named email.		* After the end-user has signed up to the intervention a logic command is then set up to send an e-mail to them 1 week (or 352800 seconds) after they first visited this page to remind them to go back to the intervention for the next session. The unique name for this e-mail consists of the end-user’s username appended to the string reminder1. The e-mail address is taken from an interaction on the signup page that is uniquely named email.

Aco at 13:27, 26 July 2010

2010-07-26T13:27:28Z

← Older revision		Revision as of 13:27, 26 July 2010
Line 95:		Line 95:
	A demo accompanying this example can be found on the LifeGuide Community site entitled '''Email Example 3'''. Note that for testing purposes the time for sending the e-mail has been set to 10 minutes (600 seconds).		A demo accompanying this example can be found on the LifeGuide Community site entitled '''Email Example 3'''. Note that for testing purposes the time for sending the e-mail has been set to 10 minutes (600 seconds).

	<code>show welcome		<code>show welcome</code>

	show signin</code>		<code>show signin</code>

	* Show end-users the first page of the intervention which has been given the unique name welcome. This page consists of a link to either a signin page for new end-users to sign up for the intervention or a login page for registered end-users.		* Show end-users the first page of the intervention which has been given the unique name welcome. This page consists of a link to either a signin page for new end-users to sign up for the intervention or a login page for registered end-users.
Line 106:		Line 106:
	* This logic would be written all on one line or can be broken up into two lines using …		* This logic would be written all on one line or can be broken up into two lines using …

	<code>show page1		<code>show page1</code>

	show page2		<code>show page2</code>

	show page3</code>		<code>show page3</code>

	* These pages represent the first session (of course one session is likely to be much longer than this).		* These pages represent the first session (of course one session is likely to be much longer than this).
Line 118:		Line 118:
	* This is the last page of the session that encourages end-users to close the site and work on their goals for the week. Alternatively, users have a chance to skip straight to session 2 by clicking on a jump button that takes them to the '''sess2p1''' page.		* This is the last page of the session that encourages end-users to close the site and work on their goals for the week. Alternatively, users have a chance to skip straight to session 2 by clicking on a jump button that takes them to the '''sess2p1''' page.

	<code>show login		<code>show login</code>

	show sess2p1</code>		<code>show sess2p1</code>

	* If end-users select the login button on the '''welcome''' page they will go straight to the '''login''' page. Once logged in they will then go to '''sess2p1'''.		* If end-users select the login button on the '''welcome''' page they will go straight to the '''login''' page. Once logged in they will then go to '''sess2p1'''.

	<code>after sess2p1 if cancelemail ("reminder", login.email2) goto sess2p2		<code>after sess2p1 if cancelemail ("reminder", login.email2) goto sess2p2</code>

	show sess2p2</code>		<code>show sess2p2</code>

	* If an end-user visits the '''sess2p1''' page before the time specified on the sendemail command, then the e-mail will be automatically cancelled. This is the logic for cancelling the e-mail (again, this should be written on one line). The unique e-mail name is the same as the unique name in the sendemail command above and the e-mail address is taken from the interaction on the '''signin''' page.		* If an end-user visits the '''sess2p1''' page before the time specified on the sendemail command, then the e-mail will be automatically cancelled. This is the logic for cancelling the e-mail (again, this should be written on one line). The unique e-mail name is the same as the unique name in the sendemail command above and the e-mail address is taken from the interaction on the '''signin''' page.
Line 132:		Line 132:

	==== Example 4: Cancelling e-mails when the e-mail address needs to be taken from an earlier session of the intervention ====		==== Example 4: Cancelling e-mails when the e-mail address needs to be taken from an earlier session of the intervention ====
	<code>show welcome		<code>show welcome</code>

	show signin</code>		<code>show signin</code>

	* Show end-users the first page of the intervention which has been given the unique name '''welcome'''. This page consists of a link to either a '''signin''' page for new users to sign up for the intervention or a '''login''' page for registered users.		* Show end-users the first page of the intervention which has been given the unique name '''welcome'''. This page consists of a link to either a '''signin''' page for new users to sign up for the intervention or a '''login''' page for registered users.
Line 145:		Line 145:
	* Here the savevalue command is used to save the e-mail address of the end-user against their username so that the e-mail address can be loaded in subsequent places in the logic.		* Here the savevalue command is used to save the e-mail address of the end-user against their username so that the e-mail address can be loaded in subsequent places in the logic.

	<code>show page1		<code>show page1</code>

	show page2		<code>show page2</code>

	show page3</code>		<code>show page3</code>

	* These pages represent the first session (of course one session is likely to be much longer than this).		* These pages represent the first session (of course one session is likely to be much longer than this).
Line 157:		Line 157:
	* This is the last page of the session that encourages end-users to close the site and work on their goals for the week. Alternatively, users have a chance to skip straight to session 2 by clicking on a jump button that takes them to the sess2p1 page.		* This is the last page of the session that encourages end-users to close the site and work on their goals for the week. Alternatively, users have a chance to skip straight to session 2 by clicking on a jump button that takes them to the sess2p1 page.

	<code>show login		<code>show login</code>

	show sess2p1</code>		<code>show sess2p1</code>

	* If end-users select the login button on the welcome page they will go straight to the login page. Once logged in they will then go to sess2p1.		* If end-users select the login button on the welcome page they will go straight to the login page. Once logged in they will then go to sess2p1.

	<code>after sess2p1 if cancelemail ("reminder", loadvalue (signin.uname, "email")) goto sess2p2		<code>after sess2p1 if cancelemail ("reminder", loadvalue (signin.uname, "email")) goto sess2p2</code>

	show sess2p2</code>		<code>show sess2p2</code>

	* If an end-user visits the sess2p1 page before the time specified on the sendemail command then the e-mail will be automatically cancelled. This is the logic for cancelling the e-mail (again, this should be written on one line). The unique e-mail name is the same as the unique name in the sendemail command above, and the e-mail address is loaded from the information that has been saved as email which was taken from the interaction on the signin page.		* If an end-user visits the sess2p1 page before the time specified on the sendemail command then the e-mail will be automatically cancelled. This is the logic for cancelling the e-mail (again, this should be written on one line). The unique e-mail name is the same as the unique name in the sendemail command above, and the e-mail address is loaded from the information that has been saved as email which was taken from the interaction on the signin page.

Aco at 13:24, 26 July 2010

2010-07-26T13:24:31Z

Show changes

Aco at 13:09, 26 July 2010

2010-07-26T13:09:48Z

Show changes

Aco: New page: == Chapter 17: Sending e-mails == === How to automatically send an e-mail to your end-user or to yourself === ==== The formula for sending e-mails ==== To send an automated e-mail, the sa...

2010-07-26T09:33:20Z

New page: == Chapter 17: Sending e-mails == === How to automatically send an e-mail to your end-user or to yourself === ==== The formula for sending e-mails ==== To send an automated e-mail, the sa...

New page

== Chapter 17: Sending e-mails ==
=== How to automatically send an e-mail to your end-user or to yourself ===
==== The formula for sending e-mails ====

To send an automated e-mail, the same set of logic commands are used. The logic uses the command sendemail followed by a unique e-mail name, e-mail address, subject heading, e-mail content, and details of when you want the e-mail to be sent out (in that order).

Written Example of Logic:
after pagename1 if sendemail(unique name for e-mail, e-mail address, "Subject message for e-mail", "E-mail content”, number in seconds indicating how long after the end-user views pagename1 that you want the e-mail sent out) goto pagename2

Below is a break-down of each part of this logic:

Unique Name for the e-mail and email address

When the e-mail name is paired with an email address, it has to be unique for every single e-mail that you want to send out. So, if you are sending the same e-mail to every end-user, you can just choose a name for that email, like “welcomeemail” and when it is paired with an email address, this combination will be unique.

It becomes more complicated, however, if you want to send an email to a researcher, or other fixed person, relating to each end-user (e.g. if you need to send an e-mail each time an end-user finishes a session or if an e-mail needs to be sent out each time an end-user responds to an interaction in a certain way (e.g. if their responses indicate that a health condition is getting worse). This is because the researcher has a constant email address, so if three end-users all reach the same point in the intervention, meaning that three e-mails will need to be sent to the researcher, the email name and email address combination will be the same in each case.

The best way get around this problem is to use the append command to attach the end-user’s username onto the unique name you have given to the e-mail message. You will then have a unique name for that e-mail.

So, in the example below, the username that the end-user provided on the login page of the intervention has been appended to the string “sessionfinish” to create a unique name for each of these emails that are sent out.

append (login.uname, "sessionfinish")

E-mail address

The e-mail address then needs to come next in the logic.

When sending e-mails to end-users, the e-mail address will be different for each person. The e-mail address will probably come from a previous interaction in the intervention. Therefore putting the page name and interaction name in this section of the logic will mean that this is the e-mail address that will be used (e.g. login.email (where email is the unique name of the interaction that asked end-users to type their e-mail which can be found on the page called login)).

For sending e-mails to a fixed person such as a researcher, therapist or healthcare professional who is managing the intervention, the e-mail address can be typed as a string (e.g. "j.smith@uni.ac.uk")

Subject and e-mail content

These are the next two parts of the e-mail logic. Both need to be written as strings so will need to have quotation marks.

When writing the e-mail content you will need to use the phrase \n to put text onto a new line.

For example:

”For your chance to be entered into a prize draw for 100 pounds, please click on the link below or copy and paste it into the address line of your internet browser.\n http://www.virusdefence.org.uk/login \n Thank you.”

The e-mail text will be presented as plain text which means you cannot use bold, underline or italic text and cannot change the size or font type. Also, some symbols cannot be included into the text such as pound signs (£) or ampersands (&). At present, these symbols will need to be written as words.

Using end-user’s details in the e-mail content
You can also include tailored feedback within the content of the e-mail using the append command. For example, the person’s username can be taken from the text entry interaction where they first entered it to put in the email content, by simply writing the page.interaction name into the logic (see example 1 below). Similarly, information from any text entry or numeric value interaction can be incorporated into e-mail content in the same way.

If you want to add scores that have been calculated from the interactions or responses to single/multiple choice interactions you will need to use the set function (see chapter 19).
When you want the e-mail to be sent out

The final part of the logic command refers to when you want the e-mail to be sent out. This number needs to be in seconds and relates to how long after the end-user has viewed the page mentioned before it that it should be sent. So if you want the e-mail to be sent after 24 hours this will be 86400 seconds.

Because of this time element, you can have a number of e-mails stored up after the end-user has visited the page. This is especially useful if you want to send out automated reminders to users throughout the course of using the intervention.

The rest of this chapter provides two examples of logic for sending out automated e-mails; the first involves sending e-mails out to end-users and the second for sending e-mails out to a researcher (or other fixed person).