Recherche avancée
Autres articles (52)
-
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
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 (14556)
-
Consent management platforms : Keys to compliance and user trust
14 juin, par JoeToday’s marketing managers and data analysts face a tricky balancing act : gaining meaningful customer insights while respecting user privacy. Finding ways to navigate the maze of complex privacy regulations while managing consent at scale can be daunting.
Consent management platforms (CMPs) offer a solution. They allow companies to collect data ethically, manage user consent efficiently, and comply with privacy regulations like Europe’s General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA).
This guide explains everything you need to know about CMPs : how they function, why they’re essential for data governance, and how they work hand-in-hand with analytics platforms to promote transparency and build trust with users.
What is a consent management platform (CMP) and what is it for ?
A consent management platform (CMP) helps organisations collect, organise, and store user consent for personal data processing purposes. In short, it’s a tool that ensures data collection respects user privacy and complies with regulations like the GDPR and CCPA.
Without a CMP, businesses could face hefty fines and penalties for violating data privacy laws in different parts of the world. This shows how vital these tools are to all modern businesses.
How do consent management platforms work ?
CMPs give users a clear and straightforward way to provide explicit consent for data collection. These platforms manage both the technical aspects of consent storage and the user experience on your site or app.
Here’s a simplified breakdown :
- Cookie consent banners : The CMP displays a banner whenever a user visits your website. This banner explains the types of personal information collected and for what purpose.
- User choice : The user can accept or reject cookies and trackers. They can often customise their preferences to choose which specific data types they’re willing to share.
- Preference storage : The CMP stores the user’s choices. This information helps ensure that you only collect and process the permitted data.
- Integration with other systems : CMPs integrate with other systems, such as analytics platforms and advertising networks, to ensure that data collection and processing comply with the user’s choices throughout the customer experience.
A key feature of CMPs is their role in shaping privacy policy design. This design encompasses the layout, visual elements, and cues employed to seek user consent.
A recent study by Karlstad University in Sweden showed that privacy policy design significantly influences user comprehension and willingness to disclose information. In other words, it affects consent rates considerably and is key to enhancing data collection.
Importance of consent management for compliance
As the world becomes increasingly interconnected, consent management is taking centre stage. Although it applies to all technologies and systems that gather or handle personal data, few instances are as relevant as smart homes.
Smart home devices have unique access to our personal spaces and private lives. They represent a unique challenge to consent management since one person is potentially granting access to personal data from themselves and other people who may be inside or around the house.
A 2023 study by the University College London and the University of Oxford pointed out that clear design principles and granular, contextual permission structures are essential in these situations.
However, consent management isn’t just best practice. It’s a widespread legal requirement. Not meeting these requirements can result in hefty penalties and reputational damage to your organisation.
Consent management under GDPR
The European Union’s GDPR is a data protection law applicable to organisations that process the personal data of individuals residing in the European Economic Area (EEA). It’s based on the principle of opting in.
The GDPR is one of the strongest data privacy laws globally. For non-compliance, fines can be up to €20 million or 4% of the company’s total global turnover (whichever is higher).
It’s also one of the most heavily enforced privacy laws. According to enforcementtracker.com, Meta was fined €1.2 billion in 2023, with GDPR fines reaching over €2 billion that year alone. In the UK, the largest GDPR fine is €22.05 million, according to Statista. It pays to comply.
The GDPR has specific rules around consent, including that it must be :
- Freely given : Users must not be pressured or coerced.
- Specific : Must be given for specific data processing purposes.
- Informed : Users must be provided with clear and concise information.
- Unambiguous : Permission must be granted through clear and affirmative action, such as checking a box or tapping a button.
CMPs help you meet these requirements by providing a transparent and user-friendly way to obtain and manage consent.
Consent management under CCPA
The CCPA is another privacy protection law for businesses collecting personal information from California residents. It grants Californians the right to know what data is being collected about them, to prevent it from being sold, and to request its deletion.
CMPs support CCPA compliance by enabling users to exercise their rights and ensuring transparent data collection practices.
Managing consent under other regulatory frameworks
In addition to the GDPR and CCPA, numerous other privacy regulations can impact your organisation. These regulations include :
- The COPPA in the US
- Brazil’s LGPD
- Japan’s APPI
- Canada’s PIPEDA.
- Australia’s Privacy Act 1988
A CMP will help streamline the process by providing a clear, practical framework to ensure you meet all applicable requirements.
Key features to look for in a CMP
Choosing the right CMP is crucial for global business.
Here are some key features to consider :
Custom banners
Consent banners are often among users’ first digital interactions with your brand. It should be clear, concise and visually appealing. Look for a CMP that allows you to :
- Customise the banner’s design to match your website’s branding and aesthetics.
- Control the banner’s positioning for optimal visibility.
End-user management tools
The CMP should also offer a user-friendly interface allowing visitors to grant, manage and withdraw consent.
This includes customisable banners, granular permissions, and a preference centre. The latter is a dedicated space where users can manage their preferences anytime.
Integration capabilities with existing systems
The CMP should integrate with your existing technology stack, including your analytics platform, marketing automation tools and CRM. This integration ensures a smooth workflow and prevents data silos.
How to select the right CMP for your organisation
To find the perfect CMP, focus on your specific needs and priorities. Here’s a step-by-step guide to help you make an informed decision :
Assessing organisational needs and goals
Start by clearly defining your organisation’s requirements. Consider the following :
- Types of data collected : What personal data do you collect (for example, cookies, IP addresses, location data) ?
- Compliance requirements : Which privacy regulations must you comply with (GDPR, CCPA, COPPA) ?
- Website or app complexity : How complex is your website or app in terms of user interactions and data collection points ?
- Budget : How much are you willing to invest in a CMP ?
Comparing features and pricing
Once you thoroughly understand your needs, you can compare the features and pricing of various CMPs. Look for key features like :
- Customisable banners
- Granular options
- Preference centre
- Integration with existing systems
- Analytics and reporting
Once you’ve shortlisted a few options, compare the pricing and choose the best value for your budget. Take advantage of free trials before committing to a paid plan.
Checking verified user reviews
Read user reviews on platforms like G2 or Trustpilot to get an idea of the strengths and weaknesses of different CMPs. Look for reviews from similar organisations regarding size, industry and compliance requirements.
Integration with a privacy-focused analytics platform
A consent management platform acts as the bridge between your users and your analytics and marketing teams. It ensures user preferences are communicated to your analytics setup, so data collection and analysis align with their choices and comply with privacy regulations.
Finding a consent manager integration that works with your analytics setup is essential for businesses.
Top five consent management platforms
The CMP market is pretty competitive, with many players providing excellent solutions. According to Emergen Research, it was valued at $320.9 million in 2021 and is growing at 21.2%.
Here are five of our top choices
1. usercentrics
usercentrics is a comprehensive CMP with customisable banners, granular consent options and a preference centre.
usercentrics geolocation rulesets page (Source : Usercentrics)
This Google-certified CMP allows you to create global and regional consent rules to ensure compliance with local regulations like GDPR, CCPA and LGPD. For a smooth implementation, usercentrics provides access to a knowledgeable support team and a dedicated customer success executive.
It’s worth noting that Usercentrics is the CMP we use here at Matomo. It helps us in our mission to collect and analyse data ethically and with a privacy-first mindset.
- Key features : Customisable banners, granular permissions, cross-domain and cross-device capabilities, automatic website scans, reporting and analytics.
- Pricing : Usercentrics offers a free plan and four paid subscription plans from €7 to €50 per month.
2. Osano
Osano is a user-friendly CMP focusing on transparency and ease of use.
Osano’s main dashboard (Source : Osano)
Osano can scan websites for tracking technologies without impacting the user experience.
- Key features : Customisable banners, multi-language support, granular consent options, a preference centre and access to a knowledgeable team of compliance specialists.
- Pricing : Osano offers a self-service free plan and a paid plan at $199 per month.
3. Cookiebot
Cookiebot is another popular CMP with numerous integration options, including Matomo and other analytics tools.
Cookiebot consent banner options (Source : Cookiebot)
- Key features : A cookie scanner, a privacy trigger or button allowing users to change their consent settings, a consent management API and advanced analytics.
- Pricing : Cookiebot offers a free plan and paid plans ranging from €7 to €50 per month.
4. CookieYes
CookieYes is well-suited for small businesses and websites with basic privacy needs.
CookieYes cookie banner options (Source : CookieYes)
It offers various features, including multilingual support, geo-targeting, privacy policy generation, and a preference centre. CookieYes also integrates with analytics and CMS tools, making it easy to implement as part of your stack.
- Key features : Customisable consent banners, granular consent options, preference centre, integration with Matomo, reporting and analytics.
- Pricing : You can use CookieYes for free or subscribe to one of their three paid plans, which range from $10 to $55 per month.
5. Tarte au Citron
Tarte au Citron is an open-source, lightweight, and customisable CMP developed in France.
(Source : Tarte au Citron)
Its focus is on transparency and user experience. It provides many features free of charge, but many do require some technical knowledge to deploy. There’s also a paid subscription with ongoing support and faster implementation.
Tarte au Citron integrates with Matomo, which is also open-source. If you’re building an open-source stack for your analytics, Matomo and Tarte au Citron make an excellent pair.
- Key features : Open-source, customisable consent banners, integration with Matomo, works with over 220 services.
- Pricing : You can deploy the open-source core for free, but Tarte au Citron offers three paid licenses starting at €190 for one year and reaching €690 for a lifetime license.
How to implement cookie consent the right way
Implementing cookie consent requires precision, time and effort. But doing it wrong can result in significant legal penalties and severe reputational damage, eroding user trust and impacting your brand’s standing. Here are the key dos and don’ts of consent :
Provide clear and concise information
Use plain language that is easy for anyone to understand. Avoid using technical terms or legal jargon that may confuse users.
Prioritise transparency
Be upfront about your data collection practices. Clearly state what data you collect, how you use it and who you share it with. Provide links to your privacy and cookie policies for users who want to learn more.
Offer granular control
Give users detailed control over as many of their cookie preferences as possible. Allow them to choose which categories of tracking cookies they consent to, such as strictly necessary, performance and marketing cookies.
Implement user-friendly banners
Ensure banners are prominently displayed, easy to understand, and use clear and concise language. Also, make sure they’re accessible to all users, including those with disabilities.
Respect “do not track” settings
It’s essential to honour users’ choices when they enable their “do not track” browser setting.
Document consent
Maintain a record of user consent. This will help you demonstrate compliance with data privacy regulations and provide evidence of user consent in case of an audit or investigation.
Regularly review and update consent policies
Review and update your customer consent policies regularly to ensure they comply with evolving data privacy regulations and reflect your current data collection practices.
Cookie consent pitfalls to avoid
Here are some common pitfalls to avoid that may lead to legal penalties, loss of user trust or inaccurate analytics :
- Avoid lengthy and complicated explanations. Overwhelming users with dense legal jargon or overly technical details can lead to consent fatigue and reduce the likelihood of informed consent.
- Don’t force users to accept all cookies or none. Blanket consent options violate user autonomy and fail to comply with regulations like the GDPR.
- Don’t make information about your data collection practices hard to find. Hidden or buried privacy policies breed suspicion and erode trust.
- Avoid pre-checking all cookie consents. Pre-checked boxes imply consent without explicit user action, which is not compliant with GDPR and similar regulations. Users must actively opt in, not out.
Emerging consent management trends
Consent management is constantly evolving and driven by new technologies, regulations, and user expectations. Here are some emerging trends to watch out for in the short term :
- Increased automation : AI and machine learning are helping automate consent management processes, making them more efficient and effective.
- Enhanced user experience : CMPs are becoming more user-friendly, focusing on providing an intuitive experience.
- Privacy-preserving analytics : CMPs are being integrated with privacy-preserving analytics platforms, such as Matomo, to enable organisations to gain insights into user behaviour without compromising privacy.
- Google Consent Mode : In 2024, Google rolled out Consent Mode v2 to align with the Digital Markets Act. Due to upcoming privacy regulations, more versions may be coming soon.
The Privacy Governance Report 2024 also highlights the increasing complexity of managing data privacy, with more than four in five privacy professionals taking on additional responsibilities in their existing roles. This trend will likely continue in the coming years as more privacy laws are enacted.
Addressing upcoming privacy regulations
Data privacy and user consent requirements continue to emerge and evolve. Businesses must stay informed and adapt their practices accordingly.
In 2025, several new privacy regulations are going into effect, including :
- New state-level privacy laws in eight US states :
- Delaware (1 January 2025)
- Iowa (1 January 2025)
- Nebraska (1 January 2025)
- New Hampshire (1 January 2025)
- New Jersey (15 January 2025)
- Tennessee (1 July 2025)
- Minnesota (31 July 2025)
- Maryland (1 October 2025)
- The EU’s Artificial Intelligence Act (which will be implemented from 1 August 2024 through 2 August 2026) and other AI-focused regulations.
- The UK Adequacy Decision Review has a deadline of 27 December 2025.
Organisations that collect, process or otherwise handle data from Europe and the above-named US states should proactively prepare for these changes by :
- Conducting regular privacy impact assessments
- Reviewing consent mechanisms regularly
- Implementing data minimisation strategies
- Providing user-friendly privacy controls
Future-proofing your consent management strategy
CMPs are essential for managing consent preferences, protecting user privacy, and earning customers’ trust through transparency and ethical data practices.
When choosing a CMP, you should consider key features such as integration capabilities, customisation options and user-friendly interfaces.
Integrating a CMP with a privacy-first analytics solution like Matomo allows you to collect and analyse data in a way that’s compliant and respectful of user preferences. This combination helps maintain data integrity while demonstrating a strong commitment to privacy.
Start your 21-day free trial today.
-
Web Analytics : The Quick Start Guide
25 janvier 2024, par ErinYou’ve spent ages carefully designing your website, crafting copy to encourage as many users as possible to purchase your product.
But they aren’t. And you don’t know why.
The good news is you don’t have to remain in the dark. Collecting and analysing web analytics lets you understand how your users behave on your site and why they aren’t converting.
But before you can do that, you need to know what those metrics and KPIs mean. That’s why this article is taking things back to basics. Below, we’ll show you which metrics to track, what they mean and how to choose the best web analytics platform.
What is web analytics ?
Web analytics is the process of collecting, analysing and reporting website data to understand how users behave on your website. Web analytics platforms like Matomo collect this data by adding a code line to every site page.
Why is it important to track web analytics ?
There are plenty of reasons you should start tracking web analytics, including the following :
Analyse user behaviour
Being able to analyse user behaviour is the most important reason to track website analytics. After all, you can’t improve your website’s conversion rate if you don’t know what users do on your site.
A web analytics platform can show you how users move around your site, the links they click on and the forms they fill in.
Improve site experience
Web analytics is a fantastic way to identify issues and find areas where your site could improve. You could look at your site’s exit pages, for example, and see why so many users leave your site when viewing one of these pages and what you can do to fix it.
It can also teach you about your user’s preferences so you can improve the user experience in the future. Maybe they always click a certain type of button or prefer one page’s design over another. Whatever the case, you can use the data to make your site more user-friendly and increase conversions.
Boost marketing efforts
Web analytics is one of the best ways to understand your marketing efforts and learn how to improve them.
A good platform can collect valuable data about your marketing campaigns, including :
- Where users came from
- What actions these users take on your site
- Which traffic sources create the most conversions
This information can help you decide which marketing campaigns send the best users to your site and generate the highest ROI.
Make informed decisions
Ultimately, web analytics simplifies decision-making for your website and marketing efforts by relying on concrete data instead of guesswork.
Rather than wonder why users aren’t adding products to their shopping cart or signing up for your newsletter, you can analyse how they behave and use that information to hypothesise how you can improve conversions. Web analytics will even give you the data to confirm whether you were right or wrong.
What are the key metrics you should track ?
Getting your head around web analytics means knowing the most important metrics to track. Below are seven key metrics and how to track them using Matomo.
Traffic
Traffic is the number of people visiting your website over a period of time. It is the lifeblood of your website since the more visits your site receives, the more revenue it stands to generate.
However, simply having a high volume of visitors does not guarantee substantial revenue. To maximise your success, focus on attracting your ideal customers and generating quality traffic from those who are most likely to engage with your offerings.
Ideally, you should be seeing an upward trend in traffic over time though. The longer your website has been published and the more quality and targeted content you create, the more traffic you should receive.
Matomo offers multiple ways to check your website’s traffic :
The visits log report in Matomo is perfect if you want a granular view of your visitors.
It shows you each user session and get a detailed picture of each user, including :
- Their geographic location
- The number of actions they took
- How they found your site
- The length of time they stayed
- Their device type
- What browser they are using
- The keyword they used to find your site
Traffic sources
Traffic sources show how users access your website. They can enter via a range of traffic sources, including search engines, email and direct visits, for instance.
Matomo has five default traffic source types :
- Search engine – visitors from search platforms (like Google, Bing, etc.)
- Direct traffic – individuals who directly type your website’s URL into their browser or have it bookmarked, bypassing search engines or external links
- Websites – visits from other external sites
- Campaigns – traffic resulting from specific marketing initiatives (like a newsletter or ad campaign, for instance)
- Social networks – visitors who access your website through various social media platforms (such as Facebook, LinkedIn, Instagram. etc.)
But each of these can be broken into more granular sources. Take organic traffic from search engines, for example :
Matomo tracks visits from each search engine, showing you how many visits you had in total, how many actions those visitors took, and the average amount of time those visitors spent on your site.
You can even integrate Google, Bing and Yahoo search consoles to monitor keyword performance and enhance your search engine optimisation efforts.
Pageviews
Whenever a browser loads a page, your web analytics tool records a pageview. This term, pageview, represents the count of unique times a page on your website is loaded.
You can track pageviews in Matomo by opening the Pages tab in the Behaviour section of the main navigation.
You can quickly see your site’s most visited pages in this report in Matomo.
Be careful of deriving too much meaning from pageviews. Just because a page has lots of views, doesn’t necessarily mean it’s quality or valuable. There are a couple of reasons for this. First, the page might be confusing, so users have to keep revisiting it to understand the content. Second, it could be the default page most visitors land on when they enter your site, like the homepage.
While pageviews offer insights, it’s important to dig deeper into user behaviour and other metrics to truly gauge a page’s importance and impact.
Average time on page
Time on page is the amount of time users spend on the page on average. You can see average time on page in Matomo’s page analytics report.
A low time on page score isn’t necessarily a bad thing. Users will naturally spend less time on gateway pages and checkout pages. A short time spent on checkout pages, especially if users are successfully completing their transactions, indicates that the checkout process is easy and seamless.
Conversely, a longer time on blog posts is a positive indicator. It suggests that readers are genuinely engaged with the content.
Try Matomo for Free
Get the web insights you need, without compromising data accuracy.
Returning visitors
Returning visitors measures the number of people who visit your site more than once. It can be expressed as a number or a percentage.
While some analytics tools only show returning visitors as a percentage, Matomo lets you learn more about each of them in the Visitor profile report.
This report offers a full summary of a user’s previous actions, including :
- How many times they’ve visited your site
- The pages they viewed on each visit
- Where they visited from
- The devices they used
- How quickly pages loaded
When people keep coming back to a website, it’s usually a positive sign and means they like the service, content or products. But, it depends on the type of website. If it’s the kind of site where people make one-off purchases, the focus might not be on getting visitors to return. For a site like this, a high number of returning visitors could indicate that the website is confusing or difficult to use.
It’s all about the context – different websites have different goals, and it’s important to keep this in mind when analysing your site.
Conversions
A conversion is when a user takes a desired action on your website. This could be :
- Making a purchase
- Subscribing to your newsletter
- Signing up for a webinar
You can track virtually any action as a conversion in Matomo by setting goals and analysing the goals report.
As you can see in the screenshot above, Matomo shows your conversions plotted over time. You can also see your conversion rate to get a complete picture and assign a value to each conversion to calculate how much revenue each conversion generates.
Bounce rate
A visitor bounces when they leave your website without taking an action or visiting another page.
Typically, you want bounce rate to be low because it means people are engaged with your site and more likely to convert. However, in some cases, a high bounce rate isn’t necessarily bad. It might mean that visitors found what they needed on the first page and didn’t feel the need to look further.
The impact of bounce rate depends on your website’s purpose and goals.
You can view your website’s bounce rate using Matomo’s page analytics report — the same report that shows pageviews.
Try Matomo for Free
Get the web insights you need, without compromising data accuracy.
Web analytics best practices
You should follow several best practices to get the most from website analytics data.
Choose metrics that align with your goals
Only some metrics your analytics platform tracks will be relevant to your business. So don’t waste time analysing all of them.
Instead, focus on the ones that matter most to your business. A marketer for an e-commerce store, for example, might focus on conversion-related metrics like conversion rate and total number of transactions. They might also want to look at campaign-related metrics, like traffic sources and bounce rates, so they can optimise paid ad campaigns accordingly.
A marketer looking to improve their site’s SEO, on the other hand, will want to track SEO web analytics like bounce rate and broken links.
Add context to your data
Don’t take your data at face value. There could be dozens of factors that impact how visitors access and use your site — many of which are outside your control.
For example, you may think an update to your site has sent your conversions crashing when, in reality, a Google algorithm update has negatively impacted your search traffic.
Adding annotations within Matomo can provide invaluable context to your data. These annotations can be used to highlight specific events, changes or external factors that might influence your website metrics.
By documenting significant occurrences, such as website updates, marketing campaigns or algorithm changes, you create a timeline that helps explain fluctuations in your data.
Go further with advanced web analytics features
It’s clear that a web analytics platform is a necessary tool to understand your website’s performance.
However, if you want greater confidence in decision-making, quicker insights and better use of budget and resources, you need an advanced solution with behavioural analytics features like heatmaps, A/B testing and session recordings.
Most web analytics solutions don’t offer these advanced features, but Matomo does, so we’ll be showcasing Matomo’s behavioural analytics features.
Now, if you don’t have a Matomo account, you can try it free for 21-days to see if it’s the right tool for you.
A heatmap, like the example above, makes it easy to discover where your users pay attention, which part of your site they have problems with, and how they convert. It adds a layer of qualitative data to the facts offered by your web analytics tool.
Similarly, session recordings will offer you real-time playbacks of user interactions, helping you understand their navigation patterns, identify pain points and gain insights into the user experience.
Then you can run experiments bu using A/B testing to compare different versions of your website or specific elements, allowing you to make informed decisions based on actual user preferences and behaviour. For instance, you can compare different headlines, images, page layouts or call-to-action buttons to see which resonates better with your audience.
Together, these advanced features will give you the confidence to optimise your website, improve user satisfaction and make data-driven decisions that positively impact your business.
Try Matomo for Free
Get the web insights you need, without compromising data accuracy.
How to choose a web analytics tool
A web analytics tool is the best way to track the above metrics. Choose the best one for your company by following the steps below.
Look for the right features
Most popular web analytics platforms, like Google Analytics, will offer the same core features like tracking website traffic, monitoring conversions and generating reports.
But it’s the added features that set great tools apart. Do you need specific tools to measure the performance of your e-commerce store, for example ? What about paid ad performance, A/B testing or form analytics ?
By understanding exactly what you need from an analytics platform, you can make an informed choice.
Think about data accuracy
Data accuracy is one of the biggest issues with analytics tools. Many users block cookies or opt out of tracking, making it difficult to get a clear picture of user behaviour — and meaning that you have to think about how your user data will be collected with your chosen platform.
Google Analytics, for instance, uses data sampling to make assumptions about traffic levels rather than relying on accurate data. This can lead to inaccurate reports and false conclusions.
It’s why Matomo doesn’t use data sampling and provides 100% accurate data.
Understand how you’ll deal with data privacy
Data privacy is another big concern for analytics users. Several major analytics platforms aren’t compatible with regional data privacy laws like GDPR, which can impact your ability to collect data in these regions.
It’s why many companies trust privacy-focused analytics tools that abide by regulations without impacting your ability to collect data. Matomo is a market leader in this respect and is one of the few web analytics tools that the Centre for Data Privacy Protection in France has said is exempt from tracking consent requirements.
Many government agencies across Europe, Asia, Africa and North America, including organisations like the United Nations and European Commission, rely on Matomo for web analytics.
Conclusion
Web analytics is a powerful tool that helps you better understand your users, improve your site’s performance and boost your marketing efforts.
If you want a platform that offers advanced features, 100% accurate data and protects your users’ privacy, then look no further than Matomo.
Try Matomo free for 21 days, no credit card required.
-
TCP connection refused with FFMPEG
2 février 2017, par SamulOFFICIAL EDIT :
I thank you so much for your help but I am still encountering problems.
My ffserver.conf file is like this :
# Port on which the server is listening. You must select a different
# port from your standard HTTP web server if it is running on the same
# computer.
HTTPPort 8090
# Address on which the server is bound. Only useful if you have
# several network interfaces.
HTTPBindAddress 0.0.0.0
# Number of simultaneous HTTP connections that can be handled. It has
# to be defined *before* the MaxClients parameter, since it defines the
# MaxClients maximum limit.
MaxHTTPConnections 2000
# Number of simultaneous requests that can be handled. Since FFServer
# is very fast, it is more likely that you will want to leave this high
# and use MaxBandwidth, below.
MaxClients 1000
# This the maximum amount of kbit/sec that you are prepared to
# consume when streaming to clients.
MaxBandwidth 1000
# Access log file (uses standard Apache log file format)
# '-' is the standard output.
CustomLog -
##################################################################
# Definition of the live feeds. Each live feed contains one video
# and/or audio sequence coming from an ffmpeg encoder or another
# ffserver. This sequence may be encoded simultaneously with several
# codecs at several resolutions.
<feed>
# You must use 'ffmpeg' to send a live feed to ffserver. In this
# example, you can type:
#
# ffmpeg http://localhost:8090/feed1.ffm
# ffserver can also do time shifting. It means that it can stream any
# previously recorded live stream. The request should contain:
# "http://xxxx?date=[YYYY-MM-DDT][[HH:]MM:]SS[.m...]".You must specify
# a path where the feed is stored on disk. You also specify the
# maximum size of the feed, where zero means unlimited. Default:
# File=/tmp/feed_name.ffm FileMaxSize=5M
File /tmp/feed1.ffm
FileMaxSize 200K
# You could specify
# ReadOnlyFile /saved/specialvideo.ffm
# This marks the file as readonly and it will not be deleted or updated.
# Specify launch in order to start ffmpeg automatically.
# First ffmpeg must be defined with an appropriate path if needed,
# after that options can follow, but avoid adding the http:// field
#Launch ffmpeg
# Only allow connections from localhost to the feed.
#ACL allow 127.0.0.1
#ACL allow 189.34.0.158
</feed>
##################################################################
# Now you can define each stream which will be generated from the
# original audio and video stream. Each format has a filename (here
# 'test1.mpg'). FFServer will send this stream when answering a
# request containing this filename.
<stream>
# coming from live feed 'feed1'
Feed feed1.ffm
# Format of the stream : you can choose among:
# mpeg : MPEG-1 multiplexed video and audio
# mpegvideo : only MPEG-1 video
# mp2 : MPEG-2 audio (use AudioCodec to select layer 2 and 3 codec)
# ogg : Ogg format (Vorbis audio codec)
# rm : RealNetworks-compatible stream. Multiplexed audio and video.
# ra : RealNetworks-compatible stream. Audio only.
# mpjpeg : Multipart JPEG (works with Netscape without any plugin)
# jpeg : Generate a single JPEG image.
# asf : ASF compatible streaming (Windows Media Player format).
# swf : Macromedia Flash compatible stream
# avi : AVI format (MPEG-4 video, MPEG audio sound)
Format mpeg
# Bitrate for the audio stream. Codecs usually support only a few
# different bitrates.
AudioBitRate 32
# Number of audio channels: 1 = mono, 2 = stereo
AudioChannels 1
# Sampling frequency for audio. When using low bitrates, you should
# lower this frequency to 22050 or 11025. The supported frequencies
# depend on the selected audio codec.
AudioSampleRate 44100
# Bitrate for the video stream
VideoBitRate 64
# Ratecontrol buffer size
VideoBufferSize 40
# Number of frames per second
VideoFrameRate 3
# Size of the video frame: WxH (default: 160x128)
# The following abbreviations are defined: sqcif, qcif, cif, 4cif, qqvga,
# qvga, vga, svga, xga, uxga, qxga, sxga, qsxga, hsxga, wvga, wxga, wsxga,
# wuxga, woxga, wqsxga, wquxga, whsxga, whuxga, cga, ega, hd480, hd720,
# hd1080
VideoSize 160x128
# Transmit only intra frames (useful for low bitrates, but kills frame rate).
#VideoIntraOnly
# If non-intra only, an intra frame is transmitted every VideoGopSize
# frames. Video synchronization can only begin at an intra frame.
VideoGopSize 12
# More MPEG-4 parameters
# VideoHighQuality
# Video4MotionVector
# Choose your codecs:
#AudioCodec mp2
#VideoCodec mpeg1video
# Suppress audio
#NoAudio
# Suppress video
#NoVideo
#VideoQMin 3
#VideoQMax 31
# Set this to the number of seconds backwards in time to start. Note that
# most players will buffer 5-10 seconds of video, and also you need to allow
# for a keyframe to appear in the data stream.
#Preroll 15
# ACL:
# You can allow ranges of addresses (or single addresses)
#ACL ALLOW <first address="address"> <last address="address">
# You can deny ranges of addresses (or single addresses)
#ACL DENY <first address="address"> <last address="address">
# You can repeat the ACL allow/deny as often as you like. It is on a per
# stream basis. The first match defines the action. If there are no matches,
# then the default is the inverse of the last ACL statement.
#
# Thus 'ACL allow localhost' only allows access from localhost.
# 'ACL deny 1.0.0.0 1.255.255.255' would deny the whole of network 1 and
# allow everybody else.
</last></first></last></first></stream>
##################################################################
# Example streams
# Multipart JPEG
#<stream>
#Feed feed1.ffm
#Format mpjpeg
#VideoFrameRate 2
#VideoIntraOnly
#NoAudio
#Strict -1
#</stream>
# Single JPEG
#<stream>
#Feed feed1.ffm
#Format jpeg
#VideoFrameRate 2
#VideoIntraOnly
##VideoSize 352x240
#NoAudio
#Strict -1
#</stream>
# Flash
#<stream>
#Feed feed1.ffm
#Format swf
#VideoFrameRate 2
#VideoIntraOnly
#NoAudio
#</stream>
# ASF compatible
<stream>
Feed feed1.ffm
Format asf
VideoFrameRate 15
VideoSize 352x240
VideoBitRate 256
VideoBufferSize 40
VideoGopSize 30
AudioBitRate 64
StartSendOnKey
</stream>
# MP3 audio
#<stream>
#Feed feed1.ffm
#Format mp2
#AudioCodec mp3
#AudioBitRate 64
#AudioChannels 1
#AudioSampleRate 44100
#NoVideo
#</stream>
# Ogg Vorbis audio
#<stream>
#Feed feed1.ffm
#Metadata title "Stream title"
#AudioBitRate 64
#AudioChannels 2
#AudioSampleRate 44100
#NoVideo
#</stream>
# Real with audio only at 32 kbits
#<stream>
#Feed feed1.ffm
#Format rm
#AudioBitRate 32
#NoVideo
#NoAudio
#</stream>
# Real with audio and video at 64 kbits
#<stream>
#Feed feed1.ffm
#Format rm
#AudioBitRate 32
#VideoBitRate 128
#VideoFrameRate 25
#VideoGopSize 25
#NoAudio
#</stream>
##################################################################
# A stream coming from a file: you only need to set the input
# filename and optionally a new format. Supported conversions:
# AVI -> ASF
#<stream>
#File "/usr/local/httpd/htdocs/tlive.rm"
#NoAudio
#</stream>
#<stream>
#File "/usr/local/httpd/htdocs/test.asf"
#NoAudio
#Metadata author "Me"
#Metadata copyright "Super MegaCorp"
#Metadata title "Test stream from disk"
#Metadata comment "Test comment"
#</stream>
##################################################################
# RTSP examples
#
# You can access this stream with the RTSP URL:
# rtsp://localhost:5454/test1-rtsp.mpg
#
# A non-standard RTSP redirector is also created. Its URL is:
# http://localhost:8090/test1-rtsp.rtsp
#<stream>
#Format rtp
#File "/usr/local/httpd/htdocs/test1.mpg"
#</stream>
# Transcode an incoming live feed to another live feed,
# using libx264 and video presets
#<stream>
#Format rtp
#Feed feed1.ffm
#VideoCodec libx264
#VideoFrameRate 24
#VideoBitRate 100
#VideoSize 480x272
#AVPresetVideo default
#AVPresetVideo baseline
#AVOptionVideo flags +global_header
#
#AudioCodec libfaac
#AudioBitRate 32
#AudioChannels 2
#AudioSampleRate 22050
#AVOptionAudio flags +global_header
#</stream>
##################################################################
# SDP/multicast examples
#
# If you want to send your stream in multicast, you must set the
# multicast address with MulticastAddress. The port and the TTL can
# also be set.
#
# An SDP file is automatically generated by ffserver by adding the
# 'sdp' extension to the stream name (here
# http://localhost:8090/test1-sdp.sdp). You should usually give this
# file to your player to play the stream.
#
# The 'NoLoop' option can be used to avoid looping when the stream is
# terminated.
#<stream>
#Format rtp
#File "/usr/local/httpd/htdocs/test1.mpg"
#MulticastAddress 224.124.0.1
#MulticastPort 5000
#MulticastTTL 16
#NoLoop
#</stream>
##################################################################
# Special streams
# Server status
<stream>
Format status
# Only allow local people to get the status
ACL allow localhost
ACL allow 192.168.0.0 192.168.255.255
#FaviconURL http://pond1.gladstonefamily.net:8080/favicon.ico
</stream>
# Redirect index.html to the appropriate site
<redirect>
URL http://www.ffmpeg.org/
</redirect>I started my server and executed :
ffserver -d -f /usr/share/doc/ffmpeg-2.6.8/ffserver.confNo error message and everything looks fine.
After that I execute this (in your answer, I think you forgot the port number) :
ffmpeg -i "rtsp://200.180.90.95:554/onvif1" -r 25 -s 640x480 -c:v libx264 -flags +global_header -f flv "http://45.79.207.38:8090/feed1.ffm"Then I get this log :
libavutil 54. 20.100 / 54. 20.100
libavcodec 56. 26.100 / 56. 26.100
libavformat 56. 25.101 / 56. 25.101
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 11.102 / 5. 11.102
libavresample 2. 1. 0 / 2. 1. 0
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 1.100 / 1. 1.100
libpostproc 53. 3.100 / 53. 3.100
[h264 @ 0x1a23580] RTP: missed 1 packets
[pcm_alaw @ 0x1a24360] RTP: missed 2 packets
[h264 @ 0x1a23580] RTP: missed 1 packets
Invalid UE golomb code
[h264 @ 0x1a23580] cbp too large (3199971767) at 76 33
[h264 @ 0x1a23580] error while decoding MB 76 33
[h264 @ 0x1a23580] Cannot use next picture in error concealment
[h264 @ 0x1a23580] concealing 933 DC, 933 AC, 933 MV errors in P frame
[h264 @ 0x1a23580] RTP: missed 1 packets
[h264 @ 0x1a23580] cbp too large (62) at 50 24
[h264 @ 0x1a23580] error while decoding MB 50 24
[h264 @ 0x1a23580] Cannot use next picture in error concealment
[h264 @ 0x1a23580] concealing 1679 DC, 1679 AC, 1679 MV errors in P frame
[h264 @ 0x1a23580] RTP: missed 2 packets
[h264 @ 0x1a23580] Cannot use next picture in error concealment
[h264 @ 0x1a23580] concealing 1965 DC, 1965 AC, 1965 MV errors in P frame
[pcm_alaw @ 0x1a24360] RTP: missed 1 packets
Last message repeated 1 times
[h264 @ 0x1a23580] RTP: missed 3 packets
[h264 @ 0x1a23580] mb_type 49 in P slice too large at 74 25
[h264 @ 0x1a23580] error while decoding MB 74 25
[h264 @ 0x1a23580] Cannot use next picture in error concealment
[h264 @ 0x1a23580] concealing 1575 DC, 1575 AC, 1575 MV errors in P frame
[h264 @ 0x1a23580] RTP: missed 2 packets
[h264 @ 0x1a23580] P sub_mb_type 29 out of range at 30 26
[h264 @ 0x1a23580] error while decoding MB 30 26
[h264 @ 0x1a23580] Cannot use next picture in error concealment
[h264 @ 0x1a23580] concealing 1539 DC, 1539 AC, 1539 MV errors in P frame
[h264 @ 0x1a23580] RTP: missed 1 packets
[h264 @ 0x1a23580] out of range intra chroma pred mode at 72 29
[h264 @ 0x1a23580] error while decoding MB 72 29
[h264 @ 0x1a23580] Cannot use next picture in error concealment
[h264 @ 0x1a23580] concealing 1257 DC, 1257 AC, 1257 MV errors in P frame
[h264 @ 0x1a23580] RTP: missed 3 packets
[h264 @ 0x1a23580] negative number of zero coeffs at 48 5
[h264 @ 0x1a23580] error while decoding MB 48 5
[h264 @ 0x1a23580] Cannot use next picture in error concealment
[h264 @ 0x1a23580] concealing 3201 DC, 3201 AC, 3201 MV errors in P frame
[pcm_alaw @ 0x1a24360] RTP: missed 1 packets
[rtsp @ 0x1a20ee0] decoding for stream 0 failed
Guessed Channel Layout for Input Stream #0.1 : mono
Input #0, rtsp, from 'rtsp://200.180.90.95:554/onvif1':
Metadata:
title : H.264 Video, RtspServer_0.0.0.2
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Video: h264 (Baseline), yuv420p, 1280x720, 90k tbr, 90k tbn, 180k tbc
Stream #0:1: Audio: pcm_alaw, 8000 Hz, 1 channels, s16, 64 kb/s
[libx264 @ 0x1b728a0] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2
[libx264 @ 0x1b728a0] profile High, level 3.0
[libx264 @ 0x1b728a0] 264 - core 142 r2495 6a301b6 - H.264/MPEG-4 AVC codec - Copyleft 2003-2014 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=1 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
[flv @ 0x1a66300] FLV does not support sample rate 8000, choose from (44100, 22050, 11025)
[flv @ 0x1a66300] Audio codec mp3 not compatible with flv
Output #0, flv, to 'http://45.79.207.38:8090/feed1.ffm':
Metadata:
title : H.264 Video, RtspServer_0.0.0.2
encoder : Lavf56.25.101
Stream #0:0: Video: h264 (libx264) ([7][0][0][0] / 0x0007), yuv420p, 640x480, q=-1--1, 25 fps, 1k tbn, 25 tbc
Metadata:
encoder : Lavc56.26.100 libx264
Stream #0:1: Audio: mp3 (libmp3lame) ([2][0][0][0] / 0x0002), 8000 Hz, mono, s16p
Metadata:
encoder : Lavc56.26.100 libmp3lame
Stream mapping:
Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
Stream #0:1 -> #0:1 (pcm_alaw (native) -> mp3 (libmp3lame))
Could not write header for output file #0 (incorrect codec parameters ?): Function not implementedI am doing this in a clean install of CENTOS, no customization. Could you please helpe me ?
Syndiquer tout le site
