Open personalization with Apache Unomi in the GDPR era

Personalization: Go or No?
In the era of consent, privacy and GDPR it may no longer seem acceptable to do behavioral personalization.

Personalization doesn’t have to be an Evil Big Brother
Personalization is proven an effective way of increasing engagement. As a visitor, you feel understood. It leads to better user experience and higher conversion, as long as it’s done in all trust and consent.

In recent years many software companies were created to deliver these highly contextualised experiences but none of them really delivered the necessary trust so that you could use the technology in the same way you are using Drupal.Drupal is yours to take. It is your responsibility to use it wisely. Apache Solr is also yours to take. In combination with Drupal it’s highly powerful, and yet - at all times, all your customer data remains in your hands only.

Apache Unomi
Welcome Apache Unomi, the new kid in town of customer data management and personalization. Nick will explain how Drupal, Mautic and Apache Unomi can be seen as a Digital Experience Platform without lock-in, without handing over your data to an external software vendor.Bonus - This also works in a fully decoupled architecture, as long as you keep using the Drupal core access systems.

Decoupled Architecture & Personalization
I'll show a case that is fully decoupled and still uses paragraphs to render content. This site uses graphql to fetch the content and then renders this in React.

Existing Ecosystem
Drupal Module: https://www.drupal.org/project/unomi
PHP Library: https://gitlab.com/dropsolid/unomi-sdk-php
JS Library: https://www.npmjs.com/package/unomi-sdk-node
General Apache Unomi Documentation: https://unomi.apache.org/

The session also includes a technical deep dive into Apache Unomi, how it can be used to deliver highly personalized experiences, compliant with the GDPR regulations and with respect to users trust.

*Session Materials*