How it works
1. Tracking the user behaviour
When a customer visits your site or shop, he or she leaves various traces. He looks at products of certain categories, he reads blog posts or he orders something. All this information is tracked.
2. Create user segments
Based on the tracked information, visitor segments are created. A visitor can belong to more than one segment. eCommerce examples of segments are, for example, “Customers who have bought something in the last three months” or “Customers who frequently use vouchers”.
3. Create personalized content
In the last step you use the segment information to create personalized content. For example, certain segments can be targeted with advertising.
To make it as easy as possible for you to create an awesome user experience for your customers. We provide to tools, the Experience Platform and the Experience Manager.
On the one hand there is the Experience Platform. This is basically a database for events. Additionally it offers the possibility to determine user segments based on these events.
The Experience Platform is implemented as a Java application and currently needs to be hosted by yourself.
On the other hand, there is the Experience Manager. This is the WordPress plugin and integrates the Experience Platform into WordPress.
Additionally there is the possibility to create user segments. Such a segment can be, for example, “someone who has looked at articles of a certain category frequently” or “someone who has bought at least 2 times in the last 6 months”. These segments are transferred to the Experience Platform.
The segments can then be used in the different integrations to create content to be displayed only to specific audiences.
For example, there are integrations to the Gutenberg Editor and Elementor PageBuilder to restrict blocks and widgets to specific audiences. Integrations in PopupMaker and AdvancedAds allow messages to be delivered for specific segments only.
How does the tracking works
Experience Platform basicaly tracks events. Each event has a user, a visit and a request id.
The user id has a life time of 365 days. That means, if a customer does not become active within these 365 days, the ID expires and on the next visit the customer is identified as a new user.
The visit id on the other hand has a life time of just one hour. So if a user is inactive for one hour, the next visit will be handled as a new visit.
The request id is has the shortest life time of just three minutes.