Data Capture Best Practice

Taking the time to build and maintain Lists of engaged Users will always return the best results in terms of Campaign performance.

Once consent to send emails to people has been gathered it is important that Lists are being maintained through sending regular email, providing recipients with the ability to opt-out and also using other List hygiene related features to ensure the quality of data stored remains at the highest level possible.

We have a permission policy for sending emails and by using the service provided you are acknowledging and agreeing to our Terms of Use.

Proven permission is required to send emails to Users on your Lists and without proven permission it means you do not have consent and are effectively sending Spam.

Importing & Capturing Data

When data is captured outside of the features of our service permission and compliancy with applicable law is still required. Importing data into our application (CSV upload, via the API etc.) implies acknowledgment of and agreement with our Terms of Use.

Forms and Automation enable data to be captured and entered directly into the application.

A method for ensuring quality of data, improving security and to confirm consent is to automatically send a confirmation that contains a unique link and that the person must click in order to complete the process.

This approach is commonly known as "double opt-in" and is something that regular users of the internet will be familiar with. Double opt-in is a very good method for ensuring that consent is given and the details of which, including date, time and IP address, will be stored for future reference if needed.

Click here to find out more about how to make use of double opt-in when capturing data.

Preferences & Opt-out

Every email that gets sent should always include a clearly displayed and accessible link for people to opt-out. There are exceptions to this for more transactional type emails such as receipts and invoices but in general terms a User should always be able to opt-out.

Where people are subscribed to multiple Lists it's also advisable to include a link to allow people to set their own preferences. This puts recipients in control over what types of emails they want to receive.

Inactive Email Addresses

There are a number of different types of Spam traps and ISPs including AOL, Yahoo and Microsoft will "recycle" old and unused email addresses in an attempt to detect senders that do not keep their Lists clean.

The time between an email addresses becoming dormant and then being converted into a Spam trap varies (and it does not happen for every dormant email address) but it makes complete sense to have a process in place to periodically remove email addresses that do not engage through opens or clicks.

A common approach is to implement a process where any email address that does not engage for a period of 9 months becomes suppressed entirely.

Overall List size will reduce by removing inactive email addresses but it will result in List quality being improved and will also reduce complaint rates.

Auto-cleansing & Suppression

Auto-cleansing is the automated process of suppressing email addresses of Users that have either complained or where repeated delivery failures have been encountered when sending emails. This process helps to keep Lists 'clean' by ensuring bad email addresses and User records that have previously complained can never be used.

There are a number of features that can be used to suppress email addresses and it is recommended that you take the time to understand the differences between each type of suppression and how they can work in combination to maintain customised preferences for individual Users.

Here's a brief explanation of the available options...

  • Email addresses that are added to the Global Suppression will never receive an email regardless of what Lists they appear on.

  • List level suppression is useful when there is the requirement to allow people to receive specific types of emails based on topics of interest. For example, a person may want to stay updated about news relating to football but may no longer be interested in receiving news about cricket.

  • The Realtime Block List allows for individual email addresses and entire domains to be blocked by the application. Not only does this stop emails from being sent for anything that is listed it also stops data getting into the application through file upload, API, Forms etc.

  • On the Campaign send screen there is a feature that enables entire Lists to be excluded. It's a useful feature for suppressing Users when there is duplication across Lists and, for example, allows you to send to all of the people on a selected List whilst ensuring the email does not get sent to anyone that appears on a different List.

Common Questions

What is GDPR?

The General Data Protection Regulation (GDPR) (Regulation (EU) 2016/679) is a regulation by which the European Parliament, the Council of the European Union and the European Commission intend to strengthen and unify data protection for all individuals within the European Union (EU). For more info, click here.

How can legal compliancy be ensured?

First, read the application Terms of Use and then research the worldwide legislation to review how each law impacts on the data you store and the emails you send.

What is double opt-in?

Double opt-in is a way to validate email addresses as people complete forms (signup, register etc.). Before being added to a List the User must first click the link on the email sent to their inbox. To find out more about double opt-in, click here.

What is a "Subject Access Request"?

An individual is entitled to obtain all of the information stored about them and this is commonly termed as a 'Subject Access Request'. For more info on how to deal with this type of request, click here.

What is the "Right to Be Forgotten"?

When an individual no longer wants their information to be stored they are able to exercise their right to be forgotten. Users can opt-out at any time but this goes a step further and removes all personally identifiable information relating to them. For more info on how to deal with this type of request, click here.

Related Pages