Sur d’autres sites (11279)

• Exceeded GA’s 10M hits data limit, now what ?

  21 juin 2019, par Joselyn Khor
  Exceeded GA’s 10M hits data limit, now what ? Matomo has the answers

  “Your data volume (1XXM hits) exceeds the limit of 10M hits per month as outlined in our Terms of Service. If you continue to exceed the limit, we will stop processing new data on XXX 21, 2019. Learn more about possible solutions.”

  Yikes. Alarm bells were ringing when a Google Analytics free user came to us faced with this notice. Let’s call him ‘Mark’. Mark had reached the limits on the data he could collect through Google Analytics and was shocked by the limited options available to fix the problem, without blowing the budget. The thoughts racing through his head were :

  • “What happens to all my data ?”
  • “What if Google starts charging USD150K now ?”

  Then he came across Matomo and decided to get in touch with our support team …

  “Can you fix this issue ?” he asked us.

  “Absolutely !” we said.

  We’ll get back to helping Mark in a minute. For now let’s go over why this was such a dilemma for him.

  In order to resolve this data limits issue, one of the solutions was for him to upgrade to Google Analytics 360, which meant shelling out USD150,000 per year for their 1 billion hits per month option. Going from free to USD150,000 was too much of a stretch for a growing company.

  “Your data volume (1XXM hits) exceeds the limit of 10M hits per month …”, what did this message mean ?

  With the free version, Mark could collect up to 10 million “hits” per month, per account. Going over meant Google Analytics could stop collecting any more data for free as outlined in their Terms.

  Google Analytics’ Terms of Service (2018, sec. 2) states, “Subject to Section 15, the Service is provided without charge to You for up to 10 million Hits per month per account.”[1]

  In general, what’s a "hit" ?

  Data being sent to Google Analytics. It can be a transaction, event, social interaction or pageview - these all produce what Google calls a “hit”.

  

  And their Analytics Help Data Limits (n.d.) support page makes clear that : “If a property sends more hits per month to Analytics than allowed by the Analytics Terms of Service, there is no assurance that the excess hits will be processed. If the property’s hit volume exceeds this limit, a warning may be displayed in the user interface and you may be prevented from accessing reports.”[2]

  

  Possible solutions

  So the possible solutions given by Google Analytics’ Data Limits support page were (also shown in image below) :

  • To pay USD150K to upgrade to Google Analytics 360
  • To send fewer hits by setting up sampling
  • Or choose the slightly less relevant option to upgrade mobile app tracking to Google Analytics for Firebase.

  Without the means to pay, the free version was fast becoming inaccessible for Mark as he was facing a future where he risked no longer having access to up-to-date data used in his business’ reporting.

  Mark was facing a problem that potentially didn’t have a cost-effective solution.

  

  So what can you really do about it ?

  This is where we can help provide some assistance. If you’re reading this article, we’ll assume you can relate to Mark and share with you the advice on options we gave him.

  Options :

  One option posed by Google is for you to send fewer hits by auditing your data collection processes

  If you really don’t have the budget, you’ll need to reassess your data collection priorities and go over your strategies to see what is necessary to track, and what isn’t.

  • Make sure you know what you’re tracking and why. Look at what websites are being tracked by Google and into what properties.
  • Go through what data you’re tracking and decide what is or isn’t of value.
  • Set up data sampling, this however, will lead to inaccurate data.

  From here you can start to course correct. If you’ve found data you’re not using for analysis, get rid of these events/pageviews in your Google Analytics.

  But the limitations here are that eventually, you’re going to run out of irrelevant metrics and everything you’re tracking will be essential. So you’ll hit another brick wall and return to the same situation.

  Option 2 – Ignore and continue using the free version of Google Analytics

  With this option, you’ll have to bear the business risks involved by basing decisions off of analytics reports that may or may not be updated. In this case, you may still get contacted about exceeding the limits. As the free service is provided for only up to 10 million hits, once you’ve gone over them, you’re violating what’s stipulated in the Terms of Service. 

  There’s also the warning that “… you may be prevented from accessing reports” (Data limits, n.d.). So while we may not know for certain what Google Analytics will do, in this case it may be better to be safe rather than sorry by acting quickly to resolve it. 

  Option 3 –The Matomo solution. Upgrade to a web analytics platform that can handle your demanding data requirements

  Save money while continuing to gain valuable insights by moving over to Matomo Analytics (recommended)

  This is where you can save up to USD130,000 a year. As well as that, the transition from Google Analytics to the Matomo Cloud is a seamless experience as setup and maintenance is taken care of by our experts.

  For example, you can get up to 15M pageviews for USD1,612.50/month (or USD19,350/year) on the Essentials plan.

  Or even 25M pageviews for USD2400/month (or USD24000/year) on the Business plan – which offers additional web analytics and conversion optimization resources.

  Matomo Cloud is a great option if you’re looking for a secure, cost-effective and powerful analytics solution. You also get what Google Analytics could never offer you : full control and ownership of your own data and privacy. 

  No need to worry about losing your Google Analytics data because …

  Now you can import your historic Google Analytics data directly into your Matomo with the Google Analytics Importer tool. Simply follow the step-by-step guide to get started for free.

  Along with savings you can get :

  • A solution for the data limits issue forever. You choose the right plan to suit your data needs and adapt as you continue growing
  • 100% accurate data (no data sampling)
  • 100% data ownership of all your information without signing away your data to a third party
  • Powerful web analytics and conversion optimization features
  • Matomo Tag Manager
  • Easy setup
  • Support from Matomo’s specialists

  Learn more about Matomo Cloud pricing.

  

  Or go for Matomo On-Premise

  If you have the in-house infrastructure to support self-hosting Matomo on your own servers then there’s also the option of Matomo On-Premise. Here you’ll get full security knowing the data is on your own servers. 

  Setup will also require technical knowledge. There will also be costs associated with acquiring your own servers, and keeping up with regular maintenance and updates. With On-Premise you get maximum flexibility, with no data limits whatsoever. But if you’re coming over from Google Analytics and don’t have the infrastructure and team to host On-Premise, the Matomo Cloud could be right for you.

  Learn more about Matomo On-Premise.

  Where do you go from here ?

  Getting 10 millions hits per month is no small feat, it’s actually pretty fantastic. But if it means having to shell out USD150,000 just to be able to continue with Google Analytics, we feel your problem could be fixed with Matomo Cloud. You could then put the rest of the money you save to better use.

  If you choose Matomo, you now have the option to : 

  • Raise your data limits for a fraction of Google Analytics 360’s price
  • Get a comprehensive range of analytics features for the most impactful insights to ensure your website continues excelling
  • Get data that’s not sampled – meaning 100% accuracy in your reports
  • Migrate your data easily with the help of Matomo’s support team

  We’ll have you covered. 

  By sharing with you the options and advice we gave to Mark, we hope you’ll be able to find a solution that makes your life easier and solves the issue of data restrictions forever.

  The team at Matomo is here to help you every step of the way to ensure a stress-free transition from Google Analytics if that is what works best for you.

  For next steps, why not check out our pricing page to see what could suit your needs !

  References :

  [1] Terms of Service. (2018, July 24). In Google Analytics Terms of Service. Retrieved June 12, 2019, from https://www.google.com/analytics/terms/us.html

  [2] Data limits. (n.d.). In Analytics Help Data limits. Retrieved June 12, 2019, from https://support.google.com/analytics/answer/1070983?hl=en

• How to fix : Frame rate differs from source after encoding certain mp4 videos to wmv

  25 juin 2019, par hpenhp

  I’m having trouble with a usually working ffmpeg script for encoding mp4 and more to wmv. The goal is to keep it like the original, except for the resolution (smaller) and the format (wmv).

  When it usually works for a lot of videos, on some of them it doesn’t... and i would like to understand and avoid that.

  I tried several things, forcing the framerate for the output, using -vsync 2 option, -vsync 0 also.. noone of that fixed the issue.

  An other thing, worth adding, is that the fps value from media info is good (24 fps) on the output like the input, but through the M$ windows explorer, it says 30 frames per sec, and when you play the video you see that the text that was matching the input doesn’t match the output any more (because of the fps mismatching).

  Below the script i use :

  ffmpeg -threads auto -i input.mp4 -s 480*320 -b:v 1000k -vcodec msmpeg4 -acodec wmav2 -f asf output.wmv

  Here is the ffmpeg log :

  ffmpeg version 3.4.1-1~16.04.york0 Copyright (c) 2000-2017 the FFmpeg developers
  
    built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.5) 20160609
  
    configuration: --prefix=/usr --extra-version='1~16.04.york0' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
  
    WARNING: library configuration mismatch
  
    avcodec     configuration: --prefix=/usr --extra-version='1~16.04.york0' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared --enable-version3 --disable-doc --disable-programs --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libtesseract --enable-libvo_amrwbenc
  
    libavutil      55. 78.100 / 55. 78.100
  
    libavcodec     57.107.100 / 57.107.100
  
    libavformat    57. 83.100 / 57. 83.100
  
    libavdevice    57. 10.100 / 57. 10.100
  
    libavfilter     6.107.100 /  6.107.100
  
    libavresample   3.  7.  0 /  3.  7.  0
  
    libswscale      4.  8.100 /  4.  8.100
  
    libswresample   2.  9.100 /  2.  9.100
  
    libpostproc    54.  7.100 / 54.  7.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from './test_2k-24__hq_960x540.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41isomavc1
  
      creation_time   : 2019-05-27T14:37:50.000000Z
  
    Duration: 01:28:52.80, start: 0.000000, bitrate: 1232 kb/s
  
      Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, smpte170m), 960x540, 1091 kb/s, 24 fps, 24 tbr, 24 tbn, 48 tbc (default)
  
      Metadata:
  
        creation_time   : 2019-05-27T14:37:50.000000Z
  
        handler_name    : L-SMASH Video Handler
  
        encoder         : AVC Coding
  
      Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 137 kb/s (default)
  
      Metadata:
  
        creation_time   : 2019-05-27T14:37:50.000000Z
  
        handler_name    : L-SMASH Audio Handler
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> msmpeg4v3 (msmpeg4))
  
    Stream #0:1 -> #0:1 (aac (native) -> wmav2 (native))
  
  Press [q] to stop, [?] for help
  
  Output #0, asf, to '/nas/copiedetravail/test_2k-24__hq_960x540.mp4.wmv':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: mp42mp41isomavc1
  
      WM/EncodingSettings: Lavf57.83.100
  
      Stream #0:0(und): Video: msmpeg4v3 (msmpeg4) (MP43 / 0x3334504D), yuv420p(progressive), 480x320, q=2-31, 1000 kb/s, 24 fps, 1k tbn, 24 tbc (default)
  
      Metadata:
  
        creation_time   : 2019-05-27T14:37:50.000000Z
  
        handler_name    : L-SMASH Video Handler
  
        encoder         : Lavc57.107.100 msmpeg4
  
      Side data:
  
        cpb: bitrate max/min/avg: 0/0/1000000 buffer size: 0 vbv_delay: -1
  
      Stream #0:1(und): Audio: wmav2 (a[1][0][0] / 0x0161), 48000 Hz, stereo, fltp, 128 kb/s (default)
  
      Metadata:
  
        creation_time   : 2019-05-27T14:37:50.000000Z
  
        handler_name    : L-SMASH Audio Handler
  
        encoder         : Lavc57.107.100 wmav2
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
      Last message repeated 31 times
  
  frame=  228 fps=0.0 q=2.0 size=     291kB time=00:00:09.45 bitrate= 252.4kbits/s speed=18.9x    
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
      Last message repeated 1 times
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
      Last message repeated 1 times
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
      Last message repeated 1 times
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
      Last message repeated 5 times
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
      Last message repeated 2 times
  
  frame=  449 fps=449 q=2.0 size=     663kB time=00:00:18.98 bitrate= 286.2kbits/s speed=  19x    
  
  frame=  629 fps=418 q=1.6 size=    1307kB time=00:00:26.16 bitrate= 409.2kbits/s speed=17.4x    
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
      Last message repeated 30 times
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
      Last message repeated 7 times
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
      Last message repeated 2 times
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
      Last message repeated 34 times
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
      Last message repeated 1 times
  
  frame=  821 fps=410 q=2.0 size=    1960kB time=00:00:34.26 bitrate= 468.7kbits/s speed=17.1x    
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
      Last message repeated 71 times
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 2 dct coefficients to -127..127
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
      Last message repeated 82 times
  
  frame= 1026 fps=409 q=2.0 size=    2695kB time=00:00:42.96 bitrate= 513.8kbits/s speed=17.1x    
  
  [msmpeg4 @ 0x5648e407cb60] warning, clipping 1 dct coefficients to -127..127
  
      Last message repeated 102 times
  
  frame= 1202 fps=400 q=1.6 size=    3754kB time=00:00:50.13 bitrate= 613.4kbits/s speed=16.7x  
  
  ......
  
  frame=127987 fps=301 q=2.0 Lsize=  753842kB time=01:28:52.77 bitrate=1158.0kbits/s speed=12.6x    
  
  video:650704kB audio:83244kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 2.710554%

  EDIT :
  My workaround was to encode to MPEG, doing this, i’m able to read my file and the frame rate is same as source. If someone knows why it couldn’t keep the original framerate in wmv, i’m still interested to know.

• Anomalie #4351 : Login par email (cookie spip_admin)

  17 juin 2019, par RastaPopoulos ♥

  Si ça ne casse rien, +1000 :)