Pavel Jiřík Kentico Software

Kentico 11 has been out for some time, and many new projects are already running on the latest addition to the Kentico family. At the same time, many instances running on older version(s) of Kentico have been upgraded to the latest one. This involved some upgrade considerations, one of them being the changes in Kentico 11’s Email Marketing.

This is a last part of the three-part miniseries (here are the first and second article) focused on wrestling  GDPR and data protection through Kentico 11 editions. We covered consents and their management, continued to the challenges stemming from dealing with the consent agreements, and have finally arrived at exploring the topic of GDPR rights.

In my previous article, I explored the challenges related to data flow mapping, storing the content of consents, and website tracking. In this second part of the three-part series, I am going to have a look at challenges related to newsletters, user registrations, and online form submissions. So, get yourself a cup of coffee, and let’s dive into it!

It is definite. Spring 2018 is going to be in the name of GDPR preparation for many businesses interested into doing EU business. Mapping the data flow, last minute collecting of consents, exploring the deep waters of the data-collecting ocean, and ensuring enough coffee supply for their teams to make it through on time. With Kentico 11 release, however, the preparation for GDPR (or any other data protection regulation) can be much easier and streamlined.

When using email marketing in Kentico, the tracking capability plays a significant role in the whole marketing process. Kentico allows you to track opened emails, clicked links, unsubscription rate or contact activities. The information can then be used elsewhere in the system - e.g. for marketing automation or contact segmentation.

When your database is very large, and you suddenly enable the deletion of inactive contacts (Settings application -> On-line marketing -> Contact management -> Inactive contacts -> Delete inactive contacts), the scheduled task responsible for the deletion may result in a timeout as it tries to delete all inactive contacts at once.

Sometimes, you may need to delete an automation process, even though it contains many contacts. For example, when you realize that the process is wrong or not needed anymore as it was only a test.

Sometimes you have a snippet of the HTML code or a longer text that you wish to use multiple times on your site. By default, Kentico contains the Localization application that allows you creation of custom resource strings. However, this is intended more for multi-culture sites. Therefore, I would like to show you how to create such a module from scratch.

Sometimes, when deleting inactive contacts, you may receive a constraint error similar to these ones:

If you track web analytics statistics over a long period of time, your database can become really large. To maintain database performance and size, you may eventually get to the point where you need to delete old web analytics data. In Kentico 9 this is not possible to do in the admin interface anymore but as always you can easily achieve this by using our Kentico API.