Recherche avancée

Sur d’autres sites (11800)

• 7 Reasons to Migrate from Google Analytics to Matomo Now

  15 mai 2022, par Erin

  The release of Google Analytics 4 (GA4), and the subsequent depreciation of Universal Analytics, has caused a stir amongst webmasters, SEO experts, marketers and the likes.

  Google’s Universal Analytics is the most widely used web analytics platform in the world, but from 1 July 2023, it will no longer process any new data. Google is now pushing users to set up GA4 tracking imminently.

  If you’re like many and wondering if you should upgrade to Google Analytics 4, there are two key reasons why this might be a risk :

  1. GDPR violations : recent rulings have deemed Google Analytics illegal in France and Austria, and it’s likely that this trend will continue across the EU.
  2. Data loss : users switching to Google Analytics 4 can’t migrate their data from Universal Analytics.

  To mitigate these risks, many organisations are looking to switch to a Google Analytics alternative like Matomo. This is an ideal option for organisations that want to take ownership of their data, get compliant with privacy regulations and save themselves the stress of Google deprecating the software they rely on.

  Whilst there are two major reasons to steer clear of Google Analytics 4, there are 7 reasons why migrating to Matomo instead could save your business time, money and peace of mind.

  If you want to avoid the pitfalls of GA4 and are thinking about migrating from Universal Analytics to Matomo, here’s why you should make the switch now.

  1. Keep your historical Universal Analytics data

  Users switching to Google Analytics 4 will be disappointed to find out that GA4 does not accept data imports from Universal Analytics. On top of that, Google also announced that after Universal Analytics stops processing new data (1 July 2023), users will only be able to access this data for “at least six months”. 

  Years of valuable insights will be completely wiped and organisations will not be able to report on year over year results.

  Fortunately, any organisation using Universal Analytics can import this data into Matomo using our Google Analytics Importer plugin. So you can reduce business disruptions and retain years of valuable web analytics data when you switch to Matomo.

  Our comprehensive migration documentation features a handy video, written guides and FAQs to ensure a smooth migration process.

  2. Ease of use

  Web analytics is complicated enough without having to navigate confusing platform user interfaces (UIs). One of GA4’s biggest drawbacks is the “awful and unusable” interface which has received an overwhelming amount of negative backlash online. 

  Matomo’s intuitive UI contains many of the familiar features that made Universal Analytics so well-liked. You’ll find the same popular features like Visitors, Behaviour, and Acquisition to name a few.

  

  User Flow in Matomo

  When you switch to Matomo you can get up to speed quickly and spend more time focusing on high-value tasks, rather than learning about everything new in GA4.

  3. 100% accurate unsampled data

  GA4 implements data sampling and machine learning to fill gaps. Often what you are basing critical business decisions on is actually an estimate of activity. 

  Matomo does not use data sampling, so this guarantees you will always see the full picture.

  “My primary reason to use Matomo is to get the unsampled data, [...] if your website gets lots of traffic and you can’t afford an enterprise level tool like GA premium [GA360] then Matomo is your best choice.”

  With Matomo you can be confident your data-driven decisions are being made with real data.

  4. Privacy by design

  Built-in privacy has always been at the core of Matomo. One key method we use to achieve this, is by giving you 100% data ownership of your web analytics data. You don’t ever have to worry about the data landing in the wrong hands or being used in unethical ways – like unsolicited advertising. 

  On the contrary, Google Analytics is regularly under fire for controversial uses of data. While Google has made changes to make GA4 more privacy-focused, it’s all just smoke and mirrors. The data collected from Google Analytics accounts is used by Google to create digital profiles on internet users, which is then used for advertising. 

  Consumers are becoming increasingly concerned about how businesses are using their data. Businesses that develop privacy strategies, utilise privacy-focused tools will gain a competitive advantage and a loyal customer-base. 

  Prioritise the protection of your user data by switching to a privacy-by-design analytics solution.

  5. Compliance with global privacy laws

  To date, Google Analytics has been deemed illegal to use in France and Austria due to data transfers to the US. Upgrading to GA4 doesn’t make this problem go away either since data is still transferred to the US. 

  Matomo is easily configured to follow even the strictest of privacy laws like GDPR, HIPAA, CCPA, LGPD and PECR. Here’s how :

  • Matomo’s opt-out mechanism lets users opt-out of web analytics tracking
  • You can configure analytics for data retention of raw data and aggregated reports
  • Users can anonymise IP addresses as well as implement other data anonymisation techniques
  • Matomo can respect DoNotTrack setting
  • Users can set up Matomo so it doesn’t process any personal data or PII (personally identifiable information)
  • It’s easy to set shorter expiration dates for tracking cookies
  • Matomo allows you to disable Visits Log and Visitor Profile
  • Users aren’t tracked across websites unless specifically enabled

  Matomo can also be used without cookie consent banners (unlike with Google Analytics, which will always need user consent to track). Matomo has been approved by the French Data Protection Authority (CNIL) as one of the select few web analytics tools that can be used to collect data without tracking consent.

  Every year more countries are drafting legislation that mirrors the European Union’s GDPR (like the Brazilian LGPD). Matomo is designed to stay data-privacy law compliant, and always will be.

  Stay on top of global privacy laws and reduce the time you spend on compliance by switching to a privacy-compliant solution. 

  6. All-in-one web analytics

  Matomo gives you easy access to Heatmaps, Session Recordings, A/B testing, Funnels analytics, and more right out of the box. This means that digital marketing, UX and procurement teams won’t need to set up and manage multiple tools for behavioural analytics – it’s all in one place.

  Learn more about your audience, save money and reduce complexity by switching to an all-in-one analytics solution.

  Check out Matomo’s extensive product features.

  

  Page Scroll Depth in Matomo

  7. Tag Manager built-in

  Unlike GA4, the Matomo Tag Manager comes built-in for an efficient and consistent user experience. Matomo Tag Manager offers a pain-free solution for embedding tracking codes on your website without needing help from a web developer or someone with technical knowledge.

  Help your Marketing team track more website actions and give time back to your web developer by switching to Matomo Tag Manager.

  Final Thoughts

  Google Analytics is free to use, but the surrounding legal issues with the platform and implications of switching to GA4 will make migrating a tough choice for many businesses. 

  Now is the chance for organisations to step away from the advertising tech giant, take ownership of web analytics data and get compliant. Switch to the leading Google Analytics alternative and see why over 1 million websites choose Matomo for their web analytics.

  Ready to get started with your own Google Analytics to Matomo migration ? Try Matomo free for 21 days now – no credit card required. 

  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

  

• Manim Animation Rendering Fails on Google Cloud Run : Segment Combination Issues [closed]

  28 juin, par Ahaskar Kashyap

  Problem Summary

  


  I'm running a Manim animation server on Google Cloud Run that successfully creates video segments but fails during the FFmpeg combination step. The behavior is inconsistent based on the number of segments created.

  


  Environment

  


  

  • Platform : Google Cloud Run (8GB RAM, 4 CPU)

  


  • Container : Debian 12 (bookworm) with Python 3.9.23

  


  • FFmpeg : 5.1.6 (with h264 support enabled)

  


  • Manim : Latest version with -ql (480p15) quality setting

  


  • Timeout : 240 seconds

  


  


  Observed Behavior

  


  




  


  


  


  


  


  


  



  


  


  


  


  


  


  


  


  


  


  


  


  Animation Complexity	Segments Created	Final Video	Status
  Simple (2 segments)	✅ Success	✅ Created (7,681 bytes)	❌ Reports "failed"
  Complex (8+ segments)	✅ Success	❌ Not created	❌ Actually fails

  


  Code Structure

  


  # Manim command used
manim_cmd = [
    'manim', python_file, scene_class,
    '--media_dir', output_dir,
    '-ql',  # Low quality (480p15)
    '--disable_caching',
    '--output_file', f"{output_filename}.mp4",
    '--verbosity', 'ERROR',
    '--progress_bar', 'none',
    '--write_to_movie'
]


  


  Specific Issues

  


  Issue 1 : False Negatives (Simple Animations)

  


  

  • What happens : Manim creates 2 segments successfully, FFmpeg combines them into final video

  


  • Problem : Final video exists and is playable, but process reports "Manim failed (code 1)"

  


  • Evidence : Can download the "failed" video via /videos/filename.mp4 and it plays correctly

  


  


  Issue 2 : Real Failures (Complex Animations)

  


  

  • What happens : Manim creates 8+ segments successfully

  


  • Problem : FFmpeg combination step genuinely fails, no final video created

  


  • Error : Process exits with code 1, only partial segments remain

  


  


  Key Questions

  


  

  1. Why does FFmpeg combination work for 2 segments but fail for 8+ segments ?

  


  2. Why does the same code work locally but fail on Cloud Run ?

  


  3. Is this a Cloud Run container limitation, FFmpeg configuration issue, or Manim-specific problem ?

  


  4. How can I debug FFmpeg combination failures in a containerized environment ?

  


  


  File Structure (When Working)

  


  /app/manim_animations/
└── animation_name/
    └── videos/
        └── animation_name_1234/
            └── 480p15/
                ├── partial_movie_files/
                │   └── SceneClass/
                │       ├── uncached_00000.mp4
                │       └── uncached_00001.mp4
                └── final_animation.mp4  # This gets created for 2 segments


  


  Error Output

  


  🔒 ISOLATED: Manim return code: 1
Manim failed (code 1): [stderr contains FFmpeg errors]


  


  Has anyone encountered similar issues with Manim + FFmpeg on Cloud Run or other containerized environments ? Any insights into why segment count affects combination success would be greatly appreciated.

  


  Investigation Results

  


  What Works :

  


  

  • ✅ Local development (identical code works perfectly)

  


  • ✅ FFmpeg installation (ffmpeg -version works, h264 encoders available)

  


  • ✅ Segment creation (all uncached_*.mp4 files created with correct sizes)

  


  • ✅ Simple animations after container restart

  


  


  What Doesn't Work :

  


  

  • ❌ Segment combination for 8+ segments

  


  • ❌ Status detection for 2-segment animations

  


  • ❌ Animations after multiple renders (resource accumulation ?)

  


  


  Theories Tested :

  


  

  1. Resource constraints : Upgraded to 16GB/8CPU - made things worse

  


  2. FFmpeg version : Upgraded 5.1.6→7.x - broke basic functionality

  


  3. File accumulation : Container restart helps temporarily

  


  4. Path detection : Isolation script may look in wrong directories

  


  


• Red5 live stream - huge delay on localhost

  23 janvier 2013, par user1958067

  I m running Red5 1.0.0 RC1, with JW Player and ffmpeg on Linux Mint14

  There is a huge delay while streaming, even when everythings happening on my machine/localhost.

  I do following steps :

  1. FFmpeg : ffmpeg -i 'http://localhost:port' rtmp://localhost/oflaDemo/live.flv

  2. Red5 : TCPnoDelay ist set to true.

  3. JW Player : Bufferlength is set to 0. Also tried 2 and 3.

   :

      <code class="echappe-js">&lt;script type=&amp;#39;text/javascript&amp;#39;&gt;<br />
  
       jwplayer(&amp;#39;mediaspace&amp;#39;).setup({<br />
  
      &amp;#39;flashplayer&amp;#39;: &amp;#39;player.swf&amp;#39;,<br />
  
      &amp;#39;file&amp;#39;: &amp;#39;live&amp;#39;,<br />
  
      &amp;#39;type&amp;#39;: &amp;#39;rtmp&amp;#39;,<br />
  
      &amp;#39;streamer&amp;#39;: &amp;#39;rtmp://localhost/oflaDemo&amp;#39;,<br />
  
      &amp;#39;controlbar&amp;#39;: &amp;#39;none&amp;#39;,<br />
  
      &amp;#39;autostart&amp;#39;: &amp;#39;true&amp;#39;,<br />
  
      &amp;#39;bufferlength&amp;#39;: &amp;#39;3&amp;#39;,<br />
  
      &amp;#39;width&amp;#39;: &amp;#39;640&amp;#39;,<br />
  
      &amp;#39;height&amp;#39;: &amp;#39;380&amp;#39;<br />
  
    });<br />
  
  &lt;/script&gt;
  
  

  The delay is something between 7-10 seconds !
  This all is happening on and from localhost, so bandwith shouldnt be the issue.