
Recherche avancée
Médias (91)
-
GetID3 - Boutons supplémentaires
9 avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
-
Core Media Video
4 avril 2013, par
Mis à jour : Juin 2013
Langue : français
Type : Video
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
-
Exemple de boutons d’action pour une collection collaborative
27 février 2013, par
Mis à jour : Mars 2013
Langue : français
Type : Image
-
Exemple de boutons d’action pour une collection personnelle
27 février 2013, par
Mis à jour : Février 2013
Langue : English
Type : Image
Autres articles (30)
-
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...) -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)
Sur d’autres sites (5349)
-
What is last click attribution ? A beginner’s guide
10 mars 2024, par Erin -
B2B Marketing Attribution Guide : How to Master It in 2024
21 mai 2024, par Erin -
The complete guide on tracking your websites and web apps into multiple Piwiks and how to do it easily & efficiently
23 février 2017, par InnoCraft — Community, DevelopmentGetting the tracking of your website 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 digital measurement strategy. Some challenges include tracking your analytics data into multiple Piwik services as well as the tracking of single-page websites and web applications (covered in a previous article). In this blog post, we explain how to track your data into multiple Piwik websites correctly.
Embedding the tracking code
First of all you need to embed your JavaScript tracking code into your website or app as usual. If you haven’t done this yet : Log in to your Piwik, click on “Administration” in the top right and go to “Tracking Code”. There you have various options to adjust your tracking code to your needs.
Tracking the same data into different websites
Let’s assume you have set up the regular JavaScript tracking code and you want to track the same data into a second Piwik website. This second Piwik website can be either on the same Piwik installation or on a different Piwik. To do this, add the following line to your tracking code :
_paq.push(['addTracker', 'https://$yourPiwikDomain/piwik.php', idSite]);
It should look like this :
var u = '//$yourPiwikDomain';
_paq.push(['addTracker', u + '/piwik.php', var idSite = 2]); // adds an additional tracker
_paq.push(['setSiteId', '1']); // configures your regular Piwik tracker
_paq.push(['setTrackerUrl', u + 'piwik.php']);This will track the same data into website 1 and website 2 of your Piwik installation. You can also change the domain in
addTracker
to point it to a different Piwik installation :_paq.push(['addTracker', '//$differentPiwikDomain/piwik.php', var idSite = 2]);
All Piwik tracker methods that you call afterwards will be applied to all trackers. Say you call
_paq.push(['disableCookies']); _paq.push(['trackPageView']);
, then both methods will be called on all tracker instances assuring they will behave the same and will track the same data into both Piwik websites.Tracking different data into different websites
If you want to track only certain data into one website, and different data into an additional website, you need to configure the trackers differently. For example, you want to enable link tracking only for one tracker, but not for the other. The problem is that calling
_paq.push(['enableLinkTracking']);
enables link tracking on all of your trackers. To workaround this limitation, you can configure your trackers differently like this :window.piwikAsyncInit = function () {
Piwik.on('TrackerSetup', function (tracker) {
if (tracker.getSiteId() == 2
|| tracker.getTrackerUrl() === '//$yourPiwikDomain/piwik.php') {
tracker.enableLinkTracking();
}
});
};Now it enables link tracking only for the tracker that is configured for a certain website ID or Piwik domain.
Accessing a previously generated tracker instance
When you configure a tracker via
_paq.push
, you create a so called “Async tracker” because Piwik will be loaded asynchronously and create the tracker instance as soon as it is loaded. If you need to get the instance of such a tracker, you can use the methodPiwik.getAsyncTracker(trackerUrl, idSite)
. This can be useful if you have a single-page website and want to track different data into different websites :window.addEventListener('hashchange', function() {
if ('undefined' === typeof Piwik) {
// Piwik might not be loaded yet
return;
}
var tracker1 = Piwik.getAsyncTracker('//$yourPiwikDomain/piwik.php', var idSite = 1);
var tracker2 = Piwik.getAsyncTracker('//$yourPiwikDomain/piwik.php', var idSite = 2);
tracker1.setCurrentUrl('/' + window.location.hash.substr(1));
tracker2.setCurrentUrl('/mywebsite/' + window.location.hash.substr(1));
});Tracking different data into multiple Piwik installations without using “_paq”
Some users prefer to not use
_paq.push
and instead directly create tracker instances themselves using the methodPiwik.getTracker(trackerUrl, idSite)
like this :window.piwikAsyncInit = function () {
var tracker1 = Piwik.getTracker('//$yourPiwikdomain/piwik.php', var idSite = 1);
tracker1.disableCookies();
var tracker2 = Piwik.getTracker('//$yourPiwikdomain/piwik.php', var idSite = 2);
tracker2.enableLinkTracking();
tracker1.trackPageView();
tracker2.trackPageView();
};We usually don’t recommend creating trackers manually as it is more complicated and you need to make sure to configure trackers in the right order. For example to prevent the setting of any cookies, it is recommended to call
disableCookies
before calling any other methods. If you want to create your trackers manually and you use any of the following methods, make sure to call them in this order :disableCookies(), setAPIUrl(), enableCrossDomainLinking(), setCookiePath(), setCookieDomain(), setDomains(), setUserId(), enableLinkTracking()
Roll-Up Reporting – the easy and efficient way
Often users track data into multiple websites because they need aggregated data over all their websites. They want to see all statistics for a single website, but also which pages were viewed across all their websites, or how much traffic they got from a specific website or search engine across all websites. This means they add a second tracker to all their websites and track data not only into the regular Piwik website, but also into one additional website that gives them statistics over all websites. This has several disadvantages :
- Complexity in getting the tracking code right and the time needed to integrate and maintain it
- Slower website performance because everything needs to be tracked into several websites. This can decrease your conversions and sales
- Slower Piwik performance because it has to handle twice as much traffic. This means tracking becomes slower, generating the report becomes slower, and the database gets twice as big
Luckily, there is a better solution called Roll-Up Reporting. With Roll-Up Reporting, you can get aggregated data over all websites and / or for a group of websites without any of these disadvantages. It lets you create as many Roll-Ups as you wish and you can choose which websites’ data should be aggregated together into a new website.
We had customers who were able to remove one Piwik tracker because of this feature which resulted in less server costs, a faster website, and a faster Piwik. On top of all these advantages, it also lets you view the Visitor Log, Real-time Map, and other widgets and reports across several websites.
Questions ?
If you got any questions, please let us know and get in touch with us. You can find more information about the Piwik JavaScript tracker on the Piwik Developer Zone. There is a section dedicated to Multiple Piwik Trackers.