Lists

Get started with the Lists

Today’s email marketing is based on a well matched List of email-addresses, whose owners (Subscribers) have signed up for your company newsletters.

List in ALTKRAFT is a powerful and flexible instrument to manage your subscribers.

New list creation

List’s flexibility and usability depends on how it has been created, filled and supported. If data in the list is properly collected and organized, a user can single out a target group of subscribers in accordance with some specific criteria, and send messages to each group with different content.

This is called a segmentation. And we have a specific element for this - a Segment, which has a big number of self-explanatory roles for subscribers’ groups selection.

Think of your email-marketing strategy for a second. What are your aims, who is your target audience and what kind of content does it need?

Let’s consider some examples:

1. Do you have seasonal customers? Do they like certain product types?

2. Do you need to send different content to your customers according to their preferences?

3. What other parameters/criteria can influence your target audience and each List of subscribers that you manage?

Make it clear for yourself what type of subscribers data is required and, for example, write it down. This will be helpful when you will fill in the custom fields in the List of your subscribers.

List types.

There are two main list types in ALTKRAFT:

Single Opt-in

This doesn’t use an opt-in confirmation email.

Each subscriber is added to the List with “Subscribed” status by default.

Double Opt-in

This does use an opt-in confirmation email.

Each subscriber added to the List is granted a “Not Confirmed” status. Herewith, an opt-in confirmation letter will be sent to him. After a subscriber clicks the confirmation link, he will be granted a “Subscribed” status.

Only subscribers with a “Subscribed” status will receive your newsletters.

Create a list

To create a new List, open the Lists page (Subscribers tab > Lists) and click on the +List button.

You will see a List creation form. There are 4 blocks:

1. General Settings
2. Standard Fields
3. Custom Fields
4. Email Settings

To save a List, please fill in the required fields:

1. List Name
2. List Name seen to a Subscriber
3. From Name
4. From Email
5. And tick the Terms and Conditions of Use box.

Each List is presented as a separate object. After the List is saved, it gets a unique ID. Thus, there can be several Lists with the same name and subscribers details.

General Settings

General Settings are used to set List parameters, and contain general information on each List.

List Name - is a name of a List, that you will see in the list of your personal Lists.

List Name seen to a Subscriber - is a name of a List that a subscriber will see in the Subscription Manager.

Attached suppression list - if certain subscribers or even domains should be excluded from your mail-out, you may create a Suppression list and add them to this list.

Subscribers’ language - this option determines the language of the Subscription Manager page.

Comment - it is a comment to a list, seen only to those users, who have access to the list.

Comment box is used to keep different information about a list. For example, you can enter a list creation aim or a segment name or list creation conditions.

Confirmation letters types - there are two types of confirmation: 1. Double opt-in - in this case a confirmation letter with an activation link will be sent to the address provided by a new subscriber. 2. Single opt-in - in this case no confirmation letter will be sent to a subscriber.

Opt-In letter

Opt-in letter - it is a specific letter type, which requires a subscriber confirmation. The subscriber has an “Unconfirmed” status until the subscription is confirmed.

This letter is created automatically with the Double opt-in List.

If you’ve chosen a Double opt-in option, please fill 4 more fields:

1. Email subject - a subject of an opt-in letter.

2. Text version - a text version of an opt-in letter. Text version is required because some email providers may not display HTML.

3. HTML version - an HTML version of an opt-in letter. (the picture above is an example of an HTML opt-in message).

4. A confirmation link - a link leading to a particular website. After a subscriber confirms the subscription, he will be redirected to this site.

Opt-in letters advantages: * decrease in the number of Hardbounce * achievement of a high sender reputation level * automatic country, city and IP address data saving after a subscriber clicks the confirmation link

Standard Fields

Standard Fields - are used to add general information about subscribers.

Data collection on subscribers is very important if you are going to send personalized letters.

Email - contains a subscriber’s email address. This is the subscriber’s unique ID, and there can’t be two subscribers with the same email address at one List..

First Name - a subscriber’s first name.

Last Name - a subscriber’s last name.

Birth Date - a subscriber’s birth date.

Gender - a subscriber’s gender.

Reg Date - this field is filled in automatically after a subscriber is added to the List.

Reg IP - this field is filled in automatically after a subscriber confirms a subscription through an opt-in letter. Contains information on the subscriber’s IP address .

Reg City - this field is filled in automatically after a subscriber confirms a subscription through an opt-in letter. Contains information on the city the subscriber’s located in.

Reg Country - this field is filled in automatically after a subscriber confirms a subscription through an opt-in letter. It contains information on the country s subscriber’s located in.

Reg URL - a website where a subscriber filled out the registration form. This field is filled in by a user.

IP - IP address that was assigned to a subscriber the last time he opened or clicked a link in the message. This field is filled in automatically.

Country - a country, which a subscriber’s located in the last time he opened or clicked a link in a message. This field is filled in automatically.

City - a city, which a subscriber’s located in the last time he opened or clicked a link in a message. This field is filled in automatically.

Vendor source - this field should be filled in by a user. Here a user can enter information that will help to determine the source of a subscriber sign up. This field is needed to create more detailed reporting and segmentation.

A user can assign a default value to all fields. In this case, if a subscriber didn’t fill in these fields while sign up, they will be filled in automatically by the default value.

A user can make standard fields required and add them to the Subscription Manager.

Custom Fields

Custom Fields are used in case there are not enough standard fields for keeping all the subscribers and segmentation data.

The number of custom fields is not limited.

To add a new field click on the “Add a new field” button at the bottom of the editing form.

There are 7 types of the custom fields:

Number - contains a whole number.

Line - contains text in any language. Unicode standard is used.

Date - contains a date in a particular format.

Boolean - a field that allows to choose between two variants: True or False.

List - this field is like a boolean field, but allows to choose between the unlimited number of variants, created by users. All values should be listed on one line and separated by a comma when creating a list.

IP - IP in the IPv4 format. 127.0.0.1

Tags - this field should be filled in with subscriber’s tags separated by “,” “|” and “;”. Thus, a tag shouldn’t contain these symbols.

Fields containing a subscriber’s action history

These fields are filled in automatically, when a subscriber opens a letter.

Browser - a browser used by a subscriber (Chrome, Firefox, etc.).

Platform - a subscriber’s OS (Windows, Linux, etc.).

Timezone - a subscriber’s timezone (Europe/Stockholm, Asia/Tokyo).

Sent messages - contains information on all the messages sent to a subscriber.

Click - contains information on all subscriber’s clicks.

Opened messages - contains information on types of letters and how many times they were opened by a subscriber.

Read messages - contains information on types of letters and how many times they were read by a subscriber.

Field type - line

Line - contains any text. Unicode standard is used.

For example:
砂漠のワシ - ョ
フォトショップ

This field type has the following parameters as default: “First Name”, “Last Name”, “City” and “Registration City”, “Registration URL”, “Vendor”.

The “Vendor” and “Registration URL” fields have some specific conditions: 1. The “Vendor” field should contain max 26 symbols. 2. The “Registration URL” field should contain a URL (for example: https://www.google.ru/).

String operators for segmentation:

1. Contains - determines if a line contains the specified sequence of symbols.

The operator is not case sensitive. But please mind the gaps number between the symbols.

“Line”, contains, “li” = True
“Line”, contains, “LI” = True
“Line”, contains, “Lne” = False
“Line number two”, contains, “number two” = True
“Line number two”, contains, “Line two” = False

2. Does not contain - the operator opposite to the “Contains”. The line should not contain the specified sequence of symbols.

The operator is not case sensitive. But please mind the gaps number between the symbols.

“Line”, does not contain, “li” = False
“Line”, does not contain, “LI” = False
“Line”, does not contain, “Lne” = True
“Line number two”, does not contain, “number two” = False
“Line number two”, does not contain, “Line two” = True

3. Starts with - the line starts with the specified sequence of symbols.

The operator is not case sensitive. But please mind the gaps number between the symbols.

“Line three”, starts with, “LINE” = True
“Line three”, starts with, “lin” = True
“Line three”, starts with, “three” = False

4. Equal - the sequence of symbols in the field is equal to the specified one.

The operator is case sensitive, also please mind the gaps number between the symbols.

“Line”, equal. “Line” = True
“Line”, equal. “line” = False
“Line three”, equal. “Line three” = False

5. Not equal - the sequence of symbols is not equal to the specified one.

The operator is case sensitive, also please mind the gaps number between the symbols.

“Line”, not equal. “Line” = False
“Line”, not equal. “line” = True
“Line three”, not equal. “Line three” = True

Field type - country

Country - this field contains subscriber’s country details.

There are two types of this field - “Country” and “Registration country”.

Country - this field shows where the subscriber was located in the last time he opened a letter. The information is updated automatically each time a subscriber opens a letter.

Registration country - this field shows where a subscriber was located in while signup. This field is filled in automatically when a subscriber signs up through an opt-in letter. If a subscriber was added through API or manually, a value from these sources is used. If there is no registration country value, a default value from the List is used. If the default value is not entered, the field stays blank.

Operators for country segmentation:

1. Equal - a subscriber has this exact country name in the Country field.

“UNITED STATES”, equal, “UNITED STATES” = True
“UNITED STATES”, equal, “UNITED KINGDOM” = False

2. Not equal - a subscriber has a different country name in the Country field or this field is blank.

“UNITED STATES”, not equal, “UNITED STATES” = False
“UNITED STATES”, not equal, “UNITED KINGDOM = True

Field type - date

Date - this field should be filled in with a date, a month and/or a year.

The date format can be changed in the User Profile.

There are two fields -“Birth date” and “Registration date” - by default. But a user can create also the unlimited number of custom fields.

These are operators for date segmentation:

1. Equal - the date field value in a subscriber’s profile is equal to the value specified by a user.

2. Not equal - the date field value in a subscriber’s profile is not equal to the value specified by a user. If the date field is empty, a subscriber will be filtered into a segment anyway. If that’s not preferred, please use the “Exist” operator and the “And” condition.

3. Greater than/less than - filters subscribers by date greater or less than it is specified in a condition.

4. Exist/not exist - checks the existence of a value in the date field (if there’s a value in the field or if there’s not at all).

5. Date within/in a range - the date range is determined by the left and right date fields.

6.1. Month is equal/not equal - this operator selects or excludes dates congruent to the matched month value.

6.2. Current month - this operator selects a month equal to the current month value. Every month the segment will be changed automatically in accordance with the current month.

7.1. The day [x] days before - a date equal to [x] days before the current.

7.2. Later than [x] days before the current day - a date later than a certain day before the current day. For example, if July 15, 2016 is the current day, and [x] = 10, the segment will contain all dates from July 6, 2016 and all the following dates.

7.3. Earlier than [x] days before the current day - a date earlier than a certain day before the current day. For example, if July 15, 2016 is the current day, and [x] = 10, the segment will contain all dates from July 4, 2016 and all the previous dates.

8.1. After [x] days from the current day - a date equal to the current day plus [x] days. For example, if we the current day is July 12, 2016, and [x]=2, the segment will contain all dates from July 10, 2016 and all the following dates.

8.2. Later than [x] days after the current day - all dates later than the current day plus [x] days. For example, if we the current day is July 15, 2016, and [x]=10, the segment will contain all dates from July 26, 2016 and all the following dates.

8.3. Earlier than [x] days after the current day - all dates earlier than the current day plus [x] days. For example, if we the current day is July 25, 2016, and [x]=10, the segment will contain all dates from July 24, 2016 and all the previous dates.

9.1. A day of the month equal/not equal - the segment includes/excludes dates with the matched day value.

9.2. A day of the month later/earlier than [x] - this operator uses strict inequality. For example, if [x]>15, the segment will contain all dates from 16 to 31. If [x]<15, the segment will contain all dates from 14 to 1.

9.3. A day of the month equal to the current day - the segment includes a date with the matched day value. Every day the segment sorting will change.

10.1. A day and a month equal/not equal - the segment includes/excludes dates with the matched day and month values.
For example, January 1 - not equal - January 2.

10.2. A day and a month later/earlier than - this operator uses strict inequality.
For example, July 15, 2016 > July 14, 2025. And August 1, 1990 > July 15, 2016.

10.3. A day and a month are equal to a subscriber profile field value of the current day. - A day and a month should be equal to the current date. Every day the segment sorting will change.

Field type - tag

Tag - is a list of strings separated by commas.

This field can be filed in with different values separated by “,” “|” and “;”. A tag itself shouldn’t contain such symbols.

There are segmentation operators and two API methods for this field: API add tags and API remove tags.

Operators for the tag segmentation are:

  • Please note, that tags are case sensitive.

1. One of - this field contains one of the listed tag. * Subscriber - TagField - “x”, “y”, “z”
* Condition - TagField - one of - “a”, “y”, “z” = True
* Condition - TagField - one of - “a”, “b”, “c” = False

2. None of - this field contains none of the listed tags. * Subscriber - TagField - “x”, “y”, “z”
* Condition - TagField - none of - “a”, “y”, “z” = False
* Condition - TagField - none of - “a”, “b”, “c” = True

3. All of - this field contains all the listed tags. * Subscriber - TagField - “x”, “y”, “z”
* Condition - TagField - all of - “x”, “y” = True
* Condition - TagField - all of - “x”, “b” = False
* Condition - TagField - all of - “x”, “y”, “z”, “w” = False

4. Not all of - this field should not contain all the listed tags. * ubscriber - TagField - “x”, “y”, “z”
* Condition - TagField - not all of - “x”, “y” = False
* Condition - TagField - not all of - “x”, “b” = True
* Condition - TagField - not all of - “x”, “y”, “z”, “w” = True

5. empty/filled in - this field contains any value or it is empty.

6. exist/not exist - the field exists or doesn’t exist in the subscriber’s profile.

Field type - boolean

The boolean field type has two values: True or False.

Boolean has two unique operators for segmentation:

1. True - a value in the field is equal to True
2. False - a value in the field is equal to False

There are special toggle switchers for this field type in the subscription manager:

George Boole is an English mathematician and logician. He is known as a founder of mathematical logic - a subfield of mathematics exploring the applications of formal logic to mathematics.

Field type - IP

There are two IP fields as default:

1. Reg IP address - this field is filled in automatically when a subscriber clicks signup link in the opt-in letter.

2. IP address - this field is filled in automatically when a subscriber clicks a link in a letter.

A user can create custom IP type fields.

Use a search by a subnet mask for the deeper segmentation.

1. Equal - search for IP addresses from the specified subnet.

For example, “IP equal to 127.0.0.125” means IP addresses from 127.0.0.1 to 127.0.0.126

2. Not equal - search for IP addresses the specified subnet doesn’t contain.

For example, “IP not equal to 127.0.0.126” means IP addresses from 127.0.0.63 to 127.0.0.254

To search for a certain IP address from the IP range, unite two rules under the “AND” condition.

For example, “IP equal to 127.0.0.125” and “IP not equal to 127.0.0.126” build a range of IP addresses from 127.0.0.63 to 127.0.0.126.

Try this website to calculate IP/subnet: http://ipcalc.nmonitoring.com/

Field options: Default value

A user can set a default value when creating or editing a List.

Thus, empty fields in the subscriber profile will be filled in with the default values set by a user when importing.

#Field options: Make the field required

The user can make all the fields or several of them required when creating or editing a List.

If a required field in the subscriber’s profile is empty, the user can’t add the subscriber to the List.

The subscriber can’t delete these fields from the Subscription manager.

! A subscriber API and File import is available if the required field is filled in with the default value.

{"Email" "forest.beaver@mail.fb",
 "FirstName": "your default first name"}

Please note, that required fields values can’t be deleted.

Field options: Add to the subscription manager

When creating or editing the List a user can make all or several List fields visible in the Subscription manager for subscribers.

A subscriber can change or delete the fields values by himself.

A subscriber can’t change or delete required fields values even those with the default values.

Email Settings

Email Settings - contain 4 fields for email address, sender name and feedback:

From Name - a name visible to subscribers in the Inbox.

From Email - an email visible to subscribers in the Inbox.

Reply-to Name - a name for the feedback.

Reply-to Email - an email for the feedback.

If the “Reply-to” fields are left empty, they will be filled in automatically with the sender details.

Edit a List

To edit a List open the Lists page (Subscribers tab > Lists), choose a List and click on the Edit button on the right.

You may also use the searching bar to find the needed List by a name or id.