Breadcrumbs

Blog from July, 2018

The total line in Webtrekk Analytics now features improved calculation logic. Instead of adding up all lines of an analysis, the sum is "unique" depending on the metric, i.e. multiple counts, e.g. of visits and visitors, are combined.

Pivot lists now also have a total line in which this new calculation logic is applied.

The roll-out of this functionality will take place step by step across all Webtrekk accounts and will be completed within the next few days.


Example

In an analysis with the dimension "days" and the metric "visitors", a visitor who visited the website on three different days was previously shown with the value "3" in the sum of the analysis. With this new calculation logic, the multiple counts have been combined so that this visitor is shown with the value "1".

The total line is now called "Total" (previously "Sum").


Note that under certain circumstances, the conventional calculation will still be used instead of the new calculation. The footer will then show "Sum" instead of "Total".
This can occur if the analysis includes customer journey metrics or is sorted by "ID" dimensions ("Session IDs", "Order Number").





Release date: August 01, 2018


In favor of an optimized visualization of charts, we have introduced a new color palette.


Release date: July 26, 2018

It is now even easier to evaluate the sparklines at a glance because you can set the following visualization options:

  • Normalize
    When normalization is activated, all y-axes of the sparkline start at the same minimum value and end at the same maximum value.

  • Show absolute number
    In sparklines, absolute numbers are displayed by default. You can deactivate these numbers for more space in the sparkline.



Example: "Normalize"-option

The “Normalize”-option is not activated:

If you do not look at the numbers, all sparklines seem to have the same values.


The “Normalize”-option is activated:

You can now clearly see that page views for other cities are significantly lower than for Vienna.

Release date: July 26, 2018


Previously, long titles were not completely displayed in the navigation panel on the left side and in certain diagram types (pies, pyramids, and funnels).

With this improvement, they are now completely readable as soon as you move the mouse over the relevant title.


Release date: July 26, 2018

It is now possible to map processes when you copy reports across accounts.

If the original report uses processes there will be a check if the same process exists in the target account:

  • If there is an identical process (configuration and name) it will be mapped automatically.
  • If no, there will be another check if a process with only the same name exists. If this is the case, you are asked to use it or create a new one.


Documentation: Copy Reports across Accounts


Release date: July 26, 2018

While migrating reports from Webtrekk Q3 to the Webtrekk Suite, reports containing A/B comparison are now considered.

The following restrictions must be observed:

In cases a report cannot be migrated, because, for example, a used segment does not exist anymore, or a dynamic time range was used, which is not yet available in Analytics, the migration process will be canceled.


Release date: July 26, 2018


In the Metric and Formula Editor, you can define the number of decimal places for your own metrics and formulas. In the analysis, you can now specify a different value if required.

This setting option also makes sense for metrics whose values are recorded via parameters. A standard value of two decimal places is now defined for these metrics, which can also be adjusted accordingly in the analysis.

This setting only affects the PDF export. If you export the analysis as an Excel or CSV file, the decimal places are exported as specified in the standard value.



Release date: July 02, 2018


To make a table even easier to read, the table rows are alternately colored.


Release date: July 02, 2018

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


The improved device detection has been running in the background since March 29, 2018, parallel to the old device detection. Since July 2018, the improved device detection has also been used for analyses in Webtrekk Analytics.

The effects of the improved accuracy in hardware identification can be observed very well in the analyses in calendar week 13 – from this point on the new device classes are filled with data and you will see the already mentioned shifts in traffic distribution. As a rule, this ensures retroactive deviations in the single-digit percentage range.


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 FunctionsDescriptionCustomer'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.
  • New devices are instantly detected and recognized at first request or user agent hit.

  • Better convergence with the technical service provider for device detection.

  • Scalable if there is a need to add more device attributes in the long run.

Device Naming

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:

  • Vendor name + device model (e.g. Nokia 8400)
  • Vendor name + device family (e.g. Samsung Galaxy S7)
  • Vendor name + operating system (e.g. iPhone OS 10)



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:

  • any Android
  • any iPhone
  • any iPod
  • any iPad
  • any HbbTV
  • any Desktop & Laptop

Before/ After Mapping Table

BEFOREAFTER
Fallback NameDevice ClassFallback NameDevice Class
Diverse PC & LaptopDesktopany Desktop & LaptopPC/ Laptop
Other AndroidSmartphoneany Androidunknown
iOSSmartphoneany iPhoneSmartphone
iPhoneSmartphoneany iPhoneSmartphone
iPhone OS XSmartphoneany iPhoneSmartphone
iPodSmartphoneany iPodother
iPadTabletany iPadTablet
HbbTVTVany HbbTVTV


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.


Device Classes

The following device classes have been introduced:

  • Console
  • E-Reader
  • Mediahub
  • Smartwatch
  • Other (for the ones that do not match these classes)

The new device classes provide a useful addition to the already existing classes:

  • PC/ Laptop
  • Smartphone
  • Tablet
  • TV

The device class "Unknown" is still in use.

By adding these device classes, more granularity in device class analyses is enabled.

Device Properties

Unused device properties are no longer supported.

The following device properties are no longer supported:

  • MOBILE_CONNECTION_TYPE
  • WIFI
  • POINTING_METHOD
  • HAS_QWERTY
  • WAP_PUSH_SUPPORT
  • XHTML
  • COLORS
  • COOKIE_SUPPORT
  • FLASH_LITE


Aggregation

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:

  • Device model
  • Device familiy
  • Device name

The above dimensions have been added to take advantage of the improvements in the new device detection.

In the Webtrekk Support Center, you will find the FAQs for the new device detection: FAQs Device Detection.




Release date: July 02, 2018