The new Webtrekk device detection has been completely revised to meet our customers' business needs.
Nowadays, the very rapidly growing range of products and models of the consumer devices presents us with new challenges in terms of device detection. For example, since most websites have over 50% combined mobile and tablet traffic, it is vitally important to get mobile device data (or device detection in general) with precision and with up to date information so that you can have the ability to identify where improvements could be made. These are, for example, targeted campaigns and adapting mobile strategies accordingly.
Webtrekk has not only reworked the underlying infrastructure but has redesigned the Data Processing Pipeline. Our objective is to provide a stable and self-sustaining infrastructure with minimal manual maintenance.
Example: Device Class Analysis in Webtrekk Analytics
In the following, you will find an overview providing the general outline of the status quo, the changes and the impact on the customers' end as a result of the respective change:
|New & Improved Functions||Description||Customer's Benefit & Impact|
Update Process Automated
|The device update process is now automated.||Previously, any addition of new devices requires manual updates and therefore manual work by the development teams.|
Please keep in mind that you may need to update your saved filters based on the changes of device naming.
New device naming convention:
Vendor name + device family
Except for fallback device names, such as "any iPhone".
So far, device names are derived from the following information:
With the new device naming convention, a consistent, coherent and reliable structure is created.
An alignment of old and new device names is given through mapping of old and new naming conventions.
The following list of fallback device names is now applicable:
Before/ After Mapping Table
|The assignment of devices, which are not recognized, is now clearer because fallback names are more informative. This allows a reduced, but a more accurate list of fallback names.|
Analysis of Device Models
|The detection of specific device models is now possible.|
Previously it was not possible to detect specific device models or to analyze devices based on their device family.
No model name will be shown in the device full name; however, we will add a new dimension (device model) within the next releases so that you can add the device model to the data table as a separate dimension for a better drill-down.
The following device classes have been introduced:
The new device classes provide a useful addition to the already existing classes:
The device class "Unknown" is still in use.
|By adding these device classes, more granularity in device class analyses is enabled.|
|Unused device properties are no longer supported.|
The following device properties are no longer supported:
|While aggregation, the dimensions "mobile clients" and "resolution" are not supported anymore. Aggregates containing these dimensions will be removed.||In the long term, the aggregation will be replaced by a more flexible system.|
For customers using "Webtrekk Quick Insights", this means that device data (mobile devices and screen resolution) cannot be shown anymore.
For customers using "Webtrekk Q3", raw data can still be used when available.
New Device Dimension in Analytics
The following device dimensions have been added:
|The above dimensions have been added to take advantage of the improvements in the new device detection.|