
Recherche avancée
Médias (2)
-
Granite de l’Aber Ildut
9 septembre 2011, par
Mis à jour : Septembre 2011
Langue : français
Type : Texte
-
Géodiversité
9 septembre 2011, par ,
Mis à jour : Août 2018
Langue : français
Type : Texte
Autres articles (111)
-
Personnaliser les catégories
21 juin 2013, parFormulaire de création d’une catégorie
Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire.
Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...) -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
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 (...)
Sur d’autres sites (10244)
-
Why Matomo is the top Google Analytics alternative
17 juin, par JoeYou probably made the switch to Google Analytics 4 (GA4) when Google stopped collecting Universal Analytics (UA) data in July 2023. Up to that point, UA had long been the default analytics platform, despite its many limitations.
This was mostly because everyone loved its free nature and simple setup. A Google account was all you needed — even a free legacy G-Suite account worked perfectly. Looking at the analytics for just about any website was easy.
That all changed with GA4, which addressed many of UA’s shortcomings by introducing a completely new way to model website data. Unfortunately, this also meant you couldn’t transfer historical data from UA into GA4, leading to more criticism.
Then there’s the added cost. GA4 is still free, but its limited functionality encourages you to upgrade to the enterprise version, Google Analytics 360 (GA360). Sure, you get lots of great functionality, less data sampling, and longer data retention periods, but it comes at a hefty price — $50,000 per year, to be exact.
There are other options, though, and Matomo Analytics is one of the best. It’s an open-source, privacy-centric platform that offers advanced features of GA360 and more.
In this article, we’ll compare GA4, GA360, and Matomo and give you what you need to make an informed decision.
Google Analytics 4 in a nutshell
Google Analytics 4 is a great tool to use to start learning about web analytics. But soon enough, you’ll likely find that GA4 doesn’t quite cover all of your needs.
For example, it can’t provide a detailed view of user experiences, and Google doesn’t offer dedicated support or onboarding. There are other shortcomings, too.
Data sampling
Google only processes a selected sample of website activity rather than every individual data point. Rather than looking at the whole picture, it sets a threshold and selects a [hopefully] representative sample for analysis.
This inevitably creates gaps in data. Google attempts to fill them in using AI and machine learning, inferring the rest from data patterns. Since the results rely on assumptions and estimates, they aren’t always precise.
In practical terms, this means that the accuracy of GA4 analysis will likely decline as website traffic increases.
Data collection limits
GA4’s 25 million monthly events limit seems like a lot, but they add up quickly.
All user interactions are recorded as events, including :
- Session start : User visits the site.
- Page view : User loads a page (tracked automatically).
- First visit : User accesses the site for the first time.
- User engagement : User stays on a page for a set time period.
- Scroll : User scrolls past 90% of the page (enhanced measurement).
- Click : User clicks on any element (links, buttons, etc.).
- Video start/complete : User starts or completes a video (enhanced measurement).
- File download : User downloads a file (enhanced measurement).
For context, consider a website averaging 50 events per session per user. If every user logs on every third day, on average, you’ll need 10,000 individual visitors a month to reach that 25 million. But that’s not the problem.
The problem is that collection limits in GA4 affect your ability to capture, secure, and analyse customer data effectively.
Customisation
GA4 users also face configuration limits that restrict their customisation options. For example :
- Audience limits : Since only 100 audiences are allowed, it’s necessary to combine or optimise segments rather than track too many small groups.
- Retention limits : Data retention is limited to only 14 months, so external storage solutions may be necessary in situations where historical data needs to be preserved.
- Conversion events : GA4 will only track up to 30 conversion events, so it’s best to focus on high-value interactions (e.g., purchases and lead form submissions).
- Event-scoped dimensions : Since e-commerce operations are limited to 50 event-scoped dimensions, they need to carefully consider custom dimensions and key metrics. This makes it important to be selective about which product details to track (color, size, discount code, etc.).
Data privacy
GA4 isn’t GDPR-compliant out of the box. In fact, Google Analytics 4 is banned in seven EU countries because they believe the way it collects and transfers data violates GDPR.
Data privacy regulations may or may not be a big concern, depending on where your customers are. However, if some are in the UK or any of the 30 countries that make up the European Economic Area (EEA), you must comply with the General Data Protection Regulation (GDPR).
It tells your customers that you don’t respect their data if you don’t. It can also get very expensive.
Limited attribution models
Attribution models track how different marketing touchpoints lead to a conversion (such as a purchase, sign-up, or lead generation). They help businesses understand which marketing channels and strategies are most effective in driving results.
GA4 supports only two of the six standard attribution models previously supported in Universal Analytics. Organisations wanting data-driven or last-click attribution models will find them in Google Analytics. But they’ll need to look elsewhere if they’re going to use any of these models :
- First click attribution
- Linear attribution
- Time decay attribution
- Position-based attribution (u-shaped)
GA360 isn’t a solution either
Fundamentally, GA360 is the same product as GA4, without the above limits and restrictions. For companies that pay $50,000 (or more) each year, the only changes involve how much data is collected, how long it stays and data sampling thresholds.
Above all, the GDPR-compliance issue remains. That can be a real problem for organisations with operations that collect personal data in the EEA or the UK.
And the problem could soon be much bigger than just those 31 countries. Many countries currently implementing data privacy laws are modelling their efforts on GDPR, which may rule out both GA4 and GA360.
What makes Matomo the top alternative ?
No data limits
One way to overcome all these challenges is to switch to Matomo Analytics.
There’s no data sampling and no data collection limits whatsoever with on-premise implementation. Matomo also supports all six attribution models, is open source and fully customisable and complies with GDPR out of the box.
Imagine trying to change your business strategy or marketing campaigns if you’re not confident that your data is reliable and accurate.
It’s no secret that data sampling can negatively affect the accuracy of the data, and inaccurate data can lead to poor decision-making.
With Matomo, there are no limits. We don’t restrict the size of containers within the Tag Manager nor the number of containers or tags within each container. You have more control over your customers’ data.
And you get to make your decisions based on all that data. That’s important because data quality is critical for high-impact decisions.
Open source
Open-source software allows anyone to inspect, audit, and improve the source code for security and efficiency. That means no hidden data collection, faster bug fixes, and no vendor lock-in. As a bonus, these things make complying with data privacy laws and regulations easier.
Matomo can also be modified in any way, which provides unlimited customisation possibilities. There’s also a very active developer community around Matomo, so you don’t have to make changes yourself — you can hire someone who has the technical knowledge and expertise. They can :
- Modify tracking scripts for advanced analytics
- Create custom attribution models, tracking methods and dashboards
- Integrate Matomo with any system (CRM, eCommerce, CMS, etc.)
Data ownership
Matomo’s open-source nature also means full data ownership. No third parties can access the data, and there’s no risk of Google using that data for ads or AI training. Furthermore, Matomo follows privacy-first tracking principles, meaning that there’s :
- No third-party data sharing
- Full user consent control
- Support for cookie-less tracking
- IP Anonymisation, by default
- Do Not Track (DNT) support
All of that underlines the fact that Matomo collects, stores, and tracks data 100% ethically.
On-premise and cloud-based options
You can use the Matomo On-Premise web analytics solution if local data privacy laws require that you store data locally. Here’s a helpful tip : many of them do. However, this might not be necessary.
Due to GDPR, several countries recognise the EEA as an acceptable storage location for their citizens’ data. That means servers hosted in any of those 30 countries are already compliant in terms of data location.
Alternatively, you could embrace modernity and choose Matomo Cloud — our servers are also in Europe. While GA4 and GA360 are cloud-based, Google’s servers are in the US, and that’s a big problem for GDPR.
Comprehensive analytics
If you need a sophisticated web analytics platform that offers full control of your data and you have privacy concerns, Matomo is a solid choice.
It has built-in behavioural analytics features like Heatmaps, Scroll Depth and Session Recording. These tools allow you to collect and analyse data without relying on cookies or resorting to data sampling.
Those standout features can’t be found in GA4 or GA360. Google also doesn’t offer an on-premise solution.
The one area where Matomo can’t compete with Google Analytics is in its tight integration with the Google ecosystem : Google Ads, Gemini and Firebase.
Key things to consider before switching to Matomo
There are pros and cons to switching from GA4 (or even GA360) to Matomo. That’s because no software is perfect. There are always tradeoffs somewhere. With Matomo, there are a few things to consider before switching :
- Learning curve. Matomo is a full-featured analytics platform with many advanced features (session replay, custom event tracking, etc.). That can overwhelm new users and take time to understand well enough to maximise the benefits.
- Technical resources. Choosing a Matomo On-Premise solution requires technical resources, such as a server and skills.
- Third-party integration. Matomo provides pre-built integration tools for about a hundred platforms. However, it’s open source, so technical resources are required. On the plus side, it does make it possible to add to the list of APIs and connectors.
Head-to-head : GA4 vs GA360 vs Matomo
It’s always helpful to look at how different products stack up in terms of features and capabilities :
GA4 GA360 Matomo Data ownership ✔ Event-based data ✔ ✔ ✔ Session-based data ✔ Unsampled data ✔ Real-time data ✔ ✔ ✔ Heatmaps ✔ Session recordings ✔ A/B testing ✔ Open source ✔ On-premise hosting ✔ Data privacy Subject to Google’s data policies Subject to Google’s data policies GDPR, CCPA compliant ; full control over data storage Custom dimensions Yes (limited in free version) Yes (higher limits) Yes (unlimited in self-hosted) Attribution models Last click, data-driven Last click, data-driven, advanced Google Ads integration Last click, first click, linear, time decay, position-based, custom Data retention Up to 14 months (free) Up to 50 months Unlimited (self-hosted) Integrations Google Ads, Search Console, BigQuery (limited in free version) Advanced integrations (Google Ads, BigQuery, Salesforce, etc.) 100+ integrations (Google Ads, WordPress, Shopify, etc.) BigQuery export Free (limited to 1M events/day) Free (unlimited) Paid add-on (via plugin) Custom reports Limited customisation Advanced customisation Fully customisable Scalability Suitable for small to medium businesses Designed for large enterprises Scalable without limits (self-hosted or cloud) Ease of use Simple, requires onboarding Steeper learning curve Flexible, setup-intensive. Pricing Free Premium (starts at $50,000/year) Free open-source (self-hosted) ; Cloud starts at $29/month So, is Matomo the right solution for you ?
That’d be a ‘yes’ if you want a Google Analytics alternative that ticks all these boxes :
- Complies natively with privacy laws and regulations
- Offers real-time data and custom event tracking
- Enables a deeper understanding of user behaviour
- Allows you to fine-tune user experiences
- Provides full control over your customers’ data
- Offers conversion funnels, session recordings and heatmaps
- Has session replay to trace user interactions
- Includes plenty of readily actionable insights
Find out why millions of websites trust Matomo
Matomo is an easy-to-use, all-in-one web analytics tool with advanced behavioural analytics functionality.
It’ll also help you future-proof your business because it supports compliance with global privacy laws in 162 countries. With an ethical alternative like Matomo, you don’t need to risk your business or customers’ private data.
It’s not just about avoiding fines. It’s also about building trust with your customers. That’s why you need a privacy-focused, ethical solution like Matomo.
See for yourself : download Matomo On-Premise today, or start your 21-day free trial of Matomo Cloud (no credit card required).
-
Matomo Launches Global Partner Programme to Deepen Local Connections and Champion Ethical Analytics
25 juin, par Matomo Core Team — Press Releases -
Server-side tracking vs client-side tracking : What you need to know
3 juillet, par JoeServer-side tracking vs client-side tracking : What you need to know
Today, consumers are more aware of their online privacy rights, leading to an extensive use of ad blockers and stricter cookie policies. Organisations are facing some noteworthy challenges with this trend, including :
- Limited data collection, which makes it harder to understand user behaviour and deliver personalised ads that resonate with customers
- Rising compliance costs as businesses adapt to new regulations, straining resources and budgets.
- Growing customer scepticism in data practices, affecting brand reputation.
- Maintaining transparency and fostering trust with customers through clear communication about data practices.
Server-side tracking can help resolve these problems. This article will cover server-side tracking, how it works, implementation methods and its benefits.
What is server-side tracking ?
Server-side tracking refers to a method where user data is collected directly by a server rather than through a user’s browser.
The key advantage of server-side tracking is that data collection, processing, and storage occur directly on the website’s server.
For example, when a visitor interacts with any website, the server captures that activity through the backend system, allowing for greater data control and security.
Client-side tracking vs. server-side tracking
There are two methods to collect user data : client-side and server-side.
Let’s understand their differences.
Client-side tracking : Convenience with caveats
Client-side tracking embeds JavaScript tags, pixels or other scripts directly into a website’s code. When a user interacts with the site, these tags fire, collecting data from their browser. This information might include page views, button clicks, form submissions and other user actions.
The collected data is then sent directly to third-party analytics platforms like Google Analytics or Adobe Analytics, or internal teams can also analyse it.
This method is relatively easy to implement. That’s because marketers can often deploy these tags without needing extensive developer support, enabling quick adjustments and A/B testing.
However, there are some challenges.
Ad blockers and browser privacy settings, such as Intelligent Tracking Prevention (ITP), restrict the ability of third-party tags to collect data.
This results in data gaps and inaccuracies skewing analytics reports and potentially leading to misguided business decisions.
Reliance on numerous JavaScript tags can also negatively impact website performance, slowing down page load times and affecting user experience. This is especially true on mobile devices where processing power and network speeds are often limited.
Now, let’s see how server-side tracking changes this.
Server-side tracking : Control and reliability
Server-side tracking shifts the burden of data collection from the user’s browser to a server controlled by the business.
Instead of relying on JavaScript tags firing directly from the user’s device, user interactions are first sent to the business’s own server. Here, the data can be processed, enriched, and analysed.
This method provides numerous advantages, including enhanced control over data integrity, improved privacy, and more, which we discuss in the next section.
Benefits of server-side tracking
Server-side tracking offers a compelling alternative to traditional client-side methods, providing numerous business advantages. Let’s take a look at them.
Improved data accuracy
This method reduces inaccuracies caused by ad blockers or cookie restrictions by bypassing browser limitations. As a result, the data collected is more reliable, leading to better analytics and marketing attribution.
Data minimisation
Data minimisation is a fundamental principle in data protection. It emphasises that organisations should collect only data that is strictly needed for a specific purpose.
In server-side tracking, this translates into collecting just the essential data points and discarding anything extra before the data is sent to analytics platforms. It helps organisations avoid accumulating excessive personal information, reducing the risk of data breaches and misuse.
For example, consider a scenario where a user purchases a product on an e-commerce website.
With client-side tracking scripts, the system might inadvertently collect a range of data, including the user’s IP address, browser type, operating system and even details about other websites they have visited.
However, for conversions, the organisation only needs to know the purchase amount, product IDs, user IDS, and timestamps.
Server-side tracking filters unnecessary information. This reduces the privacy impact and simplifies data analysis and storage.
Cross-device tracking capabilities
Server-side tracking provides a unified view of customer behaviour regardless of the device they use, allowing for more personalised and targeted marketing campaigns.
In-depth event tracking
Server-side tracking helps businesses track events that occur outside their websites, such as payment confirmations. Companies gain insights into the entire customer journey, from initial interaction to final purchase, optimising every touchpoint.
Enhanced privacy compliance
With increasing regulations like GDPR and CCPA, businesses can better manage user consent and data handling practices through server-side solutions.
Server-side setups make honouring user consent easier. If a user opts out, server-side logic can exclude their data from all outgoing analytics calls in one central place.
Server-side methods reassure users and regulators that data is collected and secured with minimal risk.
In sectors like government and banking, this level of control is often a non-negotiable part of their duty of care.
Extended cookie lifetime
Traditional website tracking faces growing obstacles as modern browsers prioritise user privacy. Initiatives like Safari’s ITP block third-party cookies and also constrain the use of first-party cookies.
Other browsers, such as Firefox and Brave, are implementing similar methods, while Chrome is beginning to phase out third-party cookies. Retargeting and cross-site analytics, which rely on these cookies, encounter significant challenges.
Server-side tracking overcomes this by allowing businesses to collect data over a longer duration.
When a website’s server directly sets a cookie, that cookie often lasts longer than cookies created by JavaScript code running inside the browser. This lets websites get around some of the limits browsers put on tracking and allows them to remember a visitor when they return to the site later, which gives better customer insights. Plus, server-side tracking typically classifies cookies as first-party data, which is less susceptible to blocking by browsers and ad blockers.
Server-side tracking : Responsibilities and considerations
While server-side tracking delivers powerful capabilities, remember that it also brings increased responsibility. Companies must remain vigilant in upholding privacy regulations and user consent. It’s up to the organisation to make sure the server follows user consent, for example, not sending data if someone has opted out.
Server-side setups introduce technical complexity, which can potentially lead to data errors that are more difficult to identify and resolve. Therefore, monitoring processes and quality assurance practices are essential for data integrity.
How does server-side tracking work ?
When a user interacts with a website (e.g., clicking a button), this action triggers an event. The event could be anything from a page view to a form submission.
The backend system captures relevant details such as the event type, user ID and timestamp. This information helps in understanding user behaviour and creating meaningful analytics.
The captured data is processed directly on the organisation’s server, allowing for immediate validation. For example, organisations can add additional context or filter out irrelevant information.
Instead of sending data to third-party endpoints, the organisation stores everything in its own database or data warehouse. This ensures full control over data privacy and security.
Organisations can perform their own analysis using tools like SQL or Python. To visualise data, custom dashboards and reports can be created using self-hosted analytics tools. This way, businesses can present complex data in a clear and actionable manner.
How to implement server-side tracking ?
Server-side tracking can work in four common ways, each offering a different blend of control, flexibility and complexity.
1. Server-side tag management
In this method, organisations use platforms like Google Tag Manager Server-Side to manage tracking tags on the server, often using containers to isolate and manage different tagging environments.
This approach offers a balance between control and ease of use. It allows for the deployment and management of tags without modifying the application code, which is particularly useful for marketers who want to adjust tracking configurations quickly.
2. Direct server-to-server tracking via APIs
This method involves sharing information between two servers without affecting the user’s browser or device.
A unique identifier is generated and stored on a server when a user interacts with an ad or webpage.
If a user takes some action, like making a purchase, the unique identifier is sent from the advertiser’s server directly to the platform’s server (Google or Facebook) via an API.
It requires more development effort but is ideal for organisations needing fine-grained data control.
3. Using analytics platforms with built-in server SDKs
Another way is to employ analytics platforms like Matomo that provide SDKs for various programming languages to instrument the server-side code.
This eases integration with the platform’s analytics features and is a good choice for organisations primarily using a single analytics platform and want to use its server-side capabilities.
4. Hybrid approaches
Finally, organisations can also combine client- and server-side tracking to capture different data types and maximise accuracy.
This method involves client-side scripts for specific interactions (like UI events) and server-side tracking for more sensitive or critical data (like transactions).
While these are general approaches, dedicated analytics platforms can also be helpful. Matomo, for example, facilitates server-side tracking through two specific methods.
Using server logs
Matomo can import existing web server logs, such as Apache or Nginx, that capture each request. Every page view or resource load becomes a data point.
Matomo’s log processing script reads log files, importing millions of hits. This removes the need to add code to the site, making it suitable for basic page analytics (like the URL) without client-side scripts, particularly on security-sensitive sites.
Using the Matomo tracking API (Server-side SDKs)
This method integrates application code with calls to Matomo’s API. For example, when a user performs a specific action, the server sends a request to Matomo.php, the tracking endpoint, which includes details like the user ID and action.
Matomo offers SDKs in PHP, Java C#, and community SDKs to simplify these calls. These allow tracking of not just page views but custom events such as downloads and transactions from the backend, functioning similarly to Google’s Measurement Protocol but sending data to the Matomo instance.
Data privacy, regulations and Matomo
As privacy concerns grow and regulations like GDPR and CCPA become more stringent, businesses must adopt data collection methods that respect user consent and data protection rights.
Server-side tracking allows organisations to collect first-party data directly from their servers, which is generally considered more compliant with privacy regulations.
Matomo is a popular open-source web analytics platform that is committed to privacy. It gives organisations 100% data ownership and control, and no data is sent to third parties by default.
Matomo is a full-featured analytics platform with dashboards and segmentation comparable to Google Analytics. It can self-host and provides DoNotTrack settings and the ability to anonymise IP addresses.
Governments and organisations requiring data sovereignty, such as the EU Commission and the Swiss government, choose Matomo for web analytics due to its strong compliance posture.
Balancing data collection and user privacy
Ad blockers and other restrictions prevent data from being accurate. Server-side tracking helps get data on the server and makes it more reliable while respecting user privacy. Matomo supports server-side tracking, and over one million websites use Matomo to optimise their data strategies.
Get started today by trying Matomo for free for 21 days, no credit card required.