With this release, you can expand nodes in a pivot table and save them for future/further use, so that you can see the underlying data in the report/ export at any time directly.
This configuration is saved permanently when you save the analysis as "My analysis" or as a report element. If you then export the analyses and reports saved in this way, pivot tables with the extended nodes are displayed.

Please be aware that the pivot table is displayed fully collapsed after one of these changes:

  • A dimension is removed, changed, or rearranged.
  • The user switches to the pivot list.
  • The extended node is saved position-based, not value-based. So if you expand the top third node, it will be expanded independently from its value.

Release date:

With today's release, customers with a Webtrekk account can ask for the deactivation of the predefined Dashboard view in Analytics as needed. Contact the Webtrekk Support Team for this purpose (

Publication date: 03 July 2019

Analytics: Path Analysis

The Path Analysis is now available for your Webtrekk Analytics account. With this feature, you can visualize your customers' behavior flow as well as conversion paths (customer journeys).

The most important key findings you gain from path analysis include these:

  • Understand on which page your visitors start (landing page) and to which pages they navigate.
  • Gain deep insights into specific content, such as what content was consumed and in what order.
  • Find out if there are typical "reading paths" and which content has the highest exit rates.

Webtrekk Path Analysis enables paths for each dimension that can have multiple values in a user session or lifetime. These include, for example, pages, content groups, products, and actions. You can also use the path view to gain interesting insights into the use of forms, the use of different devices, or campaigns (channels) before an order (customer journey). 

The path analysis can be configured individually, allowing you to restrict the path to the elements, segments, or device classes relevant to you, for example, individual pages in the ordering process.

To open the Path Analysis view, click the new [Path] button. Your confirmation will then perform the calculation.

Example: Path Analysis View

Publication date: July 03, 2019

Android SDK v5 (Beta)

The Webtrekk Android SDK is used to integrate the Webtrekk tracking system into your Android apps. Collect meaningful data about how your apps are used, track how your users interact with your app, how they view specific pages, and custom events. Based on the tracking data from apps different indicators can be measured, which are are already known from the web analytics, such as page impressions, events, screen size, operating system, e-commerce tracking, etc. Especially page impression data or events, and also the number of conversion in the e-commerce tracking are beneficial to draw conclusions for your business optimization.

Concerning the handling, we have focused on the following points: Developers should be able to set up the system quickly and intuitively. Overall, we have reduced the complexity to the optimal level required to ensure flexibility and scalability with high performance.

Documentation: Webtrekk Android SDK v5 (Beta)

Publishing date: July 01, 2019

The Cookie Control extension is available for the Smart Pixel. This plugin allows you to access the properties of Webtrekk cookies. You can perform the following actions for cookies:

  • Assign a new track domain and/ or track ID
  • Switch from a client cookie to a server cookie (first-party cookie to third-party cookie).

Documentation: Smart Tracking Pixel (wtSmart.extension.cookie_control)

Please note that this extension is not free of charge. If you are interested please contact your Webtrekk consultant or

Publishing date: June 12, 2019

Content Engagement Plugin

With today's release of the Content Engagement Plugin, you can precisely measure the reading behavior of your website visitors. Reading behavior analysis data is an important performance indicator, especially for content pages: For example, it is essential for publishers to know how readers deal with a published article. The Content Engagement Plugin measures the percentage of an article read by the end user.

The plugin is available in Webtrekk Tag Integration. Alternatively, you can integrate it into the standard pixel as a separate JavaScript file. For customers who have integrated the Webtrekk Smart Pixel, the extension "wtSmart.extension.content_engagement" is available as standard.

Documentation: Content Engagement Plugin

The Content Engagement Plugin in Tag Integration

Please note that the Content Engagement Plugin does not work for mobile applications and websites with Infinite Scroll.

Publishing date: June 12, 2019

For customers who, for example, use their own tracking domain or third-party cookies due to ITP 2.x, the URI syntax can be adapted to call ressources from the API.

To call the Webtrekk REST API, adapt the URI as follows:

Please note that in this case separate activation is required. Please contact your Webtrekk consultant for this purpose.

Publishing date: June 06, 2019

The updated documentation for the Webtrekk Detect AdBlock Plugin (v1.0.1) is available online.

Under the following link, you also have the opportunity to download the plugin ("webtrekk_adBlock.min.js").

Documentation: Detect AdBlock Plugin (v1.0.1)

Publishing date: May 16, 2019

With Webtrekk Smart Pixel, you can manually pixelate your web pages without the Tag Integration configuration interface, which is part of the Webtrekk Suite. The Smart Pixel is also particularly suitable for the pixelation single-page applications.

The Smart Pixel can also be integrated by developers who don't have any profound experience with Webtrekk because we have reduced the complex implementation structure to the essentials to improve comprehensibility. For this purpose, we have also wholly renewed the API.

Furthermore, the pixel allows the integration of different extensions/ plugins. Webtrekk provides such enhancements, or you can develop them yourself.

Documentation Webtrekk Smart Pixel

Publishing date: May 09, 2019

As of this release we change the calculation for page duration & session duration, so that you get even more precise data.

Until now, the page duration was calculated by comparing the timestamps of a page and its subsequent page. The difference between the two timestamps is page duration. For the session duration, the same logic is applied to all pages during a session. For the last page of a session, a constant value was being used (30 seconds by default).

With this new release, the actions and media requests are taken into account when calculating the session duration and the page duration of the previous page. Instead of just adding a constant value, event and media requests on the previous page are being used to calculate the last page duration.

Please be aware that an additional constant value is still being added by default (30 seconds by default).


PageDuration (sec.)Comment

Time between Page 1 and Page 2: 10:00:00 -> 10:03:00


Time between Page 2 and Page 3: 10:03:00 -> 10:05:00


Time between Page 3 and Action 5 plus the additional constant value: 10:05:00 -> 10:07:00 + 30

The constant value to be added can be configured per account. Default = 30s.

Release date: April 30, 2019

As of this release we have improved our iPhone device detection: the device recognition process now also takes into account the screen resolution specified by the pixel if the detected device is a generic iPhone.

In practice, this means that iPhone models that have the same resolution will be grouped from now on. In your analyses, you will see all models in the same screen resolution grouped.

Example Display in Webtrekk Analytics

With Improved iPhone Detection

Without the Improved iPhone Detection

Please note that we will not make any retrospective updates to the data (as we do not have any information on this), so the analyses dated before the launch date will still be the same as before and will not show any improvement. Only analyses that have subsequent periods (as the rollout date) should have this grouping.

Release date: April 30, 2019

The updated documentation for the Webtrekk Server-to-Server Tracking is available online.

You will find the latest documentation under this link:

Server-to-Server Tracking

Publishing date: April 29, 2019

Today we have released a new pixel version with which you can optimize your tracking. The new pixel version 5.0.9 and 4.4.5 contains the following feature and changes:

  • Request Queue
  • Not supported parameters removed

Download the pixel

Request Queue

Please note that the function is deactivated by default.

Documentation "Request Queue"

The "Request Queue" feature ensures the sequence of the tracking requests in every situation. This gives you the following advantages:

  • Offline tracking
    If this function is activated, all requests are processed 100% in the order in which they were sent. This means that no requests can be lost, even if users go offline (offline tracking). This also applies to the Progressive Web App (PWA) or Single Page Application (SPA).

  • Page unload

    If you have implemented several tracking functions on a single page, for example, form tracking, heatmap tracking, and link tracking, the request queue ensures that all requests created here are sent on the subsequent page when the user leaves the page. Formerly, the browser dropped these requests.

  • Server-side cookies
    Another advantage is the sequential processing of requests from unknown users when you set cookies on the server side. With the new ITP2.1 update, Safari browsers from version 12.1 will not store cookies for longer than seven days. After this period, a returning visitor receives a new EID and is counted as a new visitor. You can avoid this by using server-side cookies. With the Request Queue functionality, Webtrekk can guarantee an unambiguous assignment of the visitor IDs so that the use of server-side cookies does not lead to an unexpected increase in new/ unknown visitors. The request queue ensures that requests are not sent simultaneously and that too many EIDs are generated for a new/ unknown visitor.

    Please note the Best Practice for ITP 2.1. While earlier versions of ITP only blocked third-party cookies, ITP 2.1 will now also block first-party cookies. The storage period for first-party cookies is limited to seven days. To still get high quality data with ITP 2.1, please follow the steps described in the "How to Solution" which Webtrekk make available to you

Not supported parameters removed

The previous pixel version contains many parameters that are actually not in use. As part of the code cleanup we have removed the following parameters that are no longer supported:

  • eor
  • tz
  • ps
  • fvc
  • lvc
  • tmc
  • tmcv
  • tmct
  • cet
  • cst
  • X-WT-TS
  • X-WT-STT
  • ctx
  • csid

Furthermore, only parameters that differ from the default value are sent. This affects the following parameters:

  • fns=0
  • one=0
  • mca=c
  • mut=0
  • vol=0
  • bw=0

Release date: April 04, 2019