Check for Updates

At any time, you can check if there is a newer version of arpReach by going to Setup / Check for Updates:

Check for Updates — Running an old version

Check for Updates — Running the latest version

For best performance, we recommend that you always run the latest version of arpReach. This is available for download from the arpReach Hub providing you have an active Updates and Support plan.

reCAPTCHA Keys

Using reCAPTCHA keys as part of your form-based sign-up process will significantly reduce the number of fake and malicious sign-ups to your system. By using reCAPTCHA keys, you benefit by having increased email deliverability because you send fewer emails to “bad” email addresses and you also help to reduce the amount of spam and malicious emails that get sent.

Registering for Google reCAPTCHA

Before you can use reCAPTCHA, you need to sign up for an API key pair for your site at:

https://www.google.com/recaptcha/admin

After signing up, you will need to register the site(s) that you want to use reCAPTCHA with.

Google provides full details here:

https://developers.google.com/recaptcha/intro

In the reCAPTCHA site setup screen:

  1. Enter your desired label
  2. Choose the type of reCAPTCHA you want to use
  3. Enter the domain/s where you will be using the reCAPTCHA
  4. Accept the reCAPTCHA Terms of Service
  5. Click the SUBMIT button

Note that selecting reCAPTCHA V2 will expand the screen so you could choose what type of reCAPTCHA V2 to use:

After clicking the SUBMIT button, your reCAPTCHA keys will be created:

Copy the LabelSite Key, and Secret Key needed for the next step. We recommend you save them temporarily in a text file.

Managing Your reCAPTCHA Keys

To manage your reCAPTCHA keys, choose Setup / reCAPTCHA Keys / Show List from the menu bar:

To add a new reCAPTCHA key, choose Add a reCAPTCHA key from the I Want To… menu on the reCAPTCHA Keys list screen:

To edit an existing reCAPTCHA key, choose Edit from the Actions column on the reCAPTCHA Keys list screen:

When creating or editing a reCAPTCHA key, the settings are the same:

  • Site Name – this MUST be the same as the label that appears in the reCAPTCHA site.
  • Site key – the site key.
  • Secret key – the secret key.

You will now be able to use reCAPTCHA in the forms you create for each autoresponder.

This is an example of a subscription form with the reCAPTCHA V2 Checkbox (styled and formatted using an HTML editor):

… and this is an example of a subscription form using either the reCAPTCHA V2 Invisible Badge or reCAPTCHA V3 (styled and formatted using an HTML editor):

Remember that each reCAPTCHA can only be used on the domains you chose when setting up the keys at the reCAPTCHA site.

We recommend that you create new keys for each domain that you want to use your forms on so that you get good analytics.

Backup and Restore

You can back up your arpReach system’s SQL data using this facility and also restore it when necessary.

Note that due to PHP memory constraints and other PHP limitations, it may not be possible to use these facilities. In those circumstances, your web host can give you alternative ways to back up and restore your SQL data. Alternatives may be phpMyAdmin or via the command line. Your web host can advise.

Backing Up Data

Use this procedure to make a complete backup of your entire arpReach data set.

“Consider making a new backup before restoring an old one to ensure you can get back to your current state”

Using the menu bar, go to Setup / Backup & Restore / Create Backup:

Select your desired Format of backup file (Raw SQL or Zipped SQL):

Click the Create Backup button.

Then click on the link on the next screen to download the backup file:

Restoring Data

You can restore previously backed-up data using this facility.

WARNING – this deletes all current data before restoring!

Using the menu bar, go to Setup / Backup & Restore / Restore Backup:

Choose the file to restore and click the Upload Backup File button:

On the next screen, check the Check to confirm box to confirm you understand that all data will be overwritten by the restore process:

Then, click the Confirm button.

Email Headers

In the fight against SPAM, ISPs and email providers like Gmail and Outlook are increasingly using special information in email headers to manage unsubscribes and to help their systems decide if the incoming email is legitimate.

What are Email Headers?

For some context, an email consists of three core elements: 1) the envelope, 2) the header(s), and 3) the body of the email message. Think of the envelope as the wrapper that allows the email to be sent from A to B. The body is the bit we all normally see (the words and images), while the header is generally hidden but essential for email delivery.

Some headers are mandatory and you will already be familiar with them, such as the FROM, TO and DATE headers. Others are optional, but very commonly used, such as SUBJECT and CC. Other headers include the sending time stamps and the receiving time stamps of all mail transfer agents that have received and sent the message.

arpReach allows you to create any number of custom email headers in addition to the mandatory ones already used and assign them to any of your sending email systems.

As ISP requirements change, we occasionally add some custom headers as defaults, meaning they are automatically created when you install arpReach.

List-Unsubscribe is one such default custom email header and it inserts a Manage Subscriptions link into the header of emails as required by some ISPs.

You can add new custom email headers as ISPs start to use them. You can use the personalization tags in arpReach to construct the link format and insert the correct information for the recipient contact. This is helpful if you need to track who an email was sent to if the recipient complains.

At an advanced level, the real benefits of tracking custom X-Headers within email metrics begin when you separate campaigns, regions, or other special information to create new email metrics. With this new information, you will be able to determine and then optimize which campaign or region is providing the most opens or clicks. You will also be able to quickly repeat your tests to help increase conversions.

Managing Your Custom Email Headers

To manage your custom email headers, choose Setup / Email Headers / Show List from the menu bar:

To add a new custom email header, choose Setup / Email Headers / Create New from the menu bar:

… or choose Create a header from the I want to… menu on the Custom Email Headers list screen:

To edit an existing custom email header, choose Edit from the actions column on the Custom Email Headers list screen:

When creating or editing a custom email header, the settings are the same.

  • Header – the email header. For example, X-MyHeader.
  • Value – the value of the email header. You can use the personalization tags in arpReach such as {MANAGE_LINK}.
  • Assign to new email systems – check this box to automatically assign the custom email header to new email systems that you add. This can be changed in the settings of each email system.
  • Assign to these email systems – check the email systems that you want to assign the custom email header to. This can be changed in the settings of each email system.

Resources

RFC 822 – STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES

Users and Permission Profiles

“You can create any number of users for your company and control their access to all areas of the system using permission profiles”

Important distinction: While you can create an unlimited number of users for your company, it is not possible to create users for a different company (e.g., a client) and protect access to individual items such as autoresponders in a way that each client would only see their autoresponder. That would be a different type of software. That being said, you can use arpReach very successfully to run email marketing campaigns on behalf of your clients. Discover more in the Permission Profiles section.

Managing Users
Managing User Permission Profiles
User Permission Use Cases

Users

You can add multiple users to your arpReach system and control the areas of the system that they can access by assigning permission profiles. A user who has Administrator status cannot be assigned a permission profile and has unrestricted access to all areas of the system.

To manage your users, choose Setup / Users / Show List from the menu bar:

To add a new user, choose Setup / Users / Add a New User from the menu bar:

… or choose Add a user from the I Want To… menu on the Users list screen:

To edit an existing user, choose Edit from the actions column on the Users list screen:

When adding or editing a user, the settings are the same.

Account Settings Tab

  • User name – the unique username the user will enter to access the system.
  • Password – the password the user will enter to access the system.
  • Name – the name of the user.
  • Email address – the email address of the user. This is used to send the user their username and new password if they have forgotten them.
  • Level – the access level of the user.
    Administrator – has unrestricted access to all parts of the system.
    User – has restricted access to the system. The areas that can be accessed are defined by the user’s permission profile. If no permission profile is assigned, then the user has no access to any functionality within the admin system.

Preferences Tab

  • Show page header – controls whether the page header is shown at the top of the screen when using the admin system. Switch this off to free up more screen space for data.
  • Number of list items per page – controls how many items are shown per on list screens such as the contact list. A small number means faster screen drawing.
  • Show form field hints – controls whether form field hint icons are shown for every field on forms. When hints are showing, hovering your mouse over the question mark will display a panel of information about that field.
  • Home page – the page to be shown when the home icon is clicked or the user logs in. The choices are:
    My dashboard
    Action maps
    Autoresponder list
    Broadcast queue
    Contact list
    About screen
  • Report to show on dashboard – controls which graph is shown on your dashboard. The choices are:
    New contacts today
    New contacts yesterday
    New contacts this week
    New contacts last week
    New contacts this month
    New contacts last month
    New contacts this year
    New contacts last year
  • Format for dashboard report – sets the chart type for the dashboard report from:
    Line chart
    Bar chart

Permission Profiles

“Use permission profiles to manage the areas of the system that users can access.”

With a permission profile, you can control which areas of the arpReach admin system can be accessed by users with that permission profile.

To manage your permission profiles, choose Setup / Permission Profiles / Show List from the menu bar:

To add a new permission profile, choose Setup / Permission Profiles / Create New from the menu bar:

… or choose Create a permission profile from the I Want To… menu on the Permission Profiles list screen:

To edit an existing permission profile, choose Edit from the actions column on the Permission Profiles list screen:

When you create or edit a permission profile, the following options are available.

Settings Tab

  • Name – the unique name of the permission profile.
  • Description – a description of the permission profile.
  • Assign to new users – check this box to make this permission profile the default that is assigned to new users that you create in the future. There can only be one default permission profile.

Permissions Tab

The Permissions tab has six sections where you can choose the areas of the system that users with this permission profile will be able to access:

  • General
  • Autoresponders
  • Broadcasts
  • Content
  • Contacts
  • Setup

Visit each section in turn and check the boxes beside the functions you wish to make available. Use the Select all, Deselect all and Invert selection links for faster selection.

If you change the permissions in an existing permission profile, those changes will be instantly applied to all users with that permission profile.

In the image above, we see the available permission control options you can apply to a user in respect of their access to Autoresponders and the associated autoresponder functions.

User Permission Use Cases

For this use case, we consider a larger business with different departments that employs writers, editors, and department managers.

A new writer: A new employee may have great writing skills, but you want to check the quality of their work. You would not want them to edit or delete existing content in other autoresponder messages, and you would not want to give them the responsibility of testing their own work or approving their own work. You could, therefore, give them View and Add permissions.

For an editor: An editor has more responsibility and has built a higher level of trust within the company. You can, therefore, give your editors all permissions with the exception of making the final approval of the email content in your campaigns.

For the owner / manager:  As the business owner or responsible manager, in this scenario, you have had a writer add content, you have had your editor check the writer’s content and make suitable changes, and the editor has notified you that your message is ready for your final approval. You have the ability to make any edits or changes you want and the final approval is also yours.

In all of the permission profile options, you can consider your use case and give or deny the appropriate access depending on your need.

Tip! Always log in as the user with the permission profile you have created and check if the user has the access they need to complete their work but does not have access to the things you want protected (e.g., you should very carefully consider who you give any Setup access to).

Email Systems

In this section, we will discuss email systems and go into detail on:

arpReach allows you to add as many local and remote email systems as you need. They can be local MTA systems, such as Sendmail or Exim, or SMTP servers that may or may not require authentication.

“You can create as many local and remote email sending systems as you need”

To manage your email systems, choose Setup / Email Systems / Show List from the menu bar:

Every autoresponder and broadcast that you create has a sending email system, and the email system you assign as the default is assigned to new autoresponders and broadcasts. This can be changed in the settings of individual autoresponders and broadcasts.

To set a default email system, choose Set as default from the actions column on the Email Systems list screen.

Adding or editing an email system

When adding or editing an email system, the settings are the same.

To add a new email system, choose Setup / Email Systems / Add an Email System from the menu bar:

… or choose Add an email system from the I Want To… menu on the Email Systems list screen:

To edit an existing email system, choose Edit from the Actions column on the Email Systems list screen:

Settings Tab

  • Name – a unique name for the email system.
  • Description – a description of the email system.
  • Set as the default – check this box to use this email system as the default for new autoresponders and broadcasts. This can be changed in the settings of individual autoresponders and broadcasts.

Options Tab

Server Settings Section
  • Sending method – choose the sending method from:
    Sendmail – local mail transport software on your web server such as Sendmail or clones like Exim. You need to provide the path to Sendmail which your web host can provide if you don’t know it.
    SMTP – a local or remote SMTP server. You need to provide the server details, including the login credentials, if the SMTP server requires them. The provider of the SMTP server can give you these details.
Advanced Section

This section allows you to manage the speed at which you send emails and/or comply with your web host’s email sending limits.

  • Batch size – enter the number of contacts that will be processed in each batch for this email system. A higher number requires more memory but requires fewer database reads/writes and is therefore faster. The default is 250 and this is recommended for most situations.
  • Send limit per run – the number of emails that this email system may send during one run of the scheduled task. Use this to stay within your host’s sending limit if they have one.
  • Delay between each email – the number of milliseconds between every email sent by this email system. Use this if your host requires a delay. It should be zero for most situations.
  • Character set – choose the character set to send email in. The default is UTF-8 and this should be suitable for most situations.
  • Bounce address type – choose how bounces will be handled for email sent by this email system.
    Local – This is the normal settings and bounces are processed locally as they arrive at the email address being monitored as set up in Setup / System Settings / System / Incoming Email.
    Remote – Use this setting if you use the services of a remote bounce processor. They will provide you with the server and login details to enter here.
  • Send failure strings – these are custom messages sent back by some SMTP providers at the time of sending if, for one reason or another, the SMTP provider cannot send the email. They should be added one per line, entering a few unique words from the middle of the received error (Note: Matches are case-sensitive.). You can react to these failures in two ways:
    — Fail all the contact’s subscriptions – all the contact’s subscriptions will be flagged as failed.
    — Add contact to suppression list – the contact’s email address will be added to the global suppression list so that no email will be sent.

Custom Headers Tab

  • Add these custom email headers – choose the custom email headers to be added to every email sent by this email system.

How to comply with the sending limits of your server

Some servers set a limit on the number of emails that could be sent per hour.

arpReach is designed to manage such hosting limits, all you have to do is ask your web host what your hourly sending limit is and follow the guidelines below. Everything will run on autopilot from then on.

Let’s say your server only allows 500 emails to be sent per hour. The solution is to change some settings so that no more than 500 emails per hour get sent by arpReach. arpReach will then automatically manage sending 500 emails per hour until all due emails have gone out.

There are two settings to change to ensure that you comply with the limit:

  • the run frequency of your scheduled task (cron job) for the arpReach script
  • your email system’s Send limit per run setting

Scheduled task (cron job)

In the event your web host places limits on the volume of emails you can send per hour, we recommend setting the run frequency of your scheduled task (cron job) for the arpReach script to every 5 minutes. You can change this in your cPanel by changing its “minutes” setting to */5.

This means that the sending of emails will also occur every 5 minutes, whenever the arpReach script runs, totaling to 12 runs per hour (60 mins divided by 5 = 12).

Because you are limited to 500 emails per hour, you need to ensure that each of those runs sends no more than 41 emails.

Here’s a quick formula that you can use:

(hourly limit) / (no. of cron job runs in an hour)
500 / 12 = 41.67

Send limit per run (in arpReach)

Now, go to your email system’s settings in arpReach, then go to Options / Advanced and set the Send limit per run slightly lower than 41. For example, 38.

Setting the Send limit per run value slightly lower (i.e., 38 instead of 41) gives way to immediate/unscheduled messages (such as subscription confirmation emails and single emails triggered by actions).

Important Note: We’ve always been recommending setting the Delay between each email to zero (0), since setting it to a high number would not only slow the sending, but also cause timeouts. If there really is a need for a delay between each email, it should be set to a low number, and make sure that your server’s MySQL timeout can handle it.

#V2-exclusive: FBL (Feedback Loops)

In #V2, the email systems menu is accessed from the same location but has the additional FBL (Feedback loops) capability.

An FBL is a method that allows Internet Service Providers (ISPs) and third-party email service providers to notify senders of emails about problems with the emails they are sending to their contacts. The notifications received via an FBL are generally spam complaints, but they can also indicate other issues which vary from ISP to ISP.

To maintain a high sender reputation, it is essential that you do not send emails to contacts who no longer want them. When people complain, they do not always unsubscribe themselves from your list, but using the FBL feature allows you to automatically remove them from your autoresponders and also optionally add them to your ‘Do Not Contact’ list.

Currently, #V2 provides FBL processing for:

  • Amazon SES/SNS
  • Mailgun
  • Mailjet
  • Mandrill
  • SendGrid
  • Sendinblue
  • SparkPost

To access and set up a new FBL, choose Setup / Email Systems / FBL (Feedback Loops) from the menu bar. This will bring you to the FBL (Feedback Loops) setups list screen:

Each ESP will require you to set up your FBL in a slightly different way using the webhook URL links provided. Click on the setup instructions link for detailed instructions on how to set up your FBL. The instructions will open in a new window.

API Keys

The arpReach API lets you integrate arpReach with other applications. This functionality is only available in arpReach Gold or #V2.  To use the API, you must be using at least version 1.4.001 of arpReach Gold. The latest version can be downloaded from the arpReach Hub.

Managing Your API Keys

To access the API, you need to create an API key within the software. You can create as many API keys as you need for the integrations you will be creating. By enabling and disabling keys, you can control which other applications have access to your data via the API at any time.

To manage your API keys, choose Setup / API Keys / Show List from the menu bar:

To create a new API key, choose Setup / API Keys / Create New from the menu bar:

… or choose Create an API key from the I want to… menu on the API Keys list screen:

To edit an existing API key, choose Edit from the Actions column on the API Keys list screen:

When creating or editing an API key, the settings are.

  • Name – the name of the API key.
  • Description – a description of the API key. Possibly where it will be used.
  • Enabled – check this box to enable the API key.
  • Restrict access by IP – check this box to restrict the use of the API key by IP address. This function is used to improve the security of your system by limiting access to this API key to only the IP addresses listed in the Allowed IP addresses box.
  • Allowed IP Addresses – a list of IP addresses that you want to be able to use this API key when the Restrict access by IP is enabled. The IP addresses can be listed as a comma-separated list or each IP address can be on its own line. (Note: If you are providing access to an IP address that is shared hosting, other users of the IP address will be able to use the API.)

#V2-exclusive: Secret String and Check Signature

#V2 has improved API security thanks to its secret string and check signature capabilities. When creating or editing an API key in #V2, the settings are:

V2 api key settings
  • Name – the name of the API key.
  • Description – a description of the API key. Possibly where it will be used.
  • Permission profile – Choose a permission profile to assign to this API Key to restrict access to specific areas of the software.
    No permission profile may be assigned to disable the API Key to access any data (only ping is allowed). In Permission Profiles you will find the Default API Profile – This grants access to All API functions.This may be useful for a client software tests.
  • Key – The API Key
  • Secret – The API challenge secret
  • Enabled – check this box to enable the API key.
  • Check for signature – Signatures authenticate the request sender as only the owner of the “secret” can create a valid signature.
    You may check Off this option for existing services integrated with arpReach to keep them still work.It’s secure enough to disable signature checking over HTTPS or TLS (but this is not acceptable over insecure HTTP).
  • Restrict access by IP – check this box to restrict the use of the API key by IP address. This function is used to improve the security of your system by limiting access to this API key to only the IP addresses listed in the Allowed IP addresses box.
  • Allowed IP Addresses – a list of IP addresses that you want to be able to use this API key when the Restrict access by IP is enabled. The IP addresses can be listed as a comma-separated list or each IP address can be on its own line. (Note: If you are providing access to an IP address that is shared hosting, other users of the IP address will be able to use the API.)

Making API Requests

You make requests to the API by issuing HTTP calls to an API URL in your arpReach system. This will be your base URL followed by /api.

The examples shown are for an installation where arpReach is installed in the sub-domain “arpreach” of domain “example.com”:

https://arpreach.example.com/a.php/api

API Functions

The API provides various functions such as add contact, get contact details, remove a contact from a list, and so on. The function is set in the second segment of the URL to the API, after the /api part.

#V2-exclusive: Custom fields support

With #V2, you can save and update custom field data and include them when getting contact information via the API functions get_contact, add_contact, and edit_contact.

Examples:

https://arpreach.example.com/a.php/api/add_contact
https://arpreach.example.com/a.php/api/get_contact

A full list of the API functions is detailed in our API Guide.

Response Formats

The arpReach API delivers responses in JSON or XML format. The default response format is JSON. To set the response format for any call to the API, add /xml or /json to your request URL after the function part of the URL.

Examples:

In the following example, the response will default to JSON as no format is specified in the URL:

https://arpreach.example.com/a.php/api/add_contact

In these examples, however, the response format is specified in the URL as XML and JSON:

https://arpreach.example.com/a.php/api/add_contact/xml
https://arpreach.example.com/a.php/api/add_contact/json

Passing Parameters:

Parameters: are passed as GET or POST data. Your request must include a parameter called api_key containing one of your arpReach system’s API keys. Calls to invalid or disabled API keys will be rejected with an error response. Most functions need other Parameters:, these are detailed below.

To pass Parameters: via GET, add them to the calling URL, for example:

https://arpreach.example.com/a.php/api/add_contact/json?api_key=12345ABCDE&email_address=subscriber001@example.com

Responses

Contents

Responses are sent for:

  • confirmation of API call
  • error messages
  • returned data

Responses are returned in either JSON or XML format.

The default is JSON, the format is specified in the URL after the api Function call:.

JSON Response Format

Responses are in standard JSON format. The response contains pairs for:

  • status – ok or error
  • details
  • returned values

Examples:

{"status":"ok","detail":"Success"}
{"status":"error","detail":"Contact already exists"}

If the call contains multiple lists, there will be responses for the contact and each list. These will be returned in a JSON array, for example:

[
{"email_address":"subscriber001@example.com","status":"ok","detail":"Success"},
{"list":"Sales","status":"ok","detail":"Success"},
{"list":"fred","status":"error","detail":"List not found"}
]

{"status":"error","detail":"Contact already exists"}

XML Response Format

The response is returned in XML elements. As for JSON, the response contains elements to identify the API call, status, details, and data values.

Examples:

<ARPapi>
<response>
<email_address>subscribe001@example.com</email_address>
<status>ok</status>
<detail>Success</detail>
</response>
</ARPapi>

<ARPapi>
<response>
<email_address>subscriber001@example.com</email_address>
<status>ok</status>
<detail>Success</detail>
</response>
<response>
<list>Sales</list>
<status>ok</status>
<detail>Success</detail>
</response>
<response>
<list>east</list>
<status>error</status>
<detail>invalid list format</detail>
</response>
<response>
<list>fred</list>
<status>error</status>
<detail>List not found</detail>
</response>
</ARPapi>

arpReach API Guide

For a more detailed look into the arpReach API, visit the online API Guide.

Ban and Suppression Lists

Ban and suppression lists protect your business and your email marketing system from accepting contacts who are undesirable and from sending emails to contacts that may damage your reputation. The power of your suppression lists should never be underestimated!

Ban Lists

Ban lists prevent unwanted people from subscribing either via a web form, email, or by manually adding or importing in the admin system.

Banned Domains List

This is a list of domains from which no email address is allowed to subscribe. To access it, go to Setup / Ban Lists / Domain Ban List:

Domains can be added to your Banned Domains list manually, just hover your mouse over the I want to… menu on the Banned Domains list screen and choose the appropriate option. Domains can be added one at a time or in a list where each domain must be on its own line.

Use Case: The following domains are common misspellings of the correct domain.

gmial.com
outlokk.com

Innocently attempting to send emails to these domain names could reduce your email sender score or reputation and limit your ability to send emails to legitimate or correct domain names. By adding these to your Banned Domains list, people accidentally providing these domains will not get added to your list and no messages will get sent to these incorrect domains. You just protected your sender reputation by doing so.

Banned Email Addresses List

This is a list of specific email addresses that are not allowed to subscribe. To access it, go to Setup / Ban Lists / Email Ban List:

Email addresses can be added to your Banned Email Addresses list manually, just hover your mouse over the I want to… menu on the Banned Email Addresses list screen and choose the appropriate option. Email addresses can be added one at a time or in a list where each email address must be on its own line.

Use Case: The following email addresses are commonly used to either damage a business or avoid a process to secure a bonus or giveaway without providing a valid email address.

support@google.com
test@example.com

Innocently attempting to send emails to these types of email addresses could reduce your email sender score or reputation and limit your ability to send emails to legitimate or correct email addresses. By adding these to your Banned Email Addresses list, people attempting to use these email addresses will not get added to your list and no messages will get sent to them. You just protected your sender reputation by doing so.

You could also add the email addresses of serial refunders, competitors, and so on.

#V2-exclusive: Import to and export your Ban Lists

With #V2, you can easily import and export to and from your Banned Domains and Banned Email Addresses lists.

To import domains or email addresses to be banned, simply choose Import list from the I want to… drop-down menu on the Banned Domains and Banned Email Addresses list screens.

The file you will be importing must be a standard comma separated values (.CSV) file.

To export your existing banned domains and banned email addresses, choose Export list from the I want to… drop-down menu on the Banned Domains and Banned Email Addresses list screens.

Suppression Lists

Suppression lists prevent any email from being sent to specific contacts. The difference between the ban lists and the suppression lists is that the ban lists stop email addresses from being added to your list building system, while the suppression lists stop emails from being sent to contacts already in your system.

Suppressed Domains

This is a list of domains to which no email will be sent to any contact whose email address is at a domain on the list. To access it, go to Setup / Suppression Lists / Domain Suppression List:

Domains can be added to your Suppressed Domains list manually, just hover your mouse over the I want to… menu on the Suppressed Domains list screen and choose the appropriate option. Domains can be added one at a time or in a list where each domain must be on its own line.

Use Case: You may experience temporary delivery issues to Outlook.com email addresses. Or you may discover that people have signed up to your list using disposable email addresses. You could add the Outlook.com domain to your Suppressed Domains list while you resolve the issue and remove it afterwards, but you could add the domain of the disposable email addresses and leave it in place permanently.

Tip!  If you discover disposable email addresses on your Contacts list, add the domain to your Banned Domains list after suppressing them to keep your list clean.

Suppressed Email Addresses

This is a list of specific email addresses to which no email will be sent. To access it, go to Setup / Suppression Lists / Email Suppression List:

Email addresses can be added to your Suppressed Email Addresses list manually, just hover your mouse over the I want to… menu on the Suppressed Email Addresses list screen and choose the appropriate option. Email addresses can be added one at a time or in a list where each email address must be on its own line.

Use Case: A contact may get in touch to ask you to stop sending them emails. Simply add the email address they provide to your Suppressed Email Addresses list.

Important Note: All contacts using the Manage Subscriptions function in the emails you send can add themselves to the ‘Do Not Contact’ list. When they take this action, their email address is automatically added to the Suppressed Email Addresses list.

You can also use arpReach’s powerful API functions to add email addresses to the Suppressed Email Addresses list. As an example, this could be used to add serial refunders or complainers to your ‘Do Not Contact’ list.

Export your Suppression Lists

To export your existing suppressed domains and suppressed email addresses, choose Export list from the I want to… drop-down menu on the Suppressed Domains and Suppressed Email Addresses list screens.

#V2-exclusive: Import to your Suppression Lists

With #V2, you can easily import to your Suppressed Domains and Suppressed Email Addresses lists.

To import domains or email addresses to be suppressed, simply choose Import list from the I want to… drop-down menu on the Suppressed Domains and Suppressed Email Addresses list screens.

The file you will be importing must be a standard comma separated values (.CSV) file.

Personas

Use personas to create different “personalities” for sending your messages. A persona contains lots of fields that you can include in your messages (such as name, address, and company information) to create an entire sending “personality”.

To manage your personas, choose Setup / Personas / Show List from the menu bar:

The Personas list screen shows the number of autoresponders and broadcasts that are using each persona.

The persona can be changed in the settings of each autoresponder and broadcast.

Creating and Editing Personas

To create a new persona, choose Setup / Personas / Create New from the menu bar:

… or choose Create a persona from the I Want To… menu on the Personas list screen:

To edit an existing persona, choose Edit from the Actions column on the Personas list screen:

When creating or editing a persona, the settings are the same.

Settings Tab

  • Name – the name for the persona.
  • Description – a description of the persona. It is never displayed to contacts.
  • Assign to new autoresponders and broadcasts – check this box to use this persona as the default for new autoresponders and broadcasts. This can be changed in the settings of each autoresponder and broadcast.

Details Tab

Contact Section

  • Title – title for the persona.
  • First name – first name for the persona.
  • Last name – last name for the persona.
  • Full name – full name for the persona.
  • Position – position for the persona.
  • Department – department for the persona.
  • Company – company for the persona.
Address Section

  • Address line #1 – address line 1 for the persona.
  • Address line #2 – address line 2 for the persona.
  • Address line #3 – address line 3 for the persona.
  • Address line #4 – address line 4 for the persona.
  • Address line #5 – address line 5 for the persona.
Phone and Fax Section

  • Phone number #1 – phone number 1 for the persona.
  • Phone number #2 – phone number 2 for the persona.
  • Fax number #1 – fax number 1 for the persona.
  • Fax number #2 – fax number 2 for the persona.
Email Addresses Section

  • Email address #1 – email address 1 for the persona.
  • Email address #2 – email address 2 for the persona.
  • Email address #3 – email address 3 for the persona.
  • Email address #4 – email address 4 for the persona.
  • Email address #5 – email address 5 for the persona.
Websites Section

  • Website #1 – website 1 for the persona.
  • Website #2 – website 2 for the persona.
  • Website #3 – website 3 for the persona.
  • Website #4 – website 4 for the persona.
  • Website #5 – website 5 for the persona.

Signatures Tab

  • Signature #1 – signature 1 for the persona. Expand the More signatures section to create more signatures.

Resource Boxes Tab

  • Resource box #1 – resource box 1 for the persona. Expand the More resource boxes section to create more resource boxes.

Other Fields Tab

  • Other field #1 – other field 1 for the persona. Expand the More fields section to create more fields.

Usable Tags / Shortcodes

Each autoresponder or broadcast that you create can have one of your personas assigned to it. The fields from the persona can be included in messages using the following tags/shortcodes.

“These tags insert information about the sender, not the recipient. There are different tags to insert recipient information”

Title 		        {PERSONA_TITLE}
First name 	        {PERSONA_FIRST_NAME}
Last name 	        {PERSONA_LAST_NAME}
Full name 	        {PERSONA_FULL_NAME}
Position                 {PERSONA_POSITION}
Department          {PERSONA_DEPARTMENT}
Company 	        {PERSONA_COMPANY}
Address line 1 	{PERSONA_ADDRESS_1}
Address line 2 	{PERSONA_ADDRESS_2}
Address line 3 	{PERSONA_ADDRESS_3}
Address line 4 	{PERSONA_ADDRESS_4}
Address line 5 	{PERSONA_ADDRESS_5}
Phone number 1 	{PERSONA_PHONE_NUMBER_1}
Phone number 2 	{PERSONA_PHONE_NUMBER_2}
Fax number 1 	{PERSONA_FAX_NUMBER_1}
Fax number 2 	{PERSONA_FAX_NUMBER_2}
Email address 1   {PERSONA_EMAIL_ADDRESS_1}
Email address 2   {PERSONA_EMAIL_ADDRESS_2}
Email address 3   {PERSONA_EMAIL_ADDRESS_3}
Email address 4   {PERSONA_EMAIL_ADDRESS_4}
Email address 5   {PERSONA_EMAIL_ADDRESS_5}
Website 1 	        {PERSONA_WEBSITE_1}
Website 2 	        {PERSONA_WEBSITE_2}
Website 3 	        {PERSONA_WEBSITE_3}
Website 4 	        {PERSONA_WEBSITE_4}
Website 5 	        {PERSONA_WEBSITE_5}
Signature 1 	        {PERSONA_SIGNATURE_1}
Signature 2 	        {PERSONA_SIGNATURE_2}
Signature 3 	        {PERSONA_SIGNATURE_3}
Signature 4 	        {PERSONA_SIGNATURE_4}
Signature 5 	        {PERSONA_SIGNATURE_5}
Resource box 1 	{PERSONA_RESOURCE_BOX_1}
Resource box 2 	{PERSONA_RESOURCE_BOX_2}
Resource box 3 	{PERSONA_RESOURCE_BOX_3}
Resource box 4 	{PERSONA_RESOURCE_BOX_4}
Resource box 5 	{PERSONA_RESOURCE_BOX_5}
Other field 1  	{PERSONA_OTHER_1}
Other field 2  	{PERSONA_OTHER_2}
Other field 3  	{PERSONA_OTHER_3}
Other field 4  	{PERSONA_OTHER_4}
Other field 5  	{PERSONA_OTHER_5}

Activate Your License

#V2|arpReach needs to be activated before you can use it fully. Please read this page completely to understand the process and information needed.

You need:

  • Your license number and password – from your order confirmation email.
  • Your installation domain name – copied exactly from the license activation page.
  • An activation code – generated from the #V2 Hub or the arpReach Hub.

The first time you try to use #V2|arpReach you are required to activate your license. You will see this page:

Important Note: Take note of the Domain name indicated on the right-hand side of the screen. You must use the exact domain name displayed when registering it in the #V2 Hub or the arpReach Hub or your activation will fail. For example, if it shows:

www.example.com

… register it as:

www.example.com

If it only shows:

example.com

… then you need to register it as:

example.com

Once you have confirmed the domain name to activate, go to the #V2 Hub or the arpReach Hub and log in using the license number and password provided in your order confirmation email.

Once logged in, update your account with your name and email address.

Scroll down to the Register a domain or sub-domain box, input the domain name from your installation, and click the Add button.

You should now see a success message and the registered domain name appear in the Registered domains and sub-domains box.

Next, hover over the drop-down in the Choose domain or sub-domain to activate box and choose the domain you want to activate.

Copy the activation code that appears and save it to a text file. Note that the code will only be usable for 30 minutes.

Now you have all of the details needed to activate your software, go back to the license activation page and:

  1. Paste in your license number.
  2. Paste in your license password.
  3. Paste in your activation code.
  4. Read the terms and conditions and check the box.
  5. Click the Activate Now button at the top of the screen.

Congratulations! You now have an activated #V2|arpReach system. This process needs to be done only once, normally immediately after the software has been installed.