Recherche avancée

Sur d’autres sites (6495)

• What is Web Log Analytics and Why You Should Use It

  26 juin 2024, par Erin

  Can’t use JavaScript tracking on your website ? Need a more secure and privacy-friendly way to understand your website visitors ? Web log analytics is your answer. This method pulls data directly from your server logs, offering a secure and privacy-respecting alternative.  

  In this blog, we cover what web log analytics is, how it compares to JavaScript tracking, who it is best suited for, and why it might be the right choice for you. 

  What are server logs ? 

  Before diving in, let’s start with the basics : What are server logs ? Think of your web server as a diary that notes every visit to your website. Each time someone visits, the server records details like : 

  • User agent : Information about the visitor’s browser and operating system. 

  • Timestamp : The exact time the request was made. 

  • Requested URL : The specific page or resource the visitor requested. 

  These “diary entries” are called server logs, and they provide a detailed record of all interactions with your website. 

  Server log example 

  Here’s what a server log looks like : 

  192.XXX.X.X – – [24/Jun/2024:14:32:01 +0000] “GET /index.html HTTP/1.1” 200 1024 “https://www.example.com/referrer.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  192.XXX.X.X – – [24/Jun/2024:14:32:02 +0000] “GET /style.css HTTP/1.1” 200 3456 “https://www.example.com/index.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  192.XXX.X.X – – [24/Jun/2024:14:32:03 +0000] “GET /script.js HTTP/1.1” 200 7890 “https://www.example.com/index.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  192.XXX.X.X – – [24/Jun/2024:14:32:04 +0000] “GET /images/logo.png HTTP/1.1” 200 1234 “https://www.example.com/index.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  Breakdown of the log entry 

  Each line in the server log represents a single request made by a visitor to your website. Here’s a detailed breakdown of what each part means : 

  • IP Address : 192.XXX.X.X 
    • This is the IP address of the visitor’s device. 
  • User Identifier : – – 
    • These fields are typically used for user identification and authentication, which are not applicable here, hence the hyphens. 
  • Timestamp : [24/Jun/2024:14:32:01 +0000] 
  • • • The date and time of the request, including the timezone. 
  • Request Line : “GET /index.html HTTP/1.1” 
    • The request method (GET), the requested resource (/index.html), and the HTTP version (HTTP/1.1). 
  • Response Code : 200 
    • The HTTP status code indicates the result of the request (200 means OK). 
  • Response Size : 1024 
    • The size of the response in bytes. 
  • Referrer : “https://www.example.com/referrer.html“ 
    • The URL of the referring page that led the visitor to the current page. 
  • User Agent : “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 
    • Information about the visitor’s browser and operating system. 

  In the example above, there are multiple log entries for different resources (HTML page, CSS file, JavaScript file, and an image). This shows that when a visitor loads a webpage, multiple requests are made to load all the necessary resources. 

  What is web log analytics ? 

  Web log analytics is one of many methods for tracking visitors to your site.  

  

  Web log analytics is the process of analysing server log files to track and understand website visitors. Unlike traditional methods that use JavaScript tracking codes embedded in web pages, web log analytics pulls data directly from these server logs. 

  How it works : 

  1. Visitor request : A visitor’s browser requests your website. 
  2. Server logging : The server logs the request details. 
  3. Analysis : These logs are analysed to extract useful information about your visitors and their activities. 

  Web log analytics vs. JavaScript tracking 

  JavaScript tracking 

  JavaScript tracking is the most common method used to track website visitors. It involves embedding a JavaScript code snippet into your web pages. This code collects data on visitor interactions and sends it to a web analytics platform. 

  

  Differences and benefits :
  

  Privacy : 

  • Web log analytics : Since it doesn’t require embedding tracking codes, it is considered less intrusive and helps maintain higher privacy standards. 

  • JavaScript tracking : Embeds tracking codes directly on your website, which can be more invasive and raise privacy concerns. 

  Ease of setup : 

  • Web log analytics : No need to modify your website’s code. All you need is access to your server logs. 

  • JavaScript tracking : Requires adding tracking code on your web pages. This is generally an easier setup process.  

  Data collection : 

  • Web log analytics : Contain requests of users with adblockers (ghostery, adblock, adblock plus, privacy badger, etc.) sometimes making it more accurate. However, it may miss certain interactive elements like screen resolution or user events. It may also over-report data.  

  • JavaScript tracking : Can collect a wide range of data, including Custom dimensions, Ecommerce tracking, Heatmaps, Session recordings, Media and Form analytics, etc. 

  Why choose web log analytics ? 

  Enhanced privacy 

  Avoiding embedded tracking codes means there’s no JavaScript running on your visitors’ browsers. This significantly reduces the risk of data leakage and enhances overall privacy. 

  Comprehensive data collection 

  It isn’t affected by ad blockers or browser tracking protections, ensuring you capture more complete and accurate data about your visitors. 

  Historical data analysis 

  You can import and analyse historical log files, giving you insights into long-term visitor behaviour and trends. 

  Simple setup 

  Since it relies on server logs, there’s no need to alter your website’s code. This makes setup straightforward and minimises potential technical issues. 

  Who should use web log analytics ? 

  Web log analytics is particularly suited for businesses that prioritise data privacy and security.

  Organisations that handle sensitive data, such as banks, healthcare providers, and government agencies, can benefit from the enhanced privacy.  

  By avoiding JavaScript tracking, these entities minimise data exposure and comply with strict privacy regulations like Sarbanes Oxley and PCI. 

  Why use Matomo for web log analytics ? 

  Matomo stands out as a top choice for web log analytics because it prioritises privacy and data ownership

  

  Here’s why : 

  • Complete data control : You own all your data, so you don’t have to worry about third-party access. 
  • IP anonymisation : Matomo anonymises IP addresses to further protect user privacy. 
  • Bot filtering : Automatically excludes bots from your reports, ensuring you get accurate data. 
  • Simple migration : You can easily switch from other tools like AWStats by importing your historical logs into Matomo. 
  • Server log recognition : Recognises most server log formats (Apache, Nginx, IIS, etc.). 

  Start using web log analytics 

  Web log analytics offers a secure, privacy-focused alternative to traditional JavaScript tracking methods. By analysing server logs, you get valuable insights into your website traffic while maintaining high privacy standards.  

  If you’re serious about privacy and want reliable data, give Matomo’s web log analytics a try.  

  Start your 21-day free trial now. No credit card required. 

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

• A Beginner’s Guide to Omnichannel Analytics

  14 avril 2024, par Erin

  Linear customer journeys are as obsolete as dial-up internet and floppy disks. As a marketing manager, you know better than anyone that customers interact with your brand hundreds of times across dozens of channels before purchasing. That can make tracking them a nightmare unless you build an omnichannel analytics solution. 

  Alas, if only it were that simple. 

  Unfortunately, it’s not enough to collect data on your customers’ complex journeys just by buying an omnichannel platform. You need to generate actionable insights by using marketing attribution to tie channels to conversions. 

  This article will explain how to build a useful omnichannel analytics solution that lets you understand and improve the customer journey.

  What is omnichannel analytics ?

  Omnichannel analytics collects and analyses customer data from every touchpoint and device. The goal is to collect all this omnichannel data in one place, creating a single, real-time, unified view of your customer’s journey.

  

  Unfortunately, most businesses haven’t achieved this yet. As Karen Lellouche Tordjman and Marco Bertini say :

  “Despite all the buzz around the concept of omnichannel, most companies still view customer journeys as a linear sequence of standardised touchpoints within a given channel. But the future of customer engagement transforms touchpoints from nodes along a predefined distribution path to full-blown portals that can serve as points of sale or pathways to many other digital and virtual interactions. They link to chatbots, kiosks, robo-advisors, and other tools that customers — especially younger ones — want to engage with.”

  However, doing so is more important than ever — especially when consumers have over 300 digital touchpoints, and the average number of touchpoints in the B2B buyer journey is 27.

  Not only that, but customers expect personalised experiences across every platform — that’s the kind you can only create when you have access to omnichannel data.

  

  What might omnichannel analytics look like in practice for an e-commerce store ?

  An online store would integrate data from channels like its website, mobile app, social media accounts, Google Ads and customer service records. This would show how customers find its brand, how they use each channel to interact with it and which channels convert the most customers. 

  This would allow the e-commerce store to tailor marketing channels to customers’ needs. For instance, they could focus social media use on product discovery and customer support. Google Ads campaigns could target the best-converting products. While all this is happening, the store could also ensure every channel looks the same and delivers the same experience. 

  What are the benefits of omnichannel analytics ?

  Why go to all the trouble of creating a comprehensive view of the customer’s experience ? Because you stand to gain some pretty significant benefits when implementing omnichannel analytics.

  

  Understand the customer journey

  You want to understand how your customers behave, right ? No other method will allow you to fully understand your customer journey the way omnichannel analytics does. 

  It doesn’t matter how customers engage with your brand — whether that’s your website, app, social media profiles or physical stores — omnichannel analytics capture every interaction.

  With this 360-degree view of your customers, it’s easy to understand how they move between channels, where they encounter issues and what bottlenecks prevent them from converting. 

  Deliver better personalisation

  We don’t have to tell you that personalisation matters. But do you know just how important it is ? Since 56% of customers will become repeat buyers after a personalised experience, delivering them as often as possible is critical. 

  Omnichannel analytics helps in your quest for personalisation by highlighting the individual preferences of customer segments. For example, e-commerce stores can use omnichannel analytics to understand how shoppers behave across different devices and tailor their offers accordingly. 

  Upgrade the customer experience

  Omnichannel analytics gives you the insights to improve every aspect of the customer experience. 

  For starters, you can ensure a consistent brand experience across all your top channels by making sure they look and behave the same.

  Then, you can use omnichannel insights to tailor each channel to your customers’ requirements. For example, most people interacting with your brand on social media may seek support. Knowing that you can create dedicated support accounts to assist users. 

  Improve marketing campaigns

  Which marketing campaigns or traffic sources convert the most customers ? How can you improve these campaigns ? Omnichannel analytics has the answers. 

  When you implement omnichannel analytics you automatically track the performance of every marketing channel by attributing each conversion to one or more traffic sources. This lets you see whether Google Ads bring in more customers than your SEO efforts. Or whether social media ads are the most profitable acquisition channel. 

  Armed with this information, you can improve your marketing efforts — either by focusing on your profitable channels or rectifying problems that stop less profitable channels from converting.

  What are the challenges of omnichannel analytics ?

  There are three challenges when implementing an omnichannel analytics solution :

  

  • Complex customer journeys : Customer journeys aren’t linear and can be incredibly difficult to track. 
  • Regulatory and privacy issues : When you start gathering customer data, you quickly come up against consumer privacy laws. 
  • No underlying goal : There has to be a reason to go to all this effort, but brands don’t always have goals in mind before they start. 

  You can’t do anything about the first challenge. 

  After all, your customer journey will almost never be linear. And isn’t the point of implementing an omnichannel solution to understand these complex journeys in the first place ? Once you set up omnichannel analytics, these journeys will be much easier to decipher. 

  As for the other two :

  Using the right software that respects user privacy and complies with all major privacy laws will avoid regulatory issues. Take Matomo, for instance. Our software was designed with privacy in mind and is configured to follow the strictest privacy laws, such as GDPR. 

  Tying omnichannel analytics to marketing attribution will solve the final challenge by giving your omnichannel efforts a goal. When you tie omnichannel analytics to your marketing efforts, you aren’t just getting a 360-degree view of your customer journey for the sake of it. You are getting that view to improve your marketing efforts and increase sales.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  How to set up an omnichannel analytics solution

  Want to set up a seamless analytical environment that incorporates data from every possible source ? Follow these five steps :

  Choose one or more analytics providers

  You can use several tools to build an omnichannel analytics solution. These include web and app analytics tools, customer data platforms that centralise first-party data and business intelligence tools (typically used for visualisation). 

  Which tools you use will depend on your goals and your budget — the loftier your ambitions and the higher your budget, the more tools you can use. 

  Ideally, you should use as few tools as possible to capture your data. Most teams won’t need business intelligence platforms, for example. However, you may or may not need both an analytics platform and a customer data platform. Your decision will depend on how many channels your customers use and how well your analytics tool tracks everything.

  If it can capture web and app usage while integrating with third-party platforms like your back-end e-commerce platform, then it’s probably enough.

  Collect accurate data at every touchpoint 

  Your omnichannel analytics efforts hinge on the quantity and quality of data you can collect. You want to gather data from every touchpoint possible and store that data in as few places as possible. That’s why choosing as few tools as possible in the step above is so important. 

  So, where should you start ? Common data sources include :

  • Your website
  • Apps (iOS and Android)
  • Social media profiles
  • ERPs
  • PoS systems

  At the same time, make sure you’re tracking all relevant metrics. Revenue, customer engagement and conversion-focused metrics like conversion rate, dwell time, cart abandonment rate and churn rate are particularly important. 

  Set up marketing attribution

  Setting up marketing attribution (also known as multi-touch attribution) is essential to tie omnichannel data to business goals. It’s the only way to know exactly how valuable each marketing channel is and where each customer comes from. 

  You’ll want to use multi-touch attribution, given you have data from across the customer journey.

  

  Multi-touch attribution models can include (but are not limited to) :

  • Linear : where each touchpoint is given equal weighting
  • Time decay : where touchpoints are more valuable the nearer they are to conversion
  • Position-based : where the first and last touch points are more valuable than all the others. 

  You don’t have to use just one of the models above, however. One of the benefits of using a web analytics tool like Matomo is that you can choose between different attribution models and compare them.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  Create reports that help you visualise data

  Dashboards are your friend here. They’ll let you see KPIs at a glance, allowing you to keep track of day-to-day changes in your customer journey. Ideally, you’ll want a platform that lets you customise dashboard widgets so only relevant KPIs are shown. 

  

  Setting up standard and custom reports is also important. Custom reports allow you to choose metrics and dimensions that align with your goals. They will also allow you to present your data most meaningfully to your team, increasing the likelihood they act upon insights. 

  Analyse data and take action

  Now that you have customer journey data at your fingertips, it’s time to analyse it. After all, there’s no point in implementing an omnichannel analytics solution if you aren’t going to take action. 

  If you’re unsure where to start, re-read the benefits we listed at the start of this article. You could use your omnichannel insights to improve your marketing campaigns by doubling down on the channels that bring in the best customers.

  Or you could identify (and fix) bottlenecks in the customer journey so customers are less likely to fall out of your funnel between certain channels. 

  Just make sure you take action based on your data alone.

  Make the most of omnichannel analytics with Matomo

  A comprehensive web and app analytics platform is vital to any omnichannel analytics strategy. 

  But not just any solution will do. When privacy regulations impede an omnichannel analytics solution, you need a platform to capture accurate data without breaking privacy laws or your users’ trust. 

  That’s where Matomo comes in. Our privacy-friendly web analytics platform ensures accurate tracking of web traffic while keeping you compliant with even the strictest regulations. Moreover, our range of APIs and SDKs makes it easy to track interactions from all your digital products (website, apps, e-commerce back-ends, etc.) in one place. 

  Try Matomo for free for 21 days. No credit card required.

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

  I accept the terms and conditions and data processing agreement (DPA)

  
  Your information will be used to create an account on our cloud service. For more information please consult our privacy policy.
  
  
  

  Start improving your websites now

  

• FFmpeg av_dump_format showing incorrect output, but ffprobe displays correct metadata

  29 janvier, par グルグル

  I use ffmpeg 7.1 source build on windows and compilation configuration as follow :

  


  configuration:
  --toolchain=msvc
  --arch=x86_64
  --enable-x86asm
  --enable-asm
  --enable-shared
  --enable-w32threads
  --prefix=/D/build


  


  When I use av_dump_format to print metadata of test.mp3, it display the incorrect information.

  


  extern "C"&#xA;{&#xA;#include <libavformat></libavformat>avformat.h>&#xA;}&#xA;&#xA;int main()&#xA;{ &#xA;    av_log_set_level(AV_LOG_DEBUG);&#xA;&#xA;    auto url = "D:/music/test.mp3";&#xA;&#xA;    AVFormatContext* fmt;&#xA;    auto ret = avformat_open_input(&amp;fmt, url, nullptr, nullptr);&#xA;    if (ret &lt; 0)&#xA;    {&#xA;        av_log(nullptr, AV_LOG_ERROR, "Cannot open %s format : %s", url, av_err2str(ret));&#xA;        exit(EXIT_FAILURE);&#xA;    }&#xA;&#xA;    av_dump_format(fmt, 0, url, 0);&#xA;}&#xA;

  


  output

  


  [AVFormatContext @ 000001768E65BC40] Opening 'D:/music/test.mp3' for reading
[file @ 000001768E65C180] Setting default whitelist 'file,crypto,data'
[mp3 @ 000001768E65BC40] Format mp3 probed with size=4096 and score=51
id3v2 ver:4 flags:00 len:35
[mp3 @ 000001768E65BC40] pad 576 576
[mp3 @ 000001768E65BC40] Skipping 0 bytes of junk at 462.
Input #0, mp3, from 'D:/music/test.mp3':
  Metadata:
    encoder         : Lavf58.76.100
  Duration: N/A, bitrate: N/A
  Stream #0:0, 0, 1/14112000: Audio: mp3, 0 channels
      Metadata:
        encoder         : Lavc58.13


  


  You can see the Stream info is useless.

  


  But I use ffprobe which is built with same configuration to print metadata of test.mp3.

  


  It's display normal.

  


  ffprobe version 7.0.1 Copyright (c) 2007-2024 the FFmpeg developers
  built with Microsoft (R) C/C++ Optimizing Compiler Version 19.41.34123 for x64
  configuration: --toolchain=msvc --arch=x86_64 --enable-x86asm --enable-asm --enable-shared --enable-w32threads --prefix=/D/build
  WARNING: library configuration mismatch
  avutil      configuration: --toolchain=msvc --arch=x86_64 --enable-x86asm --enable-asm --enable-shared --enable-w32threads --disable-programs --disable-doc --disable-static --prefix=/D/build
  avcodec     configuration: --toolchain=msvc --arch=x86_64 --enable-x86asm --enable-asm --enable-shared --enable-w32threads --disable-programs --disable-doc --disable-static --prefix=/D/build
  avformat    configuration: --toolchain=msvc --arch=x86_64 --enable-x86asm --enable-asm --enable-shared --enable-w32threads --disable-programs --disable-doc --disable-static --prefix=/D/build
  avdevice    configuration: --toolchain=msvc --arch=x86_64 --enable-x86asm --enable-asm --enable-shared --enable-w32threads --disable-programs --disable-doc --disable-static --prefix=/D/build
  avfilter    configuration: --toolchain=msvc --arch=x86_64 --enable-x86asm --enable-asm --enable-shared --enable-w32threads --disable-programs --disable-doc --disable-static --prefix=/D/build
  swscale     configuration: --toolchain=msvc --arch=x86_64 --enable-x86asm --enable-asm --enable-shared --enable-w32threads --disable-programs --disable-doc --disable-static --prefix=/D/build
  swresample  configuration: --toolchain=msvc --arch=x86_64 --enable-x86asm --enable-asm --enable-shared --enable-w32threads --disable-programs --disable-doc --disable-static --prefix=/D/build
  libavutil      59.  8.100 / 59. 39.100
  libavcodec     61.  3.100 / 61. 19.100
  libavformat    61.  1.100 / 61.  7.100
  libavdevice    61.  1.100 / 61.  3.100
  libavfilter    10.  1.100 / 10.  4.100
  libswscale      8.  1.100 /  8.  3.100
  libswresample   5.  1.100 /  5.  3.100
Input #0, mp3, from 'D:\music\test.mp3':
  Metadata:
    encoder         : Lavf58.76.100
  Duration: 00:05:00.12, start: 0.025057, bitrate: 128 kb/s
  Stream #0:0: Audio: mp3 (mp3float), 44100 Hz, stereo, fltp, 128 kb/s
      Metadata:
        encoder         : Lavc58.13


  


  Why is av_dump_format not correctly showing stream information ? How can I fix it ?