Recherche avancée

Sur d’autres sites (7242)

• 10 Key Google Analytics Limitations You Should Be Aware Of

  9 mai 2022, par Erin

  Google Analytics (GA) is the biggest player in the web analytics space. But is it as “universal” as its brand name suggests ?
  

  Over the years users have pointed out a number of major Google Analytics limitations. Many of these are even more visible in Google Analytics 4. 

  Introduced in 2020, Google Analytics 4 (GA4) has been sceptically received. As the sunset date of 1st, July 2023 for the current version, Google Universal Analytics (UA), approaches, the dismay grows stronger.

  To the point where people are pleading with others to intervene : 

  

  Main limitations of Google Analytics

  Google Analytics 4 is advertised as a more privacy-centred, comprehensive and “intelligent” web analytics platform. 

  According to Google, the newest version touts : 

  • Machine learning at its core provides better segmentation and fast-track access to granular insights 
  • Privacy-by-design controls, addressing restrictions on cookies and new regulatory demands 
  • More complete understanding of customer journeys across channels and devices 

  Some of these claims hold true. Others crumble upon a deeper investigation. Newly advertised Google Analytics capabilities such as ‘custom events’, ‘predictive insights’ and ‘privacy consent mode’ only have marginal improvements. 

  Complex setup, poor UI and lack of support with migration also leave many other users frustrated with GA4. 

  

  Let’s unpack all the current (and legacy) limitations of Google Analytics you should account for. 

  1. No Historical Data Imports 

  Google rushed users to migrate from Universal Analytics to Google Analytics 4. But they overlooked one important precondition — backwards compatibility. 

  You have no way to import data from Google Universal Analytics to Google Analytics 4. 

  Historical records are essential for analysing growth trends and creating benchmarks for new marketing campaigns. Effectively, you are cut short from past insights — and forced to start strategising from scratch. 

  At present, Google offers two feeble solutions : 

  • Run data collection in parallel and have separate reporting for GA4 and UA until the latter is shut down. Then your UA records are gone. 
  • For Ecommerce data, manually duplicate events from UA at a new GA4 property while trying to figure out the new event names and parameters. 

  Google’s new data collection model is the reason for migration difficulties. 

  In Google Analytics 4, all analytics hits types — page hits, social hits, app/screen view, etc. — are recorded as events. Respectively, the “‘event’ parameter in GA4 is different from one in Google Universal Analytics as the company explains : 

  

  This change makes migration tedious — and Google offers little assistance with proper events and custom dimensions set up. 

  2. Data Collection Limits 

  If you’ve wrapped your head around new GA4 events, congrats ! You did a great job, but the hassle isn’t over. 

  You still need to pay attention to new Google Analytics limits on data collection for event parameters and user properties. 

  

  These apply to :

  • Automatically collected events
  • Enhanced measurement events
  • Recommended events 
  • Custom events 

  When it comes to custom events, GA4 also has a limit of 25 custom parameters per event. Even though it seems a lot, it may not be enough for bigger websites. 

  You can get higher limits by upgrading to Google Analytics 360, but the costs are steep. 

  3. Limited GDPR Compliance 

  Google Analytics has a complex history with European GDPR compliance. 

  A 2020 ruling by the Court of Justice of the European Union (CJEU) invalidated the Privacy Shield framework Google leaned upon. This framework allowed the company to regulate EU-US data transfers of sensitive user data. 

  But after this loophole was closed, Google faced a heavy series of privacy-related fines :

  • French data protection authority, CNIL, ruled that  “the transfers to the US of personal data collected through Google Analytics are illegal” — and proceeded to fine Google for a record-setting €150 million at the beginning of 2022. 
  • Austrian regulators also deemed Google in breach of GDPR requirements and also branded the analytics as illegal. 

  Other EU-member states might soon proceed with similar rulings. These, in turn, can directly affect Google Analytics users, whose businesses could face brand damage and regulatory fines for non-compliance. In fact, companies cannot select where the collected analytics data will be stored — on European servers or abroad — nor can they obtain this information from Google.

  Getting a web analytics platform that allows you to keep data on your own servers or select specific Cloud locations is a great alternative. 

  Google also has been lax with its cookie consent policy and doesn’t properly inform consumers about data collection, storage or subsequent usage. Google Analytics 4 addresses this issue to an extent. 

  By default, GA4 relies on first-party cookies, instead of third-party ones — which is a step forward. But the user privacy controls are hard to configure without losing most of the GA4 functionality. Implementing user consent mode to different types of data collection also requires a heavy setup. 

  4. Strong Reliance on Sampled Data 

  To compensate for ditching third-party cookies, GA4 more heavily leans on sampled data and machine learning to fill the gaps in reporting. 

  In GA4 sampling automatically applies when you :

  • Perform advanced analysis such as cohort analysis, exploration, segment overlap or funnel analysis with not enough data 
  • Have over 10,000,000 data rows and generate any type of non-default report 

  Google also notes that data sampling can occur at lower thresholds when you are trying to get granular insights. If there’s not enough data or because Google thinks it’s too complex to retrieve. 

  In their words :

  

  Data sampling adds “guesswork” to your reports, meaning you can’t be 100% sure of data accuracy. The divergence from actual data depends on the size and quality of sampled data. Again, this isn’t something you can control. 

  Unlike Google Analytics 4, Matomo applies no data sampling. Your reports are always accurate and fully representative of actual user behaviours. 

  5. No Proper Data Anonymization 

  Data anonymization allows you to collect basic analytics about users — visits, clicks, page views — but without personally identifiable information (or PII) such as geo-location, assigns tracking ID or other cookie-based data. 

  This reduced your ability to :

  • Remarket 
  • Identify repeating visitors
  • Do advanced conversion attribution 

  But you still get basic data from users who ignored or declined consent to data collection. 

  By default, Google Analytics 4 anonymizes all user IP addresses — an upgrade from UA. However, it still assigned a unique user ID to each user. These count as personal data under GDPR. 

  For comparison, Matomo provides more advanced privacy controls. You can anonymize :

  • Previously tracked raw data 
  • Visitor IP addresses
  • Geo-location information
  • User IDs 

  This can ensure compliance, especially if you operate in a sensitive industry — and delight privacy-mindful users ! 

  6. No Roll-Up Reporting

  Getting a bird’s-eye view of all your data is helpful when you need hotkey access to main sites — global traffic volume, user count or percentage of returning visitors.

  With Roll-Up Reporting, you can see global-performance metrics for multiple localised properties (.co.nz, .co.uk, .com, etc,) in one screen. Then zoom in on specific localised sites when you need to. 

  

  7. Report Processing Latency 

  The average data processing latency is 24-48 hours with Google Analytics. 

  Accounts with over 200,000 daily sessions get data refreshes only once a day. So you won’t be seeing the latest data on core metrics. This can be a bummer during one-day promo events like Black Friday or Cyber Monday when real-time information can prove to be game-changing ! 

  Matomo processes data with lower latency even for high-traffic websites. Currently, we have 6-24 hour latency for cloud deployments. On-premises web analytics can be refreshed even faster — within an hour or instantly, depending on the traffic volumes. 

  8. No Native Conversion Optimisation Features

  Google Analytics users have to use third-party tools to get deeper insights like how people are interacting with your webpage or call-to-action.

  You can use the free Google Optimize tool, but it comes with limits : 

  • No segmentation is available 
  • Only 10 simultaneous running experiments allowed 

  There isn’t a native integration between Google Optimize and Google Analytics 4. Instead, you have to manually link an Optimize Container to an analytics account. Also, you can’t select experiment dimensions in Google Analytics reports.

  What’s more, Google Optimize is a basic CRO tool, best suited for split testing (A/B testing) of copy, visuals, URLs and page layouts. If you want to get more advanced data, you need to pay for extra tools. 

  Matomo comes with a native set of built-in conversion optimization features : 

  • Heatmaps 
  • User session recording 
  • Sales funnel analysis 
  • A/B testing 
  • Form submission analytics 

  

  9. Deprecated Annotations

  Annotations come in handy when you need to provide extra context to other team members. For example, point out unusual traffic spikes or highlight a leak in the sales funnel. 

  This feature was available in Universal Analytics but is now gone in Google Analytics 4. But you can still quickly capture, comment and share knowledge with your team in Matomo. 

  You can add annotations to any graph that shows statistics over time including visitor reports, funnel analysis charts or running A/B tests. 

  10. No White Label Option 

  This might be a minor limitation of Google Analytics, but a tangible one for agency owners. 

  Offering an on-brand, embedded web analytics platform can elevate your customer experience. But white label analytics were never a thing with Google Analytics, unlike Matomo. 

  Wrap Up 

  Google set a high bar for web analytics. But Google Analytics inherent limitations around privacy, reporting and deployment options prompt more users to consider Google Analytics alternatives, like Matomo. 

  With Matomo, you can easily migrate your historical data records and store customer data locally or in a designated cloud location. We operate by a 100% unsampled data principle and provide an array of privacy controls for advanced compliance. 

  Start your 21-day free trial (no credit card required) to see how Matomo compares to Google Analytics ! 

  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 hereby accept the terms and conditions and the data processing agreeement (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

  

• How can I retain 2x pixel density when encoding Retina screen capture with ffmpeg ?

  26 février 2018, par hfossli

  Whenever I use ffmpeg to encode a HiDPI/Retina screen recording, the video plays at 2x the size, so it looks fuzzy, because the pixel density is not retained.

  How can I retain the original pixel density of HiDPI screen recordings with ffmpeg ?

  How to reproduce :

  1. Use QuickTime Player to create a Screen Recording on a Retina Mac.
  2. Play the video you recorded in QuickTime Player using the ⌘1 Actual Size view. Notice that it’s playing 2:1 on your Retina Display, so the video looks sharp. It’s playing in half the space of the actual recorded pixels.

  3. Use ffmpeg to encode the video using a command like this :

     ffmpeg -i haha.mov -c:v libx264 -crf 23 haha-lg.mov

  4. Play the new ffmpeg-compressed video in QuickTime Player using the ⌘1 Actual Size view. Notice that it’s playing 1:1, so the video looks fuzzy.

  To clarify, the video does not look blurry because it was compressed. Rather, it looks blurry because the video is being played twice as big as it should be, at a 1:1 pixel density, instead of the required 2:1 pixel density, presumably because some metadata is being discarded when encoding.

  For the record, VLC plays both videos too big (blurry). So being able to play HiDPI videos seems to be a feature of QuickTime Player.

  Here is the detailed information ffmpeg shows for the original screen recording :

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'haha.mov':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 0
  
      compatible_brands: qt  
  
      creation_time   : 2018-02-26T16:46:00.000000Z
  
      com.apple.quicktime.make: Apple
  
      com.apple.quicktime.model: iMac18,3
  
      com.apple.quicktime.software: Mac OS X 10.13.3 (17D102)
  
      com.apple.quicktime.creationdate: 2018-02-26T10:45:50-0600
  
    Duration: 00:00:04.35, start: 0.000000, bitrate: 10947 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1396x928 [SAR 1:1 DAR 349:232], 10701 kb/s, 60 fps, 60 tbr, 6k tbn, 12k tbc (default)
  
      Metadata:
  
        creation_time   : 2018-02-26T16:46:00.000000Z
  
        handler_name    : Core Media Data Handler
  
        encoder         : H.264

  And here is the information for the ffmpeg-compressed version :

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'haha-lg.mov':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 512
  
      compatible_brands: qt  
  
      encoder         : Lavf57.83.100
  
    Duration: 00:00:04.35, start: 0.000000, bitrate: 1923 kb/s
  
      Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1396x928 [SAR 1:1 DAR 349:232], 1783 kb/s, 60 fps, 60 tbr, 15360 tbn, 120 tbc (default)
  
      Metadata:
  
        handler_name    : DataHandler
  
        encoder         : Lavc57.107.100 libx264

• How can I retain 2x pixel density when encoding Retina screen capture with ffmpeg ?

  26 février 2018, par hfossli

  Whenever I use ffmpeg to encode a HiDPI/Retina screen recording, the video plays at 2x the size, so it looks fuzzy, because the pixel density is not retained.

  How can I retain the original pixel density of HiDPI screen recordings with ffmpeg ?

  How to reproduce :

  1. Use QuickTime Player to create a Screen Recording on a Retina Mac.
  2. Play the video you recorded in QuickTime Player using the ⌘1 Actual Size view. Notice that it’s playing 2:1 on your Retina Display, so the video looks sharp. It’s playing in half the space of the actual recorded pixels.

  3. Use ffmpeg to encode the video using a command like this :

     ffmpeg -i haha.mov -c:v libx264 -crf 23 haha-lg.mov

  4. Play the new ffmpeg-compressed video in QuickTime Player using the ⌘1 Actual Size view. Notice that it’s playing 1:1, so the video looks fuzzy.

  To clarify, the video does not look blurry because it was compressed. Rather, it looks blurry because the video is being played twice as big as it should be, at a 1:1 pixel density, instead of the required 2:1 pixel density, presumably because some metadata is being discarded when encoding.

  For the record, VLC plays both videos too big (blurry). So being able to play HiDPI videos seems to be a feature of QuickTime Player.

  Here is the detailed information ffmpeg shows for the original screen recording :

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'haha.mov':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 0
  
      compatible_brands: qt  
  
      creation_time   : 2018-02-26T16:46:00.000000Z
  
      com.apple.quicktime.make: Apple
  
      com.apple.quicktime.model: iMac18,3
  
      com.apple.quicktime.software: Mac OS X 10.13.3 (17D102)
  
      com.apple.quicktime.creationdate: 2018-02-26T10:45:50-0600
  
    Duration: 00:00:04.35, start: 0.000000, bitrate: 10947 kb/s
  
      Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1396x928 [SAR 1:1 DAR 349:232], 10701 kb/s, 60 fps, 60 tbr, 6k tbn, 12k tbc (default)
  
      Metadata:
  
        creation_time   : 2018-02-26T16:46:00.000000Z
  
        handler_name    : Core Media Data Handler
  
        encoder         : H.264

  And here is the information for the ffmpeg-compressed version :

  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'haha-lg.mov':
  
    Metadata:
  
      major_brand     : qt  
  
      minor_version   : 512
  
      compatible_brands: qt  
  
      encoder         : Lavf57.83.100
  
    Duration: 00:00:04.35, start: 0.000000, bitrate: 1923 kb/s
  
      Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1396x928 [SAR 1:1 DAR 349:232], 1783 kb/s, 60 fps, 60 tbr, 15360 tbn, 120 tbc (default)
  
      Metadata:
  
        handler_name    : DataHandler
  
        encoder         : Lavc57.107.100 libx264