Recherche avancée

Sur d’autres sites (6379)

• How to track single-page websites and web applications using Piwik Analytics

  21 février 2017, par InnoCraft — Community, Development

  Single-page websites and web applications have become a standard over the last years. Getting the tracking of such websites and apps right is crucial to your success as you need to ensure the measured data is meaningful and correct. That’s why we, at InnoCraft, help our clients setting up their web tracking and measurement strategy. Some challenges our clients face are the tracking of single-page websites and web applications. We will cover this challenge in this post with a complete example at the bottom.

  Embedding the Tracking Code

  First you need to embed your JavaScript tracking code into your single-page website or web application as usual. To do this go to “Administration” in the top right in your Piwik, click on “Tracking Code” and adjust the tracking code to your needs.

  Tracking a New Page View

  The challenge begins when you need to track a new page view. A single-page app is different from a usual website as there is no regular new page load and Piwik cannot detect automatically when a new page is viewed. This means you need to let Piwik know whenever the URL and the page title changes. You can do this using the methods setCustomUrl and setDocumentTitle like this :

  window.addEventListener('hashchange', function() {
  
          _paq.push(['setCustomUrl', '/' + window.location.hash.substr(1)']);
  
          _paq.push(['setDocumentTitle', 'My New Title']);
  
          _paq.push(['trackPageView']);
  
  }

  Resetting previously set custom variables

  If you have set any Custom Variables in scope “page”, you need to make sure to delete these custom variables again as they would be attributed to the new page view as well otherwise. The following code requires Piwik 3.0.2 :

  _paq.push(['deleteCustomVariables', 'page']);      
  
  _paq.push(['trackPageView']);

  Updating the generation time

  Next you need to update the generation time before tracking a new page view. Otherwise, the initial page generation time will be attributed to all of your subsequent pageviews.

  If you don’t load new content from the server when the page changes, simply set the value to zero :

  _paq.push(['setGenerationTimeMs', 0]);
  
  _paq.push(['trackPageView']);

  In case you load new content from the server, we recommend to measure the time it took to load this content (in milliseconds) and set the needed time :

  _paq.push(['setGenerationTimeMs', timeItTookToLoadPage]);
  
  _paq.push(['trackPageView']);

  Updating the referrer

  Depending on whether you want to track the previous page as a referrer for the new page view, you should update the referrer URL by setting it to the previous page URL :

  _paq.push(['setReferrerUrl', previousPageUrl]);
  
  _paq.push(['trackPageView']);

  Making Piwik Aware of New Content

  When you show a new page, your single-page DOM might change as well. For example, you might replace parts of your page with new content that you loaded from your server via Ajax. This means you need to instruct Piwik to scan the DOM for new content. We’ll now go over various content types (Videos & Audio, Forms, Links and Downloads, Content tracking).

  Video and Audio tracking

  If you use the Media Analytics feature to track your videos and audios, whenever a new page is displayed you need to call the following method :

  _paq.push(['MediaAnalytics::scanForMedia', documentOrElement]);

  When you don’t pass any parameter, it will scan the entire DOM for new media. Alternatively, you can pass an element to scan only a certain area of your website or app for new media.

  Form tracking

  If you use the Form Analytics feature to measure the performance of your online forms, whenever a new page is displayed you need to call the following method :

  _paq.push(['FormAnalytics::scanForForms', docuemntOrElement]);

  Where documentOrElement points either to document to re-scan the entire DOM (the default when no parameter is set) or you can pass an element to restrict the re-scan to a specific area.

  Link tracking

  Supposing that you use the link tracking feature to measure outlinks and downloads, Piwik needs to re-scan the entire DOM for newly added links whenever your DOM changes. To make sure Piwik will track such links, call this method :

  _paq.push(['enableLinkTracking']);

  Content tracking

  If you use the Content Tracking feature, whenever a new page is displayed and some parts of your DOM changes, you need to call this method :

  _paq.push(['trackContentImpressionsWithinNode', documentOrElement]);

  Where documentOrElement points either to document or an element similar to the other methods. Piwik will then scan the page for newly added content blocks.

  Measuring Single-Page Apps : Complete Example

  In this example we show how everything works together assuming you want to track a new page whenever a hash changes :

  var currentUrl = location.href;
  
  window.addEventListener('hashchange', function() {
  
      _paq.push(['setReferrerUrl', currentUrl]);
  
       currentUrl = '' + window.location.hash.substr(1);
  
      _paq.push(['setCustomUrl', currentUrl]);
  
      _paq.push(['setDocumentTitle', 'My New Title']);
  
  
  
      // remove all previously assigned custom variables, requires Piwik 3.0.2
  
      _paq.push(['deleteCustomVariables', 'page']); 
  
      _paq.push(['setGenerationTimeMs', 0]);
  
      _paq.push(['trackPageView']);
  
      
  
      // make Piwik aware of newly added content
  
      var content = document.getElementById('content');
  
      _paq.push(['MediaAnalytics::scanForMedia', content]);
  
      _paq.push(['FormAnalytics::scanForForms', content]);
  
      _paq.push(['trackContentImpressionsWithinNode', content]);
  
      _paq.push(['enableLinkTracking']);
  
  });

  Questions ?

  If you have any questions or need help, please get in touch with us. You can find more information about the Piwik JavaScript tracker on the Piwik Developer Zone.

• avcodec, avformat : deprecate anything related to side data merging

  16 mars 2017, par wm4

  avcodec, avformat : deprecate anything related to side data merging
  This patch deprecates anything that has to do with merging/splitting
  
  side data. Automatic side data merging (and splitting), as well as all
  
  API symbols involved in it, are removed completely.
  Two FF_API_ defines are dedicated to deprecating API symbols related to
  
  this : FF_API_MERGE_SD_API removes av_packet_split/merge_side_data in
  
  libavcodec, and FF_API_LAVF_KEEPSIDE_FLAG deprecates
  
  AVFMT_FLAG_KEEP_SIDE_DATA in libavformat.
  Since it was claimed that changing the default from merging side data to
  
  not doing it is an ABI change, there are two additional FF_API_ defines,
  
  which stop using the side data merging/splitting by default (and remove
  
  any code in avformat/avcodec doing this) : FF_API_MERGE_SD in libavcodec,
  
  and FF_API_LAVF_MERGE_SD in libavformat.
  It is very much intended that FF_API_MERGE_SD and FF_API_LAVF_MERGE_SD
  
  are quickly defined to 0 in the next ABI bump, while the API symbols are
  
  retained for a longer time for the sake of compatibility.
  
  AVFMT_FLAG_KEEP_SIDE_DATA will (very much intentionally) do nothing for
  
  most of the time it will still be defined. Keep in mind that no code
  
  exists that actually tries to unset this flag for any reason, nor does
  
  such code need to exist. Code setting this flag explicitly will work as
  
  before. Thus it’s ok for AVFMT_FLAG_KEEP_SIDE_DATA to do nothing once
  
  side data merging has been removed from libavformat.
  In order to avoid that anyone in the future does this incorrectly, here
  
  is a small guide how to update the internal code on bumps :
   next ABI bump (probably soon) :
  
    - define FF_API_LAVF_MERGE_SD to 0, and remove all code covered by it
  
    - define FF_API_MERGE_SD to 0, and remove all code covered by it
  
   next API bump (typically two years in the future or so) :
  
    - define FF_API_LAVF_KEEPSIDE_FLAG to 0, and remove all code covered
  
      by it
  
    - define FF_API_MERGE_SD_API to 0, and remove all code covered by it
  This forces anyone who actually wants packet side data to temporarily
  
  use deprecated API to get it all. If you ask me, this is batshit fucked
  
  up crazy, but it’s how we roll. Making AVFMT_FLAG_KEEP_SIDE_DATA to be
  
  set by default was rejected as an ABI change, so I’m going all the way
  
  to get rid of this once and for all.
  Reviewed-by : James Almer <jamrial@gmail.com>
  
  Reviewed-by : Rostislav Pehlivanov <atomnuker@gmail.com>
  
  Reviewed-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] doc/APIchanges
  • [DH] libavcodec/avcodec.h
  • [DH] libavcodec/avpacket.c
  • [DH] libavcodec/utils.c
  • [DH] libavcodec/version.h
  • [DH] libavformat/avformat.h
  • [DH] libavformat/mux.c
  • [DH] libavformat/options_table.h
  • [DH] libavformat/utils.c
  • [DH] libavformat/version.h

• avfilter/vf_overlay : remove rgb option

  24 juin 2017, par Paul B Mahol

  avfilter/vf_overlay : remove rgb option
  Its been deprecated for over 3 years.
  Signed-off-by : Paul B Mahol <onemda@gmail.com>
  

  • [DH] doc/filters.texi
  • [DH] libavfilter/vf_overlay.c