A popular app to send triggered email is Mandrill. Install the Mandrill app and open a Mandrill account.
Before you start defining when and to whom to send the triggered email to there are a few settings needed.
Mandrill setting is only done once per bucket. If it’s already set you don’t need to follow the setting-instruction. Jump directly to “Create new item”.
Go to the mandrill app under tab “settings” and add the mandrill login key. This key can be found in your Mandrill account under “Settings – API Keys”.
*The 2 other fields (“API version” and “API URL”) should be left as they are.
- Create new item
When the setting has been done, go to the tab “Rules” and click on “Create new item”.
There are three below options.
- Starter: It’s the option to define what action (event) to trigger the email.
- Advanced starter: is the same as “starter” but with an advanced option to allow you writing your own HTML DOM for cases such as sending a list of products dynamically which might be difficult to do directly in Mandrill. This option is often used for a product list in abandon cart emails.
- Stopper: as Mandrill is sending transactional emails based on triggered events, there are occasions you would want to delay the email after your user´s action has taken place. The delay may be a couple of days after your user has visited and left your website. The delay might be a couple of hours after a user has abandoned the shopping cart and not coming back and completed the purchase. In those occasions, it is important to define an action (event) to stop the email. In many cases, a purchase is such an action you would want to stop a retargeting email to be sent. A stopper is optional to use. Each stopper rule can only be assigned to one starter rule.
Get started with Mandrill - Starter
Define what action (event) to trigger the email.
Select the trigger-event by open the list of events under “Subscribe to event of type”. This option defines what event the email should be triggered on. The event list shows all available events that are stored in profile cloud. If you cannot find your event, check if “save to profile” is enabled.
- Mandrill template ID
For each template that is created in your Mandrill account, a unique ID is created. This ID is called “Template Slug” and is created and visible in the template settings (in your Mandrill account). Add the template slug here to activate the right template.
- Send timeout
Add the eventual delay (in seconds) of sending an email. The time starts ticking from the moment the event has triggered. In below screenshot, the mail will be sent 5 hours after the event has triggered if a “stopper” has not been sent before that.
Set the information to be sent to Mandrill
When the trigger-event has been selected, the data that should be used by Mandrill is to be defined. The only optional data that has to be sent to Mandrill is an email address. On the left-hand side, all elements are data from P.C. This column of elements is different depending on the event that has been selected. The trigger-event might contain data. If it does, the data from the event can be utilized here. Other data available are attributes and session data stored in P.C.
On the right-hand side is the placeholder for data to be used in Mandrill. Connect the data elements from P.C. to the correspondent element in Mandrill.
Create new data elements for mandrill to receive by click in “Add new var”
Give the element a descriptive name and click “OK”
Connect the data from the event in P.C. to the newly created placeholder.
It is also possible to connect data from attributes and session data.
Note: If attributes are to be used, make sure that the event that triggers the rule is defined in a way that the stored data is always available when the event is triggered.
Save the rule.
To use dynamic values sent by P.C. in Mandrill, use this format in the HTML editor *|variable name|*. Read more about how to set up the email template in Mandrill here http://help.mandrill.com/home
Below is an example of how to use the P.C. dynamic values in Mandrill