Recherche avancée

Médias (3)

Mot : - Tags -/collection

Autres articles (14)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

Sur d’autres sites (2553)

  • Announcing Piwik Community Meetup in Munich : Register now !

    5 mai 2014, par Piwik Core Team

    We’re excited to announce our second Piwik community Meetup ! This will be a unique opportunity to connect with other Piwik users, and meet the core team behind Piwik.

    Updated : presentation slides

    The Making Of The Analytics Platform Of The Future

    Piwik in Enterprise

    Piwik Analytics Platform

    Guest lecture : TV to Web Analytics

    Guest lecture : Oxid analytics with Piwik

    When and where is the meetup ? (update, see below)

    Location : Munich, Germany
    Date : Tuesday July 29th 2014
    Time : 5PM
    Language : German/English
    Cost : Free !

    Register now !

    Who can join ?

    All Piwik community members (users, translators, contributors) are warmly invited to join the meetup. Almost all of the core team will be present, we’re looking forward to meeting you !

    What to expect for the Piwik meetup ?

    The meetup will consist of three speakers giving quick 15-20 minute presentations followed by Q&A.

    • Discover some of the upcoming features
    • Learn tricks to make the most out of Piwik
    • Networking and socialising… and an after party in a local bar to continue the discussion !

    Who can join the meetup ?

    This meetup is open to all Piwik users and members of the community.

    • If you are using Piwik to improve your websites and apps, or generally curious about digital analytics and marketing
    • If you are interested in the platform, integrating your app with Piwik or building plugins, come meet with other developers and creators of Piwik

    Timing

    • Doors open at 17:00
    • Starts at 17:30
    • Ends at 20:00 – 20:30

    Schedule

    • 17:30 – Welcome speech (Peter Boehlke (german))
    • 17:40 – Piwik for governments & corporations – Piwik PRO case study (Maciej Zawadziński english)
    • 18:05 – Break (25 minutes) – Coffee, Tea, pastries and cold buffet (free)
    • 18:30 – Overview of the platform Piwik, custom data tracking, publishing on the new Marketplace (Thomas Steur (german))
    • 18:55 – Break (10 minutes)
    • 19:05Piwik users present interesting real world use cases (german)
      – TV-to-Web analytics (Jasper Sasse)
      – Piwik from a SEO’s perspective (Thomas Zeithaml)
      – Using the Piwik Framework to analyze Shop-Data (Joachim Barthel)
    • 19:30 – Break (10 minutes)
    • 19:40 – Next big features, milestones, future roadmap (Matthieu Aubry english)
    • 20:05 – Break (5 minutes)
    • 20:10 – Summary & end of the conference (german)
    • After party at a nearby bar or restaurant (open end)

    Call for Papers

    We would like to hear about how you use Piwik ! If you’d like to present your interesting use case on the conference (speaking time 5 to 7 minutes), please contact us at hello@piwik.org !

    Meetup location

    Munich Workstyle
    Landwehrstraße 61
    80336 München
    Location / Directions

    Parking space is limited : We recommend to use public transport !
    Stations nearby :

    - S-Bahn : Hauptbahnhof, Stachus (both 700m)

    - U-Bahn : Stachus (700m), Theresienwiese (400m)

    Beverage pricing

    - Mineral water : EUR 3,10 (0,75l)

    - Softdrinks / juices : EUR 2,10

    - Beer : EUR 2,80

    Munich Workstyle

    A special thank you to our sponsor Mayflower GmbH !

    Mayflower

    Register now

    Seats are limited, please register today to secure your seat :
    Register now !

  • Announcing Piwik Community Meetup in Munich : Register now !

    5 mai 2014, par Piwik Core Team

    We’re excited to announce our second Piwik community Meetup ! This will be a unique opportunity to connect with other Piwik users, and meet the core team behind Piwik.

    Updated : presentation slides

    The Making Of The Analytics Platform Of The Future

    Piwik in Enterprise

    Piwik Analytics Platform

    Guest lecture : TV to Web Analytics

    Guest lecture : Oxid analytics with Piwik

    When and where is the meetup ? (update, see below)

    Location : Munich, Germany
    Date : Tuesday July 29th 2014
    Time : 5PM
    Language : German/English
    Cost : Free !

    Register now !

    Who can join ?

    All Piwik community members (users, translators, contributors) are warmly invited to join the meetup. Almost all of the core team will be present, we’re looking forward to meeting you !

    What to expect for the Piwik meetup ?

    The meetup will consist of three speakers giving quick 15-20 minute presentations followed by Q&A.

    • Discover some of the upcoming features
    • Learn tricks to make the most out of Piwik
    • Networking and socialising… and an after party in a local bar to continue the discussion !

    Who can join the meetup ?

    This meetup is open to all Piwik users and members of the community.

    • If you are using Piwik to improve your websites and apps, or generally curious about digital analytics and marketing
    • If you are interested in the platform, integrating your app with Piwik or building plugins, come meet with other developers and creators of Piwik

    Timing

    • Doors open at 17:00
    • Starts at 17:30
    • Ends at 20:00 – 20:30

    Schedule

    • 17:30 – Welcome speech (Peter Boehlke (german))
    • 17:40 – Piwik for governments & corporations – Piwik PRO case study (Maciej Zawadziński english)
    • 18:05 – Break (25 minutes) – Coffee, Tea, pastries and cold buffet (free)
    • 18:30 – Overview of the platform Piwik, custom data tracking, publishing on the new Marketplace (Thomas Steur (german))
    • 18:55 – Break (10 minutes)
    • 19:05Piwik users present interesting real world use cases (german)
      – TV-to-Web analytics (Jasper Sasse)
      – Piwik from a SEO’s perspective (Thomas Zeithaml)
      – Using the Piwik Framework to analyze Shop-Data (Joachim Barthel)
    • 19:30 – Break (10 minutes)
    • 19:40 – Next big features, milestones, future roadmap (Matthieu Aubry english)
    • 20:05 – Break (5 minutes)
    • 20:10 – Summary & end of the conference (german)
    • After party at a nearby bar or restaurant (open end)

    Call for Papers

    We would like to hear about how you use Piwik ! If you’d like to present your interesting use case on the conference (speaking time 5 to 7 minutes), please contact us at hello@piwik.org !

    Meetup location

    Munich Workstyle
    Landwehrstraße 61
    80336 München
    Location / Directions

    Parking space is limited : We recommend to use public transport !
    Stations nearby :

    - S-Bahn : Hauptbahnhof, Stachus (both 700m)

    - U-Bahn : Stachus (700m), Theresienwiese (400m)

    Beverage pricing

    - Mineral water : EUR 3,10 (0,75l)

    - Softdrinks / juices : EUR 2,10

    - Beer : EUR 2,80

    Munich Workstyle

    A special thank you to our sponsor Mayflower GmbH !

    Mayflower

    Register now

    Seats are limited, please register today to secure your seat :
    Register now !

  • 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, Development

    Getting 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 method Piwik.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 method Piwik.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.