Breadcrumbs

Blog from April, 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).


Example


PageDuration (sec.)Comment
1180

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

2120

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

3150

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


The documentation for TV Analytics is now available.

With Webtrekk TV-Tracking you can identify and visualize the direct influence of TV advertising on your website presence and conversions. With the data-based knowledge about the relationship between TV usage and website traffic, you can optimize your cross-media marketing campaigns in a targeted manner.

TV tracking is made possible by assigning Internet visitors who become aware of your company or product through television advertising to a particular TV spot. The TV-induced traffic on your website is determined by using elaborated algorithms: Based on the binding broadcast times recorded in real time, analyses are carried out of all visitors who visit your site within a defined period after the TV broadcast or who have used a search with specific keywords defined by you beforehand. Relevant visitor numbers are calculated from the increase in website traffic after the TV spot has been broadcast compared to traffic before the broadcast.


This document contains the instructions for correct setup and shows you how TV tracking works and how to use it.

Documentation: TV Analytics


Publishing date: April 1, 2019