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.
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 (firstname.lastname@example.org).
Publication date: 03 July 2019
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).
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
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.
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).
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 Content Engagement Plugin in Tag Integration
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:
Audience REST API
Recommendation REST API
Publishing date: June 06, 2019
Under the following link, you also have the opportunity to download the plugin ("webtrekk_adBlock.min.js").
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.
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.
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
You will find the latest documentation under this link:
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
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:
Furthermore, only parameters that differ from the default value are sent. This affects the following parameters: