Send out a different series of messages to openers

How do I send out a different series of messages to contacts who opened the first message in a sales autoresponder series?

There are many reasons why you might want to send out a different message series to someone based on their actions. These include:

Improving the chance of a sale
Sending a reader to a more focused page in a funnel
To increase engagement
To help with email delivery

… and many more.

Here is a typical scenario:

You have an autoresponder set up to send out a series of messages offering a specific product.

You want to send a different set of messages that have different information to those that will open the first message (maybe to tell them about one of the other benefits of your product or service), while those who don’t open the first message will continue getting the original series of messages.

This is how to do it:

1. Set up the two autoresponders (See How to set up an autoresponder)

Tip! Set up your first autoresponder and test it. Then, to save time, choose ‘Copy then edit’ to create your second autoresponder.

Add the basic messages into the first autoresponder. Then add the other set of messages you want people (who will open the first message in the first autoresponder) to get into the second autoresponder.

2. Set up a couple of actions for the automation to happen (See How to create an action)

When creating an action, there is an ‘Event’ option for ‘Follow-up message open’:

how do i set up an action event

… which you need to use for the automation to occur. So, just set up the following actions:

Action 1 – Add To/Move
— Event: Follow-up message open
— Any of these: First message of the first autoresponder ticked/chosen
— Action: Add subscription
— Autoresponder: Second autoresponder chosen (then set the rest of the subscription details accordingly)

how do i set an action

Action 2 – Drop/Delete
— Event: Follow-up message open
— Any of these: First message of the first autoresponder ticked/chosen
— Action: Drop/delete subscriptions
— Drop/delete from these autoresponders: First autoresponder ticked/chosen

how do I drop a subscription action

For Action 2, you have the option to either delete or drop the original subscription (to the first autoresponder) once the first message (of the first autoresponder) is opened. We suggest you use the drop option, just so you’ll have a record of the original subscription in case you need to filter them out in the future, rather than delete the entire subscription record for the original subscription from the system altogether.

Tip! To make sure that things are going to be working out the way you want them to, we always suggest to our users that they add a test/dummy contact in the system using one of their valid email addresses, then test everything using that dummy contact and make the adjustments needed before going live.

So, for this example, once the trigger (opening of the first message in the first autoresponder) occurs, what would happen will look like this:

In case you want to add another action that will be triggered when the first message is opened, simply add the action and test again.

How Do I… ?

In this section, you will find answers to some of the common questions about using our autoresponder software.

Some of the questions we answer cover some of the basics, while some cover advanced topics that email marketers need to know to improve conversions and ROI and generally use our software more effectively.

Here is a list of the questions and topics available:

How do I avail of the free installation?

How do I warm up my IP address?

How do I organize my contacts?

How do I add images to messages?

How do I add videos to messages?

How do I send out a different series of messages to openers?

How do I remove unsubscribers from an autoresponder?

How do I remove failed subscriptions from an autoresponder?

How do I track the source of clicks?

How do I customize user-facing pages?

How do I manage multiple websites in one arpReach system?

How do I move arpReach to HTTPS?

How do I remove a registered domain?

How do I extend the login duration?

How do I use Zapier with arpReach?

 

Bulk Update of Contacts

From arpReach 1.8.001 and #V2.0.8, contacts can be updated in bulk using the Trigger Action For Matching Contacts feature.

To access the feature, choose Trigger Action for matching contacts from the I want to… drop-down menu on the Contacts list screen.

Using this feature, you are able to do the following to multiple/all contacts at the same time:

  • Add/remove a tag/category
  • Add to/remove from the suppression list
  • Add a new subscription to specific autoresponders
  • Drop/delete a subscription or all subscriptions
  • Setup custom field values
  • Send the contacts data via HTTP post to a specified URL (this would allow you to export bulk contacts into a third party software)
  • Run a user function (#V2-exclusive feature)

Reminder: When your contacts list has no filter/segment in place (i.e., the Filter drop-down menu is set to [No filter]), the “triggered action” will affect ALL your contacts. Be very mindful of the filter settings before proceeding, as you cannot remove a “triggered action” that’s been scheduled or undo a “triggered action” once it’s been processed.

Creating the action to trigger

If you want to add a category, work with the suppression list, add an autoresponder subscription (and so on) in bulk, you need to have the appropriate action for it.

To avoid confusion, you can create actions that will be used specifically for this feature and label it strategically. The Event setting doesn’t matter, but it is recommended to select an option that you do not normally use (e.g., Remote call) so it doesn’t get triggered unintentionally. For example:

See Actions and Events for instructions on how to create an action.

If you want to send contacts data via an HTTP request, you have to create an action with the desired URL and POST/GET method.

Setting the target contacts

A triggered action will be applied to all contacts that match the filter in place when it was scheduled.

You can apply any of your segments or use any of the predefined filters on the Filter drop-down menu on the Contacts list screen.

To apply an action to an existing segment, use the In segment filter. See Segmenting Contacts for instructions on how to create a segment.

Reminder: Again, when your contacts list has no filter/segment in place (i.e., the Filter drop-down menu is set to [No filter]), the “triggered action” will affect ALL your contacts. Be very mindful of the filter settings before proceeding, as you cannot remove a “triggered action” that’s been scheduled or undo a “triggered action” once it’s been processed.

Once your desired filter is in place, you may now choose Trigger Action for matching contacts from the I want to… drop-down menu.

Scheduling the action to trigger

On the Trigger Actions For Matching Contacts page, you can see the filter applied and the number of matching contacts.

This feature doesn’t create new actions but rather schedules existing ones, which will be applied to the matching contacts at the time it was triggered/scheduled.

The Choose actions to apply checklist contains your existing, enabled actions.

Select the action/s to apply to the current matching contacts by clicking in the appropriate checkbox/es.

Once selected, click the Trigger Action button.

The scheduled actions on the queue will be processed during the next run of the arpReach script.

Important note: You can choose to trigger multiple actions in just one schedule (i.e. selecting multiple actions from the Choose actions to apply checklist), but the order of the actions that will be applied is not guaranteed.

If the order of the actions does matter, schedule the actions separately — one at a time. In this case, the actions will be applied in the order they were scheduled (i.e., the first action scheduled will be applied first, then the second action scheduled, then the third action scheduled, etc.).

Bounce Codes

When the software sends an email and that email bounces, a bounce code is generated and recorded in the contact’s record.

The four digit software bounce code number is assigned based on the answer to two pieces of information.  Understanding a little about the information being used will help you make better choices or locate the cause of delivery issues.

QuickSearch Tip: If you know the bounce code number and you want to know what caused it press (Ctrl + F) or Find – and search for the number but add a zero (0) in front of it.

Email Bounce Basics

There are two types of bounces:

  • hard bounces
  • soft bounces

What is a Hard Bounce?

A hard bounce generally means that there is no point in trying to send email to that address because the reason for the bounce is unlikely to be resolved. Examples include non-existent mailboxes or domains. When the software receives a hard bounce, that contact’s subscriptions are immediately flagged as “failed”.  The software will not try to send email again to a contact who is flagged as failed.

What is a Soft Bounce?

A soft bounce generally means that the issue could be resolved in future so follow-up messages will be retried several times. Multiple soft bounces in an autoresponder sequence will eventually result in a contact’s subscription being flagged as “failed” and no more follow-up messages will be sent for that subscription.

How do I tell?  How do I check?

Understanding the basic process of what an email bounce message/code is and does will help.

An automated message gets sent back to the server that sent the email that could not be delivered.  That message has numbers and messages which generally conform to a set of rules.

The rules are called The RFC code.

Hard bounces have a 3 digit number beginning with a 5 and soft bounce messages have a three digit number beginning with a 4.  Although you should be aware that some ISPs are not consistent some of the time.  This is outside of your control and ours.

The bounce message element.

There are also guidelines for the message element that should be attached to the 4XX number and explains why that email to that contact is being rejected.  It would be good if there was consistency in the explanations and links that get sent back and stored in your mail log files.  Unfortunately there isn’t a lot of consistency and that is outside of your control and ours as well.

What is the bounce code number?

There are many common messages used by ISP’s to say the same thing.  i.e. User does not exist.  Some ISP’s try to have helpful messages.  i.e. user unknown please contact systems admin

If the bounce message the software gets is a properly formatted 5XX response it marks that contact as failed.  Hard bounce.  The software then assigns a bounce code number based on scanning the content in the message element for expected language or terms etc as the most likely reason for the failure.

The following represents a technical explanation of the codes that the software generates for trigger strings in bounced emails.   These can be used as a lookup for the bounce codes shown in a contact’s records in the software.

Top Search Tip:  Type CTRL + F to bring up the browser search tool then type in 00 (zero zero) + the bounce number you are looking for to find it quickly.

‘trigger’ => “/no such address here/i” 
‘code’ => ‘0001’ 
‘is_hard’ => 1
‘trigger’ => “/user doesn’t have.*account/is” 
‘code’ => ‘0002’ 
‘is_hard’ => 1
‘trigger’ => “/user unknown/i”
‘code’ => ‘0003’ 
‘is_hard’ => 1
‘trigger’ => “/no mailbox/i” 
‘code’ => ‘0004’ 
‘is_hard’ => 1
‘trigger’ => “/can’t find.*mailbox/is” 
‘code’ => ‘0005’ 
‘is_hard’ => 1
‘trigger’ => “/=D5=CA=BA=C5=B2=BB=B4=E6=D4=DA/i” 
‘code’ => ‘0006’ 
‘is_hard’ => 1
‘trigger’ => “/Unrouteable address/i”
‘code’ => ‘0007’
‘is_hard’ => 1
‘trigger’ => “/delivery[^\n\r]+failed/i” 
‘code’ => ‘0008’ 
‘is_hard’ => 1
‘trigger’ => “/unknown local-part/i” 
‘code’ => ‘0009’ 
‘is_hard’ => 1
‘trigger’ => “/Invalid.*(?:alias|account|recipient|address|email|mailbox|user)/is” 
‘code’ => ‘0010’ 
‘is_hard’ => 1
‘trigger’ => “/No such.*(?:alias|account|recipient|address|email|mailbox|user)/is” 
‘code’ => ‘0011’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*no.*accept.*mail>/is” 
‘code’ => ‘0012’ 
‘is_hard’ => 1
‘trigger’ => “/over.*quota/is” 
‘code’ => ‘0013’ 
‘is_hard’ => 0
‘trigger’ => “/quota exceeded/i” 
‘code’ => ‘0014’ 
‘is_hard’ => 0
‘trigger’ => “/mailbox.*full/is” 
‘code’ => ‘0015’ 
‘is_hard’ => 0
‘trigger’ => “/The message to.*bounce.*Quota exceed/is” 
‘code’ => ‘0016’ 
‘is_hard’ => 0
‘trigger’ => “/user is inactive/i” 
‘code’ => ‘0017’ 
‘is_hard’ => 1
‘trigger’ => “/inactive account/i” 
‘code’ => ‘0018’ 
‘is_hard’ => 1
‘trigger’ => “/input\/output error/i” 
‘code’ => ‘0019’ 
‘is_hard’ => 1
‘trigger’ => “/not open new email file/i” 
‘code’ => ‘0020’ 
‘is_hard’ => 1
‘trigger’ => “/Resources temporarily unavailable/i” 
‘code’ => ‘0021’ 
‘is_hard’ => 0
‘trigger’ => “/does not accept.*non-Western/is” 
‘code’ => ‘0022’ 
‘is_hard’ => 0
‘trigger’ => “/quota exceed/i” 
‘code’ => ‘0023’ 
‘is_hard’ => 0
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*full/is” 
‘code’ => ‘0024’ 
‘is_hard’ => 0
‘trigger’ => “/Insufficient system storage/i” 
‘code’ => ‘0025’ 
‘is_hard’ => 0
‘trigger’ => “/File.*too large/is” 
‘code’ => ‘0026’ 
‘is_hard’ => 0
‘trigger’ => “/larger than.*limit/is” 
‘code’ => ‘0027’ 
‘is_hard’ => 0
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*not.*list/is” 
‘code’ => ‘0028’ 
‘is_hard’ => 1
‘trigger’ => “/user path no exist/i” 
‘code’ => ‘0029’ 
‘is_hard’ => 1
‘trigger’ => “/Relay.*(?:denied|prohibited)/is” 
‘code’ => ‘0030’ 
‘is_hard’ => 1
‘trigger’ => “/no.*valid.*(?:alias|account|recipient|address|email|mailbox|user)/is”
‘code’ => ‘0031’ 
‘is_hard’ => 1
‘trigger’ => “/Invalid.*(?:alias|account|recipient|address|email|mailbox|user)/is” 
‘code’ => ‘0032’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*(?:disabl ed|discontinued)/is” 
‘code’ => ‘0033’ 
‘is_hard’ => 1
‘trigger’ => “/user doesn’t have.*account/is” 
‘code’ => ‘0034’ 
‘is_hard’ => 1
‘trigger’ => “/(?:unknown|illegal).*(?:alias|account|recipient|address|email|mai lbox|user)/is” 
‘code’ => ‘0035’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*(?:un|n ot\s+)available/is” 
‘code’ => ‘0036’ 
‘is_hard’ => 1
‘trigger’ => “/no (?:alias|account|recipient|address|email|mailbox|user)/i” 
‘code’ => ‘0037’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*unknown/is” 
‘code’ => ‘0038’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*disabled/is” 
‘code’ => ‘0039’ 
‘is_hard’ => 1
‘trigger’ => “/No such (?:alias|account|recipient|address|email|mailbox|user)/i” 
‘code’ => ‘0040’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*not found/is” 
‘code’ => ‘0041’ 
‘is_hard’ => 1
‘trigger’ => “/deactivated (?:alias|account|recipient|address|email|mailbox|user)/i” 
‘code’ => ‘0042’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*reject/is” 
‘code’ => ‘0043’ 
‘is_hard’ => 1
‘trigger’ => “/bounce.*administrator/is” 
‘code’ => ‘0044’ 
‘is_hard’ => 1
‘trigger’ => “/<.*>.*disabled/is” 
‘code’ => ‘0045’ 
‘is_hard’ => 1
‘trigger’ => “/not our customer/i” 
‘code’ => ‘0046’ 
‘is_hard’ => 1
‘trigger’ => “/Wrong (?:alias|account|recipient|address|email|mailbox|user)/i” 
‘code’ => ‘0047’ 
‘is_hard’ => 1
‘trigger’ => “/(?:unknown|bad).*(?:alias|account|recipient|address|email|mailbox|user)/is” 
‘code’ => ‘0048’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*not OK/is” 
‘code’ => ‘0049’ 
‘is_hard’ => 1
‘trigger’ => “/Access.*Denied/is” 
‘code’ => ‘0050’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*lookup.*fail/is”
‘code’ => ‘0051’ 
‘is_hard’ => 1
‘trigger’ => “/(?:recipient|address|email|mailbox|user).*not.*member of domain/is” 
‘code’ => ‘0052’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*cannot be verified/is” 
‘code’ => ‘0053’ 
‘is_hard’ => 1
‘trigger’ => “/Unable to relay/i” 
‘code’ => ‘0054’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*(?:n’t|n ot) exist/is” 
‘code’ => ‘0055’ 
‘is_hard’ => 1
‘trigger’ => “/not have an account/i” 
‘code’ => ‘0056’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*is not allowed/is” 
‘code’ => ‘0057’ 
‘is_hard’ => 1
‘trigger’ => “/inactive.*(?:alias|account|recipient|address|email|mailbox|user)/is” 
‘code’ => ‘0058’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*Inactive/is” 
‘code’ => ‘0059’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user) closed due to inactivity/i” 
‘code’ => ‘0060’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user) not activated/i” 
‘code’ => ‘0061’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*(?:suspen d|expire)/is” 
‘code’ => ‘0062’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*no longer exist/is” 
‘code’ => ‘0063’ 
‘is_hard’ => 1
‘trigger’ => “/(?:forgery|abuse)/i” 
‘code’ => ‘0064’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*restrict/is” 
‘code’ => ‘0065’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*locked/is” 
‘code’ => ‘0066’ 
‘is_hard’ => 1
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user) refused/i” 
‘code’ => ‘0067’ 
‘is_hard’ => 1
‘trigger’ => “/sender.*not.*domain/is” 
‘code’ => ‘0068’ 
‘is_hard’ => 1
‘trigger’ => “/Message refused/i” 
‘code’ => ‘0069’ 
‘is_hard’ => 1
‘trigger’ => “/No permit/i” 
‘code’ => ‘0070’ 
‘is_hard’ => 1
‘trigger’ => “/domain isn’t in.*allowed rcpthost/is” 
‘code’ => ‘0071’ 
‘is_hard’ => 1
‘trigger’ => “/AUTH FAILED/i” 
‘code’ => ‘0072’ 
‘is_hard’ => 1
‘trigger’ => “/relay.*not.*(?:permit|allow)/is” 
‘code’ => ‘0073’ 
‘is_hard’ => 1
‘trigger’ => “/not local host/i” 
‘code’ => ‘0074’ 
‘is_hard’ => 1
‘trigger’ => “/Unauthorized relay/i” 
‘code’ => ‘0075’ 
‘is_hard’ => 1
‘trigger’ => “/Transaction.*fail/is” 
‘code’ => ‘0076’ 
‘is_hard’ => 1
‘trigger’ => “/Invalid data/i” 
‘code’ => ‘0077’ 
‘is_hard’ => 1
‘trigger’ => “/Local user only/i” 
‘code’ => ‘0078’ 
‘is_hard’ => 1
‘trigger’ => “/not.*permit.*to/is” 
‘code’ => ‘0079’ 
‘is_hard’ => 1
‘trigger’ => “/Content reject/i” 
‘code’ => ‘0080’ 
‘is_hard’ => 0
‘trigger’ => “/MIME\/REJECT/i” 
‘code’ => ‘0081’ 
‘is_hard’ => 0
‘trigger’ => “/MIME error/i” 
‘code’ => ‘0082’ 
‘is_hard’ => 0
‘trigger’ => “/Mail data refused.*AISP/is” 
‘code’ => ‘0083’ 
‘is_hard’ => 0
‘trigger’ => “/Host unknown/i” 
‘code’ => ‘0084’ 
‘is_hard’ => 1
‘trigger’ => “/Specified domain.*not.*allow/is” 
‘code’ => ‘0085’ 
‘is_hard’ => 1
‘trigger’ => “/No route to host/i” 
‘code’ => ‘0086’ 
‘is_hard’ => 1
‘trigger’ => “/unrouteable address/i” 
‘code’ => ‘0087’ 
‘is_hard’ => 1
‘trigger’ => “/System.*busy/is” 
‘code’ => ‘0088’ 
‘is_hard’ => 0
‘trigger’ => “/Resources temporarily unavailable/i” 
‘code’ => ‘0089’ 
‘is_hard’ => 0
‘trigger’ => “/sender is rejected/i” 
‘code’ => ‘0090’ 
‘is_hard’ => 0
‘trigger’ => “/Client host rejected/i” 
‘code’ => ‘0091’ 
‘is_hard’ => 0
‘trigger’ => “/MAIL FROM.*mismatches client IP/is” 
‘code’ => ‘0092’ 
‘is_hard’ => 0
‘trigger’ => “/denyip/i” 
‘code’ => ‘0093’ 
‘is_hard’ => 0
‘trigger’ => “/client host.*blocked/is” 
‘code’ => ‘0094’ 
‘is_hard’ => 0
‘trigger’ => “/mail.*reject/is” 
‘code’ => ‘0095’ 
‘is_hard’ => 0
‘trigger’ => “/spam.*detect/is” 
‘code’ => ‘0096’ 
‘is_hard’ => 0
‘trigger’ => “/reject.*spam/is” 
‘code’ => ‘0097’ 
‘is_hard’ => 0
‘trigger’ => “/SpamTrap/i” 
‘code’ => ‘0098’ 
‘is_hard’ =>
‘trigger’ => “/Verify mailfrom failed/i” 
‘code’ => ‘0099’ 
‘is_hard’ => 0
‘trigger’ => “/MAIL.*FROM.*mismatch/is” 
‘code’ => ‘0100’ 
‘is_hard’ => 0
‘trigger’ => “/spam scale/i” 
‘code’ => ‘0101’ 
‘is_hard’ => 0
‘trigger’ => “/junk mail/i” 
‘code’ => ‘0102’ 
‘is_hard’ => 0
‘trigger’ => “/message filtered/i” 
‘code’ => ‘0103’ 
‘is_hard’ => 0
‘trigger’ => “/subject.*consider.*spam/is” 
‘code’ => ‘0104’ 
‘is_hard’ => 0
‘trigger’ => “/Temporary local problem/i” 
‘code’ => ‘0105’ 
‘is_hard’ => 0
‘trigger’ => “/system config error/i” 
‘code’ => ‘0106’ 
‘is_hard’ => 0
‘trigger’ => “/delivery.*suspend/is” 
‘code’ => ‘0107’ 
‘is_hard’ => 0
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*invalid/is” 
‘code’ => ‘0108’ 
‘is_hard’ => 1
‘trigger’ => “/Deferred.*No such.*(?:file|directory)/is” 
‘code’ => ‘0109’ 
‘is_hard’ => 1
‘trigger’ => “/mail receiving disabled/i” 
‘code’ => ‘0110’ 
‘is_hard’ => 1
‘trigger’ => “/bad.*(?:alias|account|recipient|address|email|mailbox|user)/is” 
‘code’ => ‘0111’ 
‘is_hard’ => 1
‘trigger’ => “/over.*quota/is” 
‘code’ => ‘0112’ 
‘is_hard’ => 0
‘trigger’ => “/quota.*exceeded/is” 
‘code’ => ‘0113’ 
‘is_hard’ => 0
‘trigger’ => “/exceed.*\n?.*quota/is” 
‘code’ => ‘0114’ 
‘is_hard’ => 0
‘trigger’ => “/(?:alias|account|recipient|address|email|mailbox|user).*full/is” 
‘code’ => ‘0115’ 
‘is_hard’ => 0
‘trigger’ => “/space.*not.*enough/is” 
‘code’ => ‘0116’ 
‘is_hard’ => 0
‘trigger’ => “/Deferred.*Connection (?:refused|reset)/is” 
‘code’ => ‘0117’ 
‘is_hard’ => 0
‘trigger’ => “/Invalid host name/i” 
‘code’ => ‘0118’ 
‘is_hard’ => 1
‘trigger’ => “/Deferred.*No route to host/is” 
‘code’ => ‘0119’ 
‘is_hard’ => 1
‘trigger’ => “/Host unknown/i” 
‘code’ => ‘0120’ 
‘is_hard’ => 1
‘trigger’ => “/Name server timeout/i” 
‘code’ => ‘0121’ 
‘is_hard’ => 1
‘trigger’ => “/Deferred.*Connection.*tim(?:e|ed).*out/is” 
‘code’ => ‘0122’ 
‘is_hard’ => 1
‘trigger’ => “/Deferred.*host name lookup failure/is” 
‘code’ => ‘0123’ 
‘is_hard’ => 1
‘trigger’ => “/MX list.*point.*back/is” 
‘code’ => ‘0124’ 
‘is_hard’ => 1
‘trigger’ => “/I\/O error/i” 
‘code’ => ‘0125’ 
‘is_hard’ => 0
‘trigger’ => “/connection.*broken/is” 
‘code’ => ‘0126’ 
‘is_hard’ => 0
‘trigger’ => “/Delivery to the following recipients failed/i” 
‘code’ => ‘0127’ 
‘is_hard’ => 0
‘trigger’ => “/User unknown/i” 
‘code’ => ‘0128’ 
‘is_hard’ => 1
‘trigger’ => “/Service unavailable/i” 
‘code’ => ‘0129’ 
‘is_hard’ => 1

What’s useful in the appendix

In this section you’ll find links to pages that can help you work out why the software might not be doing what you expect or explain what something means.

Sending emails sounds easy but it’s a complex process getting great ROI.  We hope that the appendix will help get to the root of some causes of ‘odd things’.

Posting HTTP Data

Subscription Form Codes

Bounce Codes and What Triggered It/Them

Contact Tags

Contact tags insert information for the recipient contact.

An optional default value will be inserted if the information is blank.

Important Note: The “[” and “]” (square brackets) in the contact tags define the default value element but should not be included in your email.

For example, let’s use the tag:

Hi {FIRST_NAME there},

If the contact record has the First Name as John, the message would read as:

Hi John,

If, however, the contact record does not have a First Name, then the message would read as:

Hi there,

Contact Tags

{CONTACT_ID}
{EMAIL_ADDRESS}
{REFERER_ID [default value]} 
{TITLE [default value]}
{FIRST_NAME [default value]}
{MIDDLE_NAME [default value]}
{LAST_NAME [default value]}
{FULL_NAME [default value]}
{COMPANY [default value]}
{DEPARTMENT [default value]}
{ADDRESS_1 [default value]}
{ADDRESS_2 [default value]}
{ADDRESS_3 [default value]}
{CITY [default value]}
{STATE [default value]}
{POSTAL_CODE [default value]}
{PHONE_NUMBER_1 [default value]}
{PHONE_NUMBER_2 [default value]}
{PHONE_NUMBER_3 [default value]}
{MOBILE_PHONE_NUMBER_1 [default value]}
{MOBILE_PHONE_NUMBER_2 [default value]}
{MOBILE_PHONE_NUMBER_3 [default value]}
{FAX_NUMBER_1 [default value]}
{FAX_NUMBER_2 [default value]}
{FAX_NUMBER_3 [default value]}
{ALTERNATIVE_EMAIL_ADDRESS_1 [default value]}
{ALTERNATIVE_EMAIL_ADDRESS_2 [default value]}
{ALTERNATIVE_EMAIL_ADDRESS_3 [default value]}

To insert links specific to the recipient contact:

{MANAGE_LINK}
{EDIT_LINK}

To insert custom field information for the recipient contact:

{CUSTOM_<tag> [default value]}
  • Example #1 – {CUSTOM_hat_size}
  • Example #2 – {CUSTOM_hat_size info not available}

What is Dynamic Content?

Dynamic content is content that changes based on information stored within the database.

Using dynamic content saves you time and gives you great flexibility and versatility when creating message templates or broadcast and autoresponder messages.

Your dynamic content can be automatically included in messages and subject lines by using tags (or shortcodes).

In the following pages, explanations are given where the meaning is not obvious.

  • Mandatory parameters are inside angle brackets: <>
  • Optional parameters are inside square brackets: []

Important Note: You should remove the “[” and “]” (square brackets) when using optional parameters.

Split testing autoresponder messages

Split Testing Follow-Up Messages Using Variants

Split testing is the process of sending two or more messages, as part of the same batch, to a small segment of your contacts. Each message has different content and each contact will only receive one message.

The aim of split testing is to maximize your ROI by discovering which email message performs better with a smaller segment of contacts. When you know which message has the better results (the winner) you send the winning message to the rest of your contacts.

You can split-test every follow-up message with any number of variants. This means you can test out different aspects of any message to compare their success.

How do you split-test?

First, you must create a follow-up message in your autoresponder (or broadcast message). This serves as the main or initial control message. You then create a variant of the main message which you will test against the control.

When a variant is first added to a follow-up message, it is an exact copy of the original message. It can then be tweaked to test every element of your message such as:

  • Subject line
  • Message format
  • Content
  • Layout
  • Attachments

“Some message variants will produce better results than others so you can adjust the rate at which each is sent at any time”

To create or manage the variants of a follow-up message, choose the Variants option on the Choose action… drop-down menu or click the number under the Variants column.

After doing so, the following screen appears:

To create a split-test variant, choose Add a variant to this message on the I want to… drop-down menu.

This creates a copy of the original message and opens up the message editor for the variant you have just created. (In the image below, we changed the Subject line so we can split test the variant against the original.)

Once you have made your changes, click the Save Variant button.

You will then be redirected back to the Message Variants list screen, which now shows the variant you just created.

In the image below, take a look at the Frequency column.

Simply use the slider to change the percentage of contacts that will be receiving the variant.

The system decides at random which message will be sent to each contact during the sending process.

Adding Email Campaign Messages

Each autoresponder you create can have any number of follow-up messages. arpReach will send them out over a period of time you define.

To manage an autoresponder’s messages, choose Messages from the Choose action… drop-down or click the number under the Messages column on the Autoresponders list screen.

This shows the messages list for the autoresponder. The columns of information in the messages table are:

  • Subject – the subject of the message. (Note the exclamation to the left of the headline. This indicates that you have not approved your message to be sent. Once you have tested your message, you can approve the message by clicking Approve to send on the Choose action… drop-down menu.)
  • Status – the status of the message.
  • Schedule – when this message will be sent in relation to the previous message.
  • Spam score – a guideline spam score for the plain text (T) and HTML (H) content of the message. The threshold for a message to be classed as spam is five (5), but other factors such as your IP address will also be a factor. Treat this as a guide and not a definitive answer.
  • Variants – the number of split-test variants the message has. Click the number to view the variant list. You can test an unlimited number of variants.
  • Sent – the number of unique contacts who have been sent the message. Click the number to view those contacts.
  • Opened – the number of unique contacts who have opened the message. Click the number to view those contacts.
  • Bounced – the number of unique contacts who have bounced this message at least once. Click the number to view those contacts.
  • Position – the position of the message in the sequence. This option is grayed out unless Unlock message positions is selected from the I want to… drop-down menu. When message positions are unlocked, you can drag messages up and down the list to set their order. When done, select Lock message positions from the I want to… drop-down menu.

“You can change the order of follow-up messages by dragging them into place on the message list”

Under the Actions column, you have the Choose action… drop-down menu for each message in your sequence.

Using the Choose action… menu, you can:

  • Preview – preview the message in a popup window. Your browser needs to allow pop-ups for this to work. The preview window has tabs for the plain text and HTML versions of the message.
  • Test – send yourself a test version of the message and its split-test variants.
  • Reports – graphical reports on the open and bounce rates for the message and its split-test variants.
  • Edit – edit the message settings and content.
  • Variants – add and manage the split-test variants for the message.
  • Copy/Copy then edit – create a new message by copying the message’s settings and content.
  • Delete – delete a message from the follow-up sequence.

On the With selected… menu:

… you can approve or disapprove, change the status, and delete the messages selected.

On the I want to… drop-down menu, you can:

  • Refresh the page to update send, open, and bounce counts.
  • Unlock the message positions to change their order using the Position column or dragging.
  • View the autoresponder list.
  • Add a new message to the follow-up sequence.
  • Import messages from another autoresponder in your system.
  • Edit the autoresponder’s settings.
  • Delete all the messages in the autoresponder’s follow-up sequence.
Tip! To maximize your return on investment, you can and should split test every message you send.

Add your first message into an autoresponder

Using the I want to… menu, select Add a message to this autoresponder.

When adding or editing a follow-up message, the settings are the same.

The Add Follow-Up Message screen is split up into three tabs for easy management, which are:

  1. Settings
  2. Message
  3. RSS Feed

The Settings Tab

The Settings tab has three sections: When to send, Day, time and duplicate restrictions, and Tracking and reporting.

When to send Section

  • Status – the status of the message. The options are:
    — Live – the message is live and being sent as required. You will need to make your messages live when you are ready to send them.
    — Inactive and skip (default) – the message is not live and subscribers reaching this point will jump over it and continue.
    — Inactive and block – the message is not live and subscribers reaching this point will stop and not receive any more messages.
  • When to send – this is where you set when this message should be sent. The options are:
    — Immediate/next run – the message will be sent as soon as possible. For form, email, and admin system subscriptions, this means immediately. For imported data, it means when the scheduled task next runs.
    — Interval in hours/days – the number of hours/days since the previous message before this one may be sent. The message will be sent as soon as possible after the interval by the scheduled task.
    For new subscriptions where no previous messages have been sent, this interval is calculated from the date and time of subscription to the autoresponder.
    — Monday to Sunday – the message will be sent on the next occurrence of the day of the week specified, assuming the scheduled task is running on that day.
  • Approved for sending – check this box to approve this message for sending. Only administrators and users with the correct permissions can approve messages. See Permission Profiles for more information.
Day, time and duplicate restrictions Section

This section allows you to control the days and times that the message may be sent. For example, you may wish to prevent sending the message during the night or at weekends.

“You can avoid sending messages at weekends and during the night”

  • Can only send on these days – check the days that the message may be sent. Use this to avoid certain days such as weekends.
  • Earliest time to send – choose the earliest time that this message may be sent. Use this to avoid sending too early in the morning.
  • Latest time to send – choose the latest time that this message may be sent. Use this to avoid sending too late at night.
  • Never allow to be resent – check this box to ensure that a contact is never sent this follow-up message more than once, even if the order of messages in the autoresponder is changed.
Tracking and reporting Section

  • Track open rate for HTML and multi-part messages – check this box to track the open rate for HTML and multi-part messages. Email technology does not allow tracking to work for plain text messages.
  • CC recipients – enter a list of email addresses (one per line) that will be CC’d on this message every time it is sent to a contact. Note that all recipients, including the contact, will see the CC’d list.
  • BCC recipients – enter a list of email addresses (one per line) that will be BCC’d on this message every time it is sent to a contact. Recipients, including the contact, will not see the BCC’d list.

The Message Tab

The Message tab is split into three sections for easy management:

  1. Content
  2. Layout
  3. Attachments

Content Section

  • Subject – enter the message subject line.
  • Format – choose the format of the message to be sent. Your options are:
    — Plain text – Send only the plain text version of the follow-up message. You need to enter plain text copy in the Plain text content box.
    — HTML – Send only the HTML version of the follow-up message. You need to enter HTML copy in the HTML content box.
    — Multi-part (Plain text + HTML) *Recommended* – Send both the plain text and HTML versions of the follow-up message, combined into a single multi-part message. You need to enter both plain text and HTML copies.
  • Template to load into editors – choose a template to load into the plain text and HTML editors from your library of pre-created templates (as defined in Content / Templates). Note: You must select the template you want to use before adding in content. If you add content and select a template afterward your content will be lost as the new template will overwrite everything in the content boxes.
  • Plain text content – enter the plain text copy of the follow-up message.
  • HTML content – enter the HTML copy of the follow-up message. Click the Toggle Editor link for a full HTML editor.
  • Add personalisation content tags (link) – clicking this will open a new window that contains all of the available standard shortcode tags that you can copy and paste into your content boxes to personalize your messages.

“Click the Toggle Editor link to use the full HTML editor. It has a full-screen button for easier editing”

Tip! Write your message out in a text app (e.g., Notepad) before adding it into the content boxes. For security reasons, some servers will automatically log you out of arpReach after a specific session length and if you have not saved your writing you will lose all of your work. This is a PHP server setting and not something that can be changed or controlled by arpReach.

Layout Section

  • Add autoresponder’s header – check this box to add the autoresponder’s header before the start of the message contained in the content boxes.
  • Add autoresponder’s footer – check this box to add the autoresponder’s footer after the end of the message contained in the content boxes.
Attachments Section

RSS Feed Tab

  • Include in autoresponder’s RSS feed – check this box to include this message in the RSS feed for this autoresponder. Using this facility, you can control which of the autoresponder’s messages appear in the RSS feed and which are sent by email only.

Once you have added your first message, you will be taken back to the Follow-Up Messages list screen.

Subscription Tags

Subscription tags are used in an autoresponder’s follow-up messages. These tags should NOT be inserted into broadcast messages.

An optional default value will be inserted if the information is blank.

Important Note: The “[” and “]” (square brackets) in the subscription tags define the default value element but should not be included in your email.

{MESSAGE_COUNT} - the number of messages in the autoresponder.
{MESSAGE_NUMBER} - this message number in the autoresponder.
{SUBSCRIPTION_LENGTH} - the number of days since subscription.
{CONTACT_COUNT} - the number of unique autoresponder subscribers.

{SENDER_NAME}
{SENDER_EMAIL_ADDRESS}
{REPLY_TO_EMAIL_ADDRESS [default value]}

{SUBSCRIBE_IP_ADDRESS [default value]}
{SUBSCRIBE_USER_AGENT [default value]}
{CONFIRM_IP_ADDRESS [default value]}
{CONFIRM_USER_AGENT [default value]}

{UNSUBSCRIBE_IP_ADDRESS [default value]}
{UNSUBSCRIBE_USER_AGENT [default value]}

{SUBSCRIBE_DATE_1} - Date format #1 as defined in your Date formats settings.
{SUBSCRIBE_DATE_2} - Date format #2 as defined in your Date formats settings.
{SUBSCRIBE_DATE_3} - Date format #3 as defined in your Date formats settings.
{SUBSCRIBE_DATE_4} - Date format #4 as defined in your Date formats settings.
{SUBSCRIBE_DATE_5} - Date format #5 as defined in your Date formats settings.
{SUBSCRIBE_DATE_6} - Date format #6 as defined in your Date formats settings.
{SUBSCRIBE_DATE_7} - Date format #7 as defined in your Date formats settings.
{SUBSCRIBE_DATE_8} - Date format #8 as defined in your Date formats settings.

{TRACKING_TAG_NAME [default value]}
{AUTORESPONDER_CONFIRMATION_SUBJECT [default value]}
{AUTORESPONDER_CONFIRMATION_TEXT [default value]}
{AUTORESPONDER_CONFIRMATION_HTML [default value]}

{NEXT_LINK} - link to send the next message immediately.
{CONFIRM_LINK} - link to confirm subscription.
{UNSUBSCRIBE_LINK} - link to unsubscribe from this autoresponder only.
{RSS_FEED_LINK} - link to the RSS feed of the sequence.