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?

 

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

System Settings Tags

System settings tags insert content from Setup / System Settings.

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.

Opt-in confirmation

{SYSTEM_CONFIRMATION_SUBJECT [default value]}
{SYSTEM_CONFIRMATION_TEXT [default value]}
{SYSTEM_CONFIRMATION_HTML [default value]}

Standard messages

{ANTI_SPAM_MESSAGE [default value]}
{PRIVACY_STATEMENT [default value]}

Contact and subscription management

{MANAGE_LINK_TEXT [default value]}
{EDIT_LINK_TEXT [default value]}
{NEXT_LINK_TEXT [default value]}
{UNSUBSCRIBE_LINK_TEXT [default value]}

Support resources

{SUPPORT_EMAIL_ADDRESS [default value]}
{SUPPORT_WEBSITE [default value]}

Resources box

{RESOURCE_BOX_TEXT [default value]}

Affiliate program

{AFFILIATE_ID [default value]}
{AFFILIATE_LINK_TEXT [default value]}
{AFFILIATE_LINK [default value]}
{AFFILIATE_AD [default value]}
{AFFILIATE_AD_TEXT [default value]}
{AFFILIATE_AD_HTML [default value]}

Note that {AFFILIATE_AD} and {AFFILIATE_AD_TEXT} are equivalent.

Date Tags

Date tags insert today’s date in one of the eight formats defined in Setup / System Settings / System / Date formats.

{DATE_1}
{DATE_2}
{DATE_3}
{DATE_4}
{DATE_5}
{DATE_6}
{DATE_7}
{DATE_8}

#V2-exclusive: Creative Date Tags

The date tags below allow you to change the date displayed either to a date in the past or a date in the future.

They can be used with or without the + (plus) or – (minus) modifiers.

For example, the date tag:

{SHORTDATE}

… is today. While the date tag:

{SHORTDATE +1}

… is today + (plus) one day. And the date tag:

{SHORTDATE -1}

… is today – (minus) one day.

Below are the creative date tags that you can use in arpReach, which also shows how the date modifiers: year, months, weeks, and days can be used. Your date can also be in European or US formats.

{SHORTDATE +3 days}
{LONGDATE -2 weeks}
{USDATE +1 year 2 months 1 week 5 days}
{USLONGDATE +5}
{USLONGDATENOYEAR -3 days}
{EUROPEANDATE +3}

{WEEKDAY}
{WEEKDAY +2}

 

Persona Tags

Persona tags insert information from the persona that you assigned to send the broadcast message or autoresponder sequence.

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.

{PERSONA_TITLE [default value]}
{PERSONA_FIRST_NAME [default value]}
{PERSONA_LAST_NAME [default value]}
{PERSONA_FULL_NAME [default value]}
{PERSONA_POSITION [default value]}
{PERSONA_DEPARTMENT [default value]}
{PERSONA_COMPANY [default value]}
{PERSONA_ADDRESS_1 [default value]}
{PERSONA_ADDRESS_2 [default value]}
{PERSONA_ADDRESS_3 [default value]}
{PERSONA_ADDRESS_4 [default value]}
{PERSONA_ADDRESS_5 [default value]}
{PERSONA_PHONE_NUMBER_1 [default value]}
{PERSONA_PHONE_NUMBER_2 [default value]}
{PERSONA_FAX_NUMBER_1 [default value]}
{PERSONA_FAX_NUMBER_2 [default value]}
{PERSONA_EMAIL_ADDRESS_1 [default value]}
{PERSONA_EMAIL_ADDRESS_2 [default value]}
{PERSONA_EMAIL_ADDRESS_3 [default value]}
{PERSONA_EMAIL_ADDRESS_4 [default value]}
{PERSONA_EMAIL_ADDRESS_5 [default value]}
{PERSONA_WEBSITE_1 [default value]}
{PERSONA_WEBSITE_2 [default value]}
{PERSONA_WEBSITE_3 [default value]}
{PERSONA_WEBSITE_4 [default value]}
{PERSONA_WEBSITE_5 [default value]}
{PERSONA_SIGNATURE_1 [default value]}
{PERSONA_SIGNATURE_2 [default value]}
{PERSONA_SIGNATURE_3 [default value]}
{PERSONA_SIGNATURE_4 [default value]}
{PERSONA_SIGNATURE_5 [default value]}
{PERSONA_RESOURCE_BOX_1 [default value]}
{PERSONA_RESOURCE_BOX_2 [default value]}
{PERSONA_RESOURCE_BOX_3 [default value]}
{PERSONA_RESOURCE_BOX_4 [default value]}
{PERSONA_RESOURCE_BOX_5 [default value]}
{PERSONA_OTHER_1 [default value]}
{PERSONA_OTHER_2 [default value]}
{PERSONA_OTHER_3 [default value]}
{PERSONA_OTHER_4 [default value]}
{PERSONA_OTHER_5 [default value]}

Variable, Ad, and Trackable Link Tags

An optional default value will be inserted if the information doest not exist or 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.

Variable Tags

Inserts the contents of a variable using the variable’s tag.

{VARIABLE_<tag> [default value]}
  • Example #1 – {VARIABLE_Price}
  • Example #2 – {VARIABLE_Price Call For Details}

Ad Tags

Inserts the plain text or HTML version of an ad using the ad’s tag.

{AD_<tag> [default value]} 
{AD_TEXT_<tag> [default value]} 
{AD_HTML_<tag> [default value]}
  • Example #1 – {AD_Membership_S}
  • Example #2 – {AD_Membership_S Invites Only}

Note that {AD_<tag>} and {AD_TEXT_<tag>} are equivalent.

Trackable Link Tags

Inserts the URL of a trackable link using the trackable link’s tag.

{LINK_<tag>}
  • Example #1 – {LINK_BBR01}
  • Example #2 – {LINK_ON02I03}

Broadcast Tags

Broadcast tags insert information from the broadcast being sent. These tags should NOT be inserted into follow-up 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.

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

To insert a link to the online version of the broadcast:

{BROADCAST_ONLINE}
{BROADCAST_ONLINE_TEXT}
{BROADCAST_ONLINE_HTML}

Note that {BROADCAST_ONLINE} and {BROADCAST_ONLINE_TEXT} are equivalent.

To insert the header or footer at a place other than the top/bottom:

{HEADER_TEXT [default value]}
{HEADER_HTML [default value]}
{FOOTER_TEXT [default value]}
{FOOTER_HTML [default value]}

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.