Nobody wants to stand in front of a landmark and google it for a long time (if one knows at all what to google). Selecting checkboxes for the right language is just as cumbersome as landing on the home page of the tourism destination.
If you want to know something specific, then immediately! Nobody has time and patience on the phone. Either it goes fast, or the user is away, before he arrived.
For this purpose, xamoom has firmly integrated locations and objects into its location CMS. This ensures that the right information is always delivered in the right place and in the right language. If so, the user is offered exactly the information he needs – and even before he knows he needs it. In order to spread such information as widely as possible,
- our customers use smart labels with QR and NFC,
- allow their users the geo-search (“nearby”) in the mobile portal or
- send iBeacon notifications (based on allowances of the app user) to their device.
The right information is distributed in the right place in the right language. But there is more than just a location or object specific context. For this reason, we finished our context engine this summer.
As before, specific information will be displayed in individual locations. However, it may be that time requires a different context (breakfast, lunch or dinner). Likewise, at the point of sale, varying information is needed than at home when using a device. Children want to be addressed differently than their parents.
All these and many other applications can be implemented with the context engine by xamoom – in the mobile web as well as in apps.
1. Time based content
The simplest use case for this technology: Prewritten menus for different times of the day. Different content could also be served depending on the season or the weekday. How about an invitation to a free coffee during the opening hours and a simple contact form when the car dealer has closed? Doable within minutes!
2. Role based differentiation
Children have very different information needs than parents. A museum or a themed walk there could offer two modes: a more playful children’s mode with animations and comics and a dad mode.
How about displaying different content for members and non-members? Non-members could be persuaded with a voucher to participate, while members see the number of loyalty points they have already collected.
Another example is maintenance. A small form for data entry is displayed to the cleaning staff (can not be manipulated by using iBeacons). The supervisor receives a control view of the data.
3. Triggers from CRM systems
A personalized app can be aware of the user’s preferences. If the person is at the main square and searches for a nearby experience, the smartphone can send him either to the museum or to a yoga class.
Or you can give different offers for different loyalty points.
4. Point-of-sale and digital manuals
Imagine a man who wants to buy a drill. The QR code on the packaging holds (with xamoom) not only 33 different language versions. He can also check whether the buyer is still in the shop or is already at home.
If an iBeacon is in range or the geofence still points to the proximity to the shop, there’s point-of-sale content being shown (data sheet, advertising video etc.). At home, the QR code becomes the portal for the digital manual, which also offers the simple ordering of consumables (targeted upselling).
5. Competitions, quizzes and scavenger hunts
A zoo app contains a quizz. In this case, the context is “quizz mode”. If the question is: “Which animal lives in Africa? A lion or a polar bear? “, the participant has to go to the lion’s cage. There, not only is the pedagogically valuable content is being displayed, but the app also congratulats the participants and the next question is being displayed.
This way you can have any scavenger hunt or geographically settable quizz.
Click, click, context
Using xamoom’s context engine is easy: You first select a default page for the spot (location or object), which is displayed if no other condition is met. Then you set up the conditions for certain pages.
As shown in the example above, the condition is that the “121 | Young Roses” page is displayed between 06 and 09 a.m. The variable name x-datetime is understood by all our mobile web clients, the SDKs and apps. Otherwise the names for variables can be assigned freely for own developments.
As data types, developers can use across our software development kits (SDKs) and programming interfaces (APIs) TIME, DATETIME, NUMBER and STRING, as well as operators of Boolean algebra to integrate this logic into all kinds of applications.
The more you get involved in the many different situations of the customer, the better. Especially in digital marketing or in e-commerce, every second matters.
Want to test it?
As mentioned earlier, at least one variable (x-datetime) is already available in all clients. Therefore, you can test this feature yourself. How? Simply order a free xamoom demo system. Have fun!