This section is mainly for UI developers and introduces the concept of upsell from a technical point of view.
In short: End user have a set of so-called capabilities. UI, however, offers functionality beyond that limited set for promotion purposes e.g. inline links, that require missing capabilities, trigger an in-app upsell. This process leads to a trial period or a new subscription.
Technical challenge for the UI developer is to check what the end user has, what can be shown beyond that, and how to handle upsell. It is also possible for hosting companies to easily integrate their own online shop since the internal mechanisms are loosely coupled via events.
In order to configure upsell server-side, create a new file
upsell-appsuite.properties or append to existing file
appsuite.properties (mind the double-slash; this is not a typo!).
If you configure upsell in the
upsell-appsuite.properties, the properties are loaded when you trigger the live reload function.
Each line enables a specific capability for upsell. That means whenever a feature misses one of these capabilities, a special upsell related event is triggered.
Note: For simple demo purposes, you can enable an internal upsell configuration by appending &demo=upsell to the URL and reload the specific page.
When implementing cross-/upsell trigger, tracking should be integrated at the same time in order to analyse performance.
The Metrics module provides a very flexible and extendible way to track user behaviour and conditions within OX App Suite.
Upsell can be tracked via the specific events.
For more information see trackevent.