You can view summary information on the database size, as well as statistics on contact additions and deletions in “Database Size Statistics”. To do this, on the main page, click the “Contacts” tab. The familiar page with all saved logic will open.

You can also click on the number of contacts after the greeting — the link looks like “Total in the database … contacts” and leads to the full statistics page.

In the table, statistics are grouped by month. Inside each month, days and the methods of addition or deletion used on those days are displayed. If your tariff depends on the contact volume, the account cost is calculated based on the maximum number of contacts for a calendar month. In the database volume table, the row with the largest excess will be highlighted — it determines the payment.

What counts as an addition:

• Contact import
• Additions via pop‑up, API, and other methods
• Restoration of previously deleted contacts

What does not count:

• Updating existing contacts via import or API — is not considered an addition and does not affect billing
• Consecutive deletion and addition of the same contact — does not increase the total database volume (+1, -1, +1, -1, etc.)

How data is grouped in the table:

All operations of the same type and source on the same day are combined into one row with a total value. For example, if you performed two imports in one day — for 10 and 20 contacts, the table will display one row: “Import of 30 contacts”. Additions from one pop‑up or one IP address are grouped according to the same principle.

Let's consider the billing logic with an example:

We start with an empty account. Beginning on 1.01, we work according to the table below.

For January, 6500 contacts will be charged even though there are only 100 contacts in the account as of 31.01.
The maximum base on 01 February is equal to the current base - 100 contacts, the process is repeated.

You can add a contact to the enKod platform in any of the following ways:

• Adding a single contact manually
• Import - manual or automatic import of contacts in the service
• API - methods for adding a single contact or several contacts
• Pop-up - contacts received from the collecting pop-up on the site
• Subscription to Web-Push notifications - permission to send push notifications on the site
• Subscribe to Mobile-Push notifications - permission to send push notifications in the application
• Tracking - adding contacts from web forms on the site, adding when ordering and other tracking methods that are set on the site
• Test sending - in case a contact has not been added to the account before
• Transaction - sending a message via API without previously adding a contact to the service
• Sending to contact list - loading csv file with contacts at the Recipients stage in the Message editor
• Restoring contacts

To add a contact to the platform by import or via API, it is necessary to specify at least one of the identifiers - email or phone number. In this case, the format of the email address record should correspond to the structure, and the format of the phone number record should correspond to the structure. this structure, and the format of the phone number record - to the standard.

If you do not want to exceed your current limit, but are worried that you may accidentally upload too large a file or not control the addition via API, then in the settings activate the restriction on importing contacts.

The list of contacts is available in the enKod menu tab.

Contact removal is a tool to optimize the size of your contact database, allowing you to stay within your monthly rate limit and avoid charges for exceeding it.

. A contact can be removed in any of the ways listed below:

• Manually - from the contact card
• Import - by uploading a .csv file
• Segmentation - Actions → Delete contacts
• Scenarion (finishing block) - selecting the “Remove contacts” option
• API - “Remove contacts” method

Contact merging is one of the most important features of any CDP, enabling automatic deduplication. By using merging mechanisms, a single, accurate and complete profile of each customer is created, and messages sent will not be duplicated for the recipient. In enKod, it is acceptable to have a unique email address, phone number and CustomID for only one contact at a time. In case of disputes, strict contact merging rules described below apply to prevent duplication:

• Import, tracking methods (script), API methods (not including sessions)
• Pop-Ups
• Working with session (outside pop-ups)

On the Contacts page you can find users through a quick search by email or phone number.

The list of contacts is sorted by default by update date.

The “Channels” column displays for each contact the fact that it has one or another identifier and the fact that it subscribes to a mailing group for this channel. There are three options for displaying the channel:

• Empty - the contact has never been subscribed to any mailing group for this channel;
• Inactive channel - the contact has been subscribed to a mailing group for this channel, but is currently unsubscribed from all groups of this channel;
• Active channel - the contact is subscribed to at least one mailing group on this channel.

You can export contacts from a list or from a segment. When exporting, you can select the contact fields that are required in the export.

If you click on a contact in the contact list, the contact card (profile) will open. Here you can see all the data known about the user: name, phone number, registration date, traffic source, interaction channels, activity and others.

We would like to draw your attention to the “Communication Channels” section, in which all available communication channels with a particular contact are highlighted in blue, and the unavailable ones - in gray. In order for a channel to be defined as available, two conditions must be met at the same time:

• the contact has a channel identifier (e.g., email address, phone number, etc.)
• a corresponding mailing module is connected in your account (e.g. email, sms, WA, etc.).

The Email channel can have additional display versions:

• orange - if a contact has an email, but it is in the local blacklist (for example, it was added by you manually at the request of a client), it is not allowed to send emails to it. The channel will become active again if the email is removed from the local blacklist
• red - if a contact has an email, but it is in the global blacklist (the contact gets there automatically after hard bounces; usually it means that such email addresses do not exist), it is forbidden to send email messages to it.

If necessary, you can edit the values of data fields, email, phone number, first name and last name. You will be notified about all actions by events in the contact card, where it is indicated how and who made the changes.

In addition, if user activity tracking is enabled, the contact card will display the events that the user has performed on the site: page views, interaction with products (additionally, lists of products currently in the contact's cart, favorites and comparison are available), orders, and more. Read more about tracking in this section of the knowledge base.

For cart, favorites and comparison you can view:

• date of update (last content change)
• product data (image, price, link, etc.) from product feed
  • if your account doesn't have feed configured - only product ID and quantity will be displayed.

If you have [en:user_guide:tracking:multiple_carts_and_favorites| multiple baskets/favourites]] functionality configured - they all will be displayed in the card.

In the contact card you can also view all mailing groups attached to the contact, unattach unwanted ones or add new ones.

A contact can have his time zone defined. Currently, the time zone is detected and recorded in the contact card automatically by tracking:

• the time zone is requested each time the contact visits the site (by session):
  • is initially recorded when a session is created;
  • updated/changed if the time zone defined during a new visit to the site was different from the one already recorded in the contact card;
• if a contact has several sessions with different time zones, the time zone with the most recent time zone request date (the most recent visit to the site) will be recorded in the contact card;
• the time zone is strictly bound to the session, so when merging contacts, the time zone is retained by the contact that still has the session or is transferred to the contact to which the session is bound;
• when a contact is deleted and then restored, the time zone is also restored, because the session is restored as well.

Tracking can automatically detect and record time zones in formats accepted in the IANA time zone database, which is supported by all modern operating systems (Windows 10, 11, Linux, MacOS, IOS, Android).

If a contact uses a non-IANA-enabled format to specify a time zone, the time zone for that contact cannot be defined and entered into the contact card.

The contact's time zone can be taken into account when sending scheduled messages.