Uniform partners with Kentico Kontent to enable the fastest personalized sites possible
Due to high demand Uniform has made an integration between its Uniform Optimize product and the Kentico Kontent CMS. The integration allows content editors to tag content items as variants for personalization. Find the custom element in the Kentico Kontent plugins gallery or read the Uniform documentation.
The philosophy behind Uniform Optimize is based on this simple paradigm:
Visitors to your site have an intent, something they want to accomplish. A reason for their visit.
Personalization aims to make it as easy as possible for the visitor to accomplish their intent. With Uniform Optimize, you can build up a real-time intent profile of every visitor and use this profile to make personalization decisions.
Uniform identifies a visitor's intent by signals that they send. Signals cause a change of the visitor's score in a specific intent. Signals can be behavior (visiting pages), a predefined cookie, events like adding something to the shopping cart or a query string from a marketing campaign.
The Uniform integration with Kentico Kontent allows the content editor to tag content with "intent tags" so it can later be used for personalization. These intent tags are configured within the Uniform Optimize dashboard and become available in the Kontent CMS through the custom Uniform field.
To make personalization work within the data model of a CMS, a wrapper "personalized" component is created and within this component all personalization variants of the component are referenced.
When a user visits a specific page that has behavior tracking on it, Uniform tracks this user and remembers the intent. Let's say the homepage has a personalized hero component. When the user returns back to the homepage, the hero component now shows the hero variant that is tagged against the intent of the user.
Uniform's Personalization component receives the variants for personalization, it checks the intent profile and its scoring and will then render the right variant for the user.
Everything happens on hydration and no API calls have to be made. We like to say: "Look ma, no origin!" Everything happens statically on the CDN edge.
First things first
Create a component data model for the element that is a personalized variation. In this example we are creating a hero component. Add the integration field as a custom element and within it add the URL and the API key.
Add any other fields you want the hero variation to have.
Now that the data model for the hero variant has been created, create the data model for the component that holds the variants. This component only needs a field that can reference hero components.
With these two data models in place it is now possible to create a page with a personalized hero and within that add multiple variants that are tagged for personalization.
If you open up the developers banner you'll see the selected intent tag as follows: