Segments are dynamic filters that are relevant “here and now”. They are applied to contacts directly at the moment of interaction with a user - sending a message or showing a pop-up window.

Segmentation capabilities allow you to show more relevant content to your subscribers. With the help of segments you can combine contacts or split them into smaller parts, highlight the most active users, as well as use a strategy of IP address warming strategy.

Two types of segments are available in enKod - for messages and for pop-ups. Segments for pop-ups cannot be counted, as they run on the site in real time.

On this page you can see the list of existing segments and create a new one.

If you click to edit a segment, you will see information about it: the conditions of display (a set of specified filters), as well as the number and list of contacts matching the conditions of the segment. Here you can edit or delete the segment.

Contacts in the segment are divided into tabbed channels. The number under each channel shows how many people from that segment have that particular field, including the emergency contacts on that channel.

The “All Contacts” section displays the full list of users, including those who are in an emergency on any of the channels.

The list of contacts from a segment can be exported as a .csv file by pressing the corresponding button.

If there will be more than one selection condition, you need to choose how the system should check these conditions: “Users get into the segment if all conditions are fulfilled” will mean that the selection conditions must be fulfilled at the same time. “Users get into the segment if any of the conditions are met” means that at least one selection condition must be met.

Use the “Add Condition Group” button if you need an additional condition branch with a separate validation rule. This is useful if the condition validation rules are different. For example, this segment will select users who have been sent at least 5 emails in the last 5 months and have opened at least one email, or users whose “Email” field is not empty and who are subscribed to the “All Subscribers” newsletter.

For some conditions of groups by messages (sends, opens, clicks, errors), by subscription date, by page visits enKod provides subconditions by event time. Below we describe in detail what exactly time indicators are taken into account in these subconditions and how they are counted.

Exactly n seconds ago - the interval within one second is taken into account

If it is 12:40:10 and the condition is “exactly 5 seconds ago”, then contacts with the event time 12:40:05 are suitable.

Exactly n minutes ago - only minutes are counted

if it is 12:40:10 and the condition is “exactly 5 minutes ago”, then contacts with event time from 12:35:00 to 12:35:59 are eligible.

Exactly n hours ago - only hours and minutes are counted

if it is 12:40:10 and the condition is “exactly 1 hour ago”, then contacts with event time from 11:40:00 to 11:40:59 are eligible.

Exactly n days ago - only days are counted

if it is any time 22.02 and the condition is “exactly 2 days ago”, then contacts with the event date from 20.02 00:00:00 to 20.02 23:59:59 are eligible.

Exactly n months ago - only the date and month are taken into account

if it is 22.02 and the condition is “exactly 1 month ago”, then contacts with the date of the event from 22.01 00:00:00 to 22.01 23:59:59 are eligible.

Exactly n years ago - only year, month and date are taken into account

if it is 22.02.2023 and the condition is “exactly 1 year ago”, then contacts with the date of the event from 22.02.2022 00:00:00 to 22.02.2022 23:59:59 are eligible.

So the logic is as follows:

• for seconds - second to second
• for minutes and hours - time within a minute
• for days, months and years - time within a day.

• Field
• Mailing group
• Subscription date

Both basic fields (“Email” and “Phone”) and manually created data fields can be used for segmentation conditions.

How the operators for conditions by mailing list group work:

• equals - contacts that are subscribed to each of the specified mailing groups will be selected (selecting multiple groups works via logical AND)
• not equal - contacts that are not subscribed to any of the specified mailing groups will be selected (selection of several groups works through logical OR).
• one of - contacts that are subscribed to at least one of the specified mailing groups will be selected (multiple group selection works via logical OR).
• none of - contacts that are not subscribed to any of the specified mailing groups will be selected (selecting multiple groups works via logical AND).

For example, if you need to select contacts who are not subscribed to any mailing group, use the “none of” operator and select all mailing groups in the account.

• Sent
• Open
• Clicked
• Delivery errors

• SQL template

Condition selects users according to the conditions specified in the SQL template for segmentation

• Product views
• Adding to basket
• Checkout
• Adding to favourites

This type of conditions is available only if you activate the tracking service, which allows you to track user behaviour on the site. More information about tracking can be found in this section of the knowledge base.

The “Add to cart” and “Add to favourites” groups of conditions work only with the current state of the favourites/cart, i.e. they find only those users who currently have items in their favourites or cart.

Site behaviour

• View current page
• Scrolling the current page
• Visiting pages
• Visiting the site
• Closing a tab

Segments whose conditions are based on user behaviour on the site work only for pop-ups and operate in realtime mode, i.e. only for users currently on the site.

Page address

• URL
• UTM tag

The “URL - by mask” condition works by the following logic: you can use the underscore _ character to match any single character in the page address, and the asterisk * character to match an unspecified number of characters in the link. For example, the following condition will find all contacts whose current page starts with any number of characters, contains the “mysite.com/page_/” part, but has only one any character after the /page part.

In this example, the condition will match users who are on page “https://mysite.com/page1/” or “http://mysite.com/page2/” etc., but not contacts with an address of “https://mysite.com/page15/” or “https://mysite.com/pages1/”

Other

• Device type
• Layout
• Visit history

The layout condition is used to show popups. It allows you to select people who have reached a certain page of the site or a certain element of the page. For example, if we don't want to show a popup to a user who has logged in to the site, we can add the HTML code of the login button to the segment condition.

Note that the condition on site visits will only work if the ekEvents.push('pageOpen') method is set on the site pages. Read more in this section of the manual.

Use this function to limit the number of eligible contacts for a segment. Contacts will be randomly selected each time the segment is recalculated. When sending a message to segments that have limits set, the limit for each segment will be counted individually.

You can attach tags to segments to categorise them and find them more quickly in the segment list. Attaching tags is available in segment editing.

Tags are displayed in the segment list, and you can work with them using a filter.