Impact Stack generates a number of different kinds of emails to make your actions work.
- Email to Target: Emails matched to a target and sent as part of your campaign. You set these up on the Target and Message steps when you create an email to target action - more details here.
- Transactional emails: these are generated by the system to confirm that a form has been submitted, including a thank you email, a confirmation (double opt in) email, or a notification, when a supporter completes the action. You set these up on the Email step when you create your action - more details below.
- System Emails: Impact Stack also sends out system emails, for example when users want to change their passwords. You can control these by accessing Manage > Advanced settings > Site settings > Account settings. For more information, contact support.
Setting up your transactional emails
All actions on Impact Stack have an email step in their wizard with the following options:
- Confirmation email Enable this if you’d like to add a confirmation step before completing the action. This means that supporters receive a confirmation link after submitting your form. By clicking on the link, they confirm their email address and the form entry is valid, before an email is sent to a target, or a petition signature is counted. The confirmation link is unique to each supporter and is added to the email body as a link via the token
[submission:confirm_url]. You can also use
[submission:confirm_url:raw]to get the raw URL that you can add to a link that you create yourself.
- Thank You email This email is sent to your supporter after a successful submission of your form.
- Notification email Enable this if you would like to receive a notification that someone submitted your form.
These three emails are configured in the same way.
Field: "E-mail from address"
When we set up your Impact Stack, we’ll have set up a default ‘sender’ email address for you, using the subdomain that points to our servers, and set it up to forward to an email box that you provided.
You can't specify a custom 'From:' email address because it’s important that emails sent from our server use a domain it’s authorised to use, such as your subdomain. If emails were sent ‘from’ Yourname@yourorganisation.org they’d risk being classed as spam. More on email deliverability and our compliance with DMARC.
You can however specify a custom Reply-To: address. This will be used if the supporter tries to reply to the transactional email.
Field: "E-mail from name"
This is the name that will appear as sender. While choosing custom, you can specify the name that accompanies the email. Again, the default sending name was defined during your onboarding.
Set a subject for your email. As always keep it simple and meaningful eg "Thank you for taking action!" or "Please confirm your email address".
Personalise the email content with tokens
Your email body content can include tokens to allow you to personalise the message - the default content will offer some examples.
The complete list of tokens is available under the email text field, just click on the "Browse available tokens" orange text and a pop-up box will open.
- [submission:values:first_name] --> will show the supporter first name
- [submission:values:last_name] --> will show the supporter last name
- [node:title] --> will show the title of your action
- [submission:url] --> will show the URL where the supporter took the action
- [submission:confirm_url:raw] --> the raw URL to the confirmation page that you can add into an anchor (<a>) tag
- [submission:date] --> will show the date of the supporter's webform submission
- [submission:email-to-target-messages] → on an email to target action, will add the copy of all messages the supporter has sent to the target or targets.
In general, if you insert [submission:values:form_key] and put in the key of a webform field instead of the text form_key it will pull out whatever information was inserted there. An explanation on how to find the form key of a particular web form field can be found here.
[submission:confirm_url] --> will show the correct link to confirm submission in the double-opt-in e-mail.
NOTE: If you edit the confirmation email, take care not to delete the [submission:confirm_url] token, as it will provide the link to confirm the email address. Without it, the action cannot be completed.
If the value you want is in a fieldset use the form [submission:values:fieldset_key:form_key].
NOTE: If your form does not have a field with the form key referred to in your token, or the supporter has left that field blank, the token will have no value and the email will simply show an extra blank space. Make sure you take this into account in your email wording.
Send e-mail as HTML
You can choose to send your transactional emails as plain text, or html, allowing colours, font sizes and images. Bear in mind that different email clients will render your email very differently, so it’s a good idea to keep your thank you emails very simple. Find out how to add images to your thank you emails here and how to add share links to your thank you emails here.