Sur d’autres sites (14054)

• Some H264-mp4 videos can't be loaded by any non-Chromium based web browser

  3 mai 2020, par Laizrod

  I regularly use ffmpeg to encode some videos, blu-ray etc in mp4 files (encoded in H264 and AAC) in order to be played on web browsers.
Chromium based browsers such as Google Chrome or the new Microsoft Edge can play all of my files flawlessly.
But today I noticed that some video files couldn't be loaded by some web browsers. It looks like they can't be loaded by any non-Chromium based web browser. (Safari, Firefox etc..)

  



  So I decided to check out and compare the specs of files that work with any web browser, and files that doesn't work with non-Chromium based browsers.

  



  There's what I got :

  



  

  • Playable by any web browser :

  


  



  General
Complete name                            : /storage/100.mp4
Format                                   : MPEG-4
Format profile                           : Base Media / Version 2
Codec ID                                 : mp42 (isom/iso2/avc1/mp41)
File size                                : 624 MiB
Duration                                 : 23 min 54 s
Overall bit rate                         : 3 648 kb/s
Encoded date                             : UTC 2019-10-02 22:15:27
Tagged date                              : UTC 2019-10-02 22:15:27
Writing application                      : HandBrake 1.2.2 2019022300

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4
Format settings                          : CABAC / 1 Ref Frames
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 1 frame
Format settings, GOP                     : M=3, N=24
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 23 min 54 s
Bit rate                                 : 3 481 kb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Variable
Frame rate                               : 23.976 (24000/1001) FPS
Minimum frame rate                       : 23.974 FPS
Maximum frame rate                       : 23.981 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.070
Stream size                              : 595 MiB (95%)
Encoded date                             : UTC 2019-10-02 22:15:27
Tagged date                              : UTC 2019-10-02 22:15:27
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 23 min 54 s
Bit rate mode                            : Constant
Bit rate                                 : 160 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 44.1 kHz
Frame rate                               : 43.066 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 27.4 MiB (4%)
Title                                    : Stereo
Language                                 : Japanese
Default                                  : Yes
Alternate group                          : 1
Encoded date                             : UTC 2019-10-02 22:15:27
Tagged date                              : UTC 2019-10-02 22:15:27


  



  

  • Unplayable by non-chromium based web browsers :

  


  



  General
Complete name                            : /storage/DL/test.mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/iso2/avc1/mp41)
File size                                : 329 MiB
Duration                                 : 23 min 52 s
Overall bit rate                         : 1 926 kb/s
Writing application                      : Lavf58.20.100

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4
Format settings                          : CABAC / 4 Ref Frames
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 4 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 23 min 52 s
Bit rate                                 : 1 792 kb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 23.976 (24000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.036
Stream size                              : 306 MiB (93%)
Writing library                          : x264 core 155 r2917 0a84d98
Encoding settings                        : cabac=1 / ref=1 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=2 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=34 / lookahead_threads=8 / 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=1 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=10 / rc=crf / mbtree=1 / crf=21.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Language                                 : Japanese
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 23 min 52 s
Bit rate mode                            : Constant
Bit rate                                 : 128 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 21.9 MiB (7%)
Language                                 : Japanese
Default                                  : Yes
Alternate group                          : 1


  



  My knowledge is limited and I'm unable to understand why and which differences are causing my issue.
Can someone identify the problem and help me fix it with ffmpeg ?

  



  Thank you

  


• 5 perfect feature combinations to use with Heatmaps and Session Recordings

  28 janvier 2020, par Jake Thornton — Uncategorized

  Gaining valuable insights by simply creating a heatmap or setting up recordings on your most important web pages is a good start, but using the Heatmaps and Session Recordings features in combination with other Matomo features is where the real magic happens.

  If you’re serious about significantly increasing conversions on your website to impact your bottom line, you need to accurately answer these questions :

  1. Are you analysing the most important pages that influence conversions ?
  2. Are you segmenting heatmaps and recordings towards your most valuable visitors ? 
  3. Are you using these features to create better customer journeys ?
  4. Have you identified current pain points for visitors before setting up heatmaps and recordings ?
  5. Are you learning what content resonates best for your audience ?

  With Matomo Analytics, you have the ability to integrate heatmaps and session recordings with all the features of a powerful web analytics platform, which means you get the complete picture of your visitor’s experience of your website.

  Here are five features that work with Heatmaps and Session Recordings to maximise conversions :

  1. Behaviour feature with Heatmaps

  Before creating heatmaps on pages you think are most important to your website, first check out Behaviour – Pages. Here you get valuable information around unique pageviews, bounce rate, average time on page and exit rates for every page on your website.

  Use this data as your starting point for heatmaps. Here you’ll identify current pain points for your visitors before using heatmaps to analyse their interactions on these pages.

  Here’s how to use the behaviour feature to determine which pages to setup heatmaps on :

  

  • Make sure you know what pages are generating the most unique page views, it could be your blog rather than your homepage
  • Which pages have the highest bounce rates – can you make some quick changes above-the-fold and see if this makes a difference
  • When the average time on page is high, why are visitors so engaged with these pages ? What keeps them reading ? Setup a heatmap to learn more
  • Reduce exit rates by moving them along to other pages on your website
  • Determine some milestones you want to achieve e.g. use heatmaps as your visual guide to improve average time on page, bounce rates and exit rates. A milestone could be that the exit rate for your previous blog was 34%, work towards getting this down to 30%

  Learn more about the Behaviour feature

  2. Ecommerce feature and Custom Segments

  If you run an ecommerce business, you may want to learn only about visitors who are more likely to be your customers. For example, if you find 65% of product sales come from customers based in New York, but visits to your product pages are from every state in the USA, how can you learn more specifically about visitors only from New York ?

  Using Segments to target a particular audience :

  • First, make sure you have created heatmaps and recordings on the popular product pages you want to learn about your visitor’s interactions
  • Note : Make sure the segment you create generates enough pageviews to apply a heatmap for more accurate results. We recommend a minimum of 1,000 page views per sample size.
  • Then create a custom Segment – search Ecommerce and find the Product Name and select the product. Learn how to do this here.

  

  Click on ‘Add a new segment’ or on the ‘edit’ link next to an existing segment name to open the segment editor :

  

  Click on any item on the left to see the list of information you can segment by. In this case search “City”, then select “Is” and in the third column search “New York” (example in the image above) :

  

  You can also use the search box at the bottom to search through the whole list.

  • This will give you insights across the Matomo platform based only on customers who purchased this product
  • Then go to the Ecommerce feature – and find Sales. Here you will learn what your most popular locations are for your product sales.

  

  • Once you know the location you want to segment, go back and update the custom Segment you just created. Click on the edit pencil icon and update it by selecting Add AND condition, and add the sub group you would like to track on the product page. In this example, select City – New York. Click Save & Apply.

  Now you should have successfully created a segment for your popular product page with visitors only from New York.

  Check out the heatmap or recordings you created for this page. You may be very surprised to see how this segment engaged with your website compared to all website visitors.

  Note : If you run a lead generation website you can use the Goals feature instead of Ecommerce to track the success metrics you need.

  Learn more about Segmentation

  3. Visitor Profiles within Session Recordings

  Seeing visitor location, device, OS and browser for your recordings is very valuable, but it’s even more valuable to integrate visitor profiles with session recordings as you get to see everything that visitor has done on your website … ever ! 

  What pages they visited before/after the recording, what actions they took, how long they spent on your website etc. All this is captured in the visitor profile of every individual session recording so you can see where exactly engaged viewers are in their journey with your business, for example :

  • How has this visitor behaved on your website in the past ? 
  • Is this visitor already a customer ? 
  • Is this the visitors first time to your website and
  • What other pages on your website are they interested in seeing in this session ?

  Use the visitor profiles feature within session recordings to understand the users better when watching each session.

  You get the full picture of what role the page you recorded played in the overall experience of your website’s visitor. And more importantly, to see if they took the desired action you wanted them to take.

  

  Learn more about Visitor Profiles

  4. Funnels feature (premium feature)

  The Funnels feature lets you see the customer journey from the first entry page through to the conversion page.

  

  Once you create a funnel, you can see the % of visitors who drop off between pages on their way to converting.

  In our example, you may then see page one to page two has a drop-off rate of 47%. Page two to page three 95% users drop-off rate and page three to page four 97.3% users drop-off rate.

  Why is the drop-off rate so high from page two to page three and why is the drop-off rate so low from page three to page four ?

  So, you may need to simplify things on page one because you may unknowingly be offering your visitor an easy way out of the funnel. Maybe the visitor is stuck reading your content and not understanding the value of your offering.

  Small tip for session recordings …

  With session recordings especially you can see firsthand through live recordings where exactly visitors click away from the page which exits them from your conversion funnel. Take note to see if this is a recurring issue with other visitors, then take action into fixing this hole.

  Whatever the case, work towards reducing drop-off rates through your conversion funnels by discovering where the problems exist, make changes and learn how these changes affect engagement through heatmaps and recordings.

  Learn more about Funnels

  5. A/B Testing feature (premium feature)

  Following on from the example with the Funnels feature, once you identify there is a problem in your conversion funnel, how do you know what is preventing visitors from taking an action that pushes them to the next page in the funnel ? You need to test different variations of content to see what works best for your visitors.

  A/B Testing lets you test a variety of things, including :

  • different headlines 
  • less copy vs more copy 
  • different call-to-actions
  • different colour schemes
  • entirely different page layouts

  

  Once you’ve created two or more variations of specific landing pages in the conversion funnel, see how visitors interacted differently between the variations of landing pages through your heatmaps and recordings.

  

  You may see that your visitors have scrolled further down the page because more content was provided or an important CTA button was clicked more due to a colour change. Whatever the case, using A/B testing with heatmaps and session recordings is an effective combination for increasing user engagement.

  Learn more about A/B Testing

  The conversion rate optimization (CRO) strategy

  CRO is the process of learning what the most valuable content/aspect of your website is and how to best optimize this for your visitors to increase conversion chances. 

  Heatmaps and session recordings play a vital role in this strategy, but it’s how you work these features in tandem with other valuable Matomo features that will give you the most actionable insights you need to grow your business.

  Want to learn how to create an effective CRO strategy ?

  Learn CRO strategies

• How to analyse 404 pages

  1er juillet 2019, par Matomo Core Team — Development, Plugins

  How to analyse “not found” pages (404) in digital analytics

  Have you ever sent out a newsletter and one link wasn’t active yet ? Would you like to know how many users get affected when this happens ? Would you like to know if your visitors are encountering 404 pages ? 

  In this article we’re describing an easy way to analyse “not found” pages on your website with Matomo to increase your visitors’ user experience, user acquisition, and SEO (search engine optimization).

  How to know the number of 404s on my website ?

  There are different ways to get this information. Depending on how your website is built, you may or may not collect this data.

  The easiest way to answer this question is to fire a 404 page on your website, you do this by accessing a wrong url :

  

  As you can see here, in our case, the page title starts with “Page non trouvée” which stands for “Page not found” when translated in English (as the website we are considering here is in French) :

  

  In this example 19 page views have been fired and it generated a bounce rate of 67%. As a result ⅔ of the visits ended here.

  In some cases, the information related to a “not found” page can be found either within the title or within the URL, as some websites redirect you to a specific web page when a page can’t be found.

  If you can’t identify “not found” pages via a page title or a page URL, we strongly advise you to use this specific tracking code method on your 404 page : “How to track error pages in Matomo ?”. 

  You can easily set it with Matomo Tag Manager with a custom HTML tag :

  

  where the trigger is the following :

  

  You will however, have to define this trigger as an exclusion for all the other tags which may conflict with it (here below is the new trigger defined for the generic Matomo tags we are inserting on all pages) :

  

  Once this specific tracking is set, you will be able to track the source of the 404 and will gather all the “not found” pages in a specific group within your Page Title report :

  

  Here, for example, you can identify that the homepage of this website had a link pointing to a 404, in our case it was https://www.webassoc.org/pro-du-web.

  Note that this is just one technique. You could also create a custom dimension report and decide to send the 404 there also.

  How to get notified when a 404 page is visited ?

  Trust us, you’re not going to check everyday whether a 404 page has been visited. In order to avoid checking it manually, you can define custom alerts.

  There are three possible scenarios when “not found” pages can be fired :

  • internal 404 : one link within your website is pointing to a wrong url on the same website.
  • external 404 : someone from an external website made a link to yours and the link is not correct.
  • direct access 404 : someone access directly to a not found page on your website.

  You can define all those three within Matomo, but in your case, you will only have to focus on the first two only. In fact, you can’t really fix the third scenario. That’s the reason why we’re not focusing on it. It would result in irrelevant alerts.

  Custom alert for internal 404

  An internal 404 is defined from a 404 where the source is an internal web page. As a result, it will look like the following in your report :

  

  In this example, we’re using this specific custom implementation, the title of the page will contain “From = https://www.webassoc.org/”. So set our custom alert accordingly :

  

  Now every time a 404 page will be fired from an internal page, you’ll be notified by email.

  Note that you can also decide to not receive any email and track the evolution of alerts with the History of triggered alerts feature.

  Custom alert for external 404

  External 404 is almost the same setup. The only thing you need to keep in mind is that we want to exclude the 404 where the source is not indicated. As a result, your configuration will look like the following :

  

  Here your regular expression pattern is the following one :

  404/URL = .*From = (?!https://www.webassoc.org)[^\s]+

  as you’ll want to have any referrer coming from a website which is not Matomo and not a direct 404.

   

  You can now be notified every time that a 404 is fired from any link.

  Note that this configuration may slightly differ from website to website. So always double check your tracking code and the way the values are sent to your reports. Also try to trigger those alerts first before validating them.

  How to follow the evolution of your 404 over time ?

  It may be interesting to know how good or how bad you are performing in terms of 404.

  In order to check this information, you can click on the evolution icon near the 404 title :

  

  But you may be interested in accessing this information more regularly without having to create this report each time.

  So, one way to analyse the evolution of your 404 is to create a segment such as :

  

  and to click after that on evolution icon :

  

  As you can see below the number of “not found” pages is quite low in general, but we can also notice that a period received an increase in terms of 404 not found pages on May 27. It may be interesting to investigate it :

  

  You can start from the overview of referrers :

  

  As you can notice here the main source of 404 is coming from direct entries which is the most difficult channel to analyse as we don’t really know where the visitors are coming from.

  How to perform your analysis even faster ?

  As you can see analysing reports in Matomo in order to detect 404 pages is a time-consuming activity. In order to make it faster, you can already create a report about it within the Email reports feature with the following settings :

  • Segment : 404
  • Email schedule : never.
  • Visits summary and Page titles as selected report.

  You will then end up with a saved report listing all the URLs concerned :

  

  You can also have a look at the “Custom reports” premium feature.

  It will provide you with more flexibility. You will then be able to focus on the most important thing : the cause of 404.

  Good luck and happy analytics !