Recherche avancée

Sur d’autres sites (4741)

• Unknown V4L2 pixel format equivalent for yuvj420p

  23 mars 2020, par c10ud

  I am trying to pipe a mp4 video located in Videos/video.mp4 to a virtual webcam device located at /dev/video0.

  I tried running :
  ffmpeg -re -i Videos/video.mp4 -map 0:v -f v4l2 /dev/video0
  and I keep getting the following error :

  [video4linux2,v4l2 @ 0x5580cf270100] Unknown V4L2 pixel format equivalent for yuvj420p
  
  Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument
  
  Error initializing output stream 0:0 -- 
  
  Conversion failed!

  Full log :

  ffmpeg version 4.2.2-1+b1 Copyright (c) 2000-2019 the FFmpeg developers
  
    built with gcc 9 (Debian 9.2.1-28)
  
    configuration: --prefix=/usr --extra-version=1+b1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
  
    libavutil      56. 31.100 / 56. 31.100
  
    libavcodec     58. 54.100 / 58. 54.100
  
    libavformat    58. 29.100 / 58. 29.100
  
    libavdevice    58.  8.100 / 58.  8.100
  
    libavfilter     7. 57.100 /  7. 57.100
  
    libavresample   4.  0.  0 /  4.  0.  0
  
    libswscale      5.  5.100 /  5.  5.100
  
    libswresample   3.  5.100 /  3.  5.100
  
    libpostproc    55.  5.100 / 55.  5.100
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Videos/video.mp4':
  
    Metadata:
  
      major_brand     : mp42
  
      minor_version   : 0
  
      compatible_brands: isommp42
  
      creation_time   : 2020-03-23T04:24:01.000000Z
  
      com.android.version: 8.1.0
  
    Duration: 00:01:00.14, start: 0.000000, bitrate: 20048 kb/s
  
      Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuvj420p(pc, smpte170m), 1920x1080, 19898 kb/s, SAR 1:1 DAR 16:9, 29.43 fps, 29.58 tbr, 90k tbn, 180k tbc (default)
  
      Metadata:
  
        rotate          : 270
  
        creation_time   : 2020-03-23T04:24:01.000000Z
  
        handler_name    : VideoHandle
  
      Side data:
  
        displaymatrix: rotation of 90.00 degrees
  
      Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 96 kb/s (default)
  
      Metadata:
  
        creation_time   : 2020-03-23T04:24:01.000000Z
  
        handler_name    : SoundHandle
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (h264 (native) -> rawvideo (native))
  
  Press [q] to stop, [?] for help
  
  [video4linux2,v4l2 @ 0x5580cf270100] Unknown V4L2 pixel format equivalent for yuvj420p
  
  Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument
  
  Error initializing output stream 0:0 -- 
  
  Conversion failed!

  The desired result is that the mp4 video is seen by apps that try to view the webcam. I am running this on a desktop without a webcam or video interface, which is why I am using /dev/video0

• How to resize dimensions of video through ffmpeg-python ?

  25 janvier, par kunambi

  I'm trying to resize a video file which a user has uploaded to Django, by using ffmpeg-python. The documentation isn't very easy to understand, so I've tried to cobble this together from various sources.

  


  This method is run in a celery container, in order to not slow the experience for the user. The problem I'm facing is that I can't seem to resize the video file. I've tried two different approaches :

  


  from django.db import models
from io import BytesIO
from myapp.models import MediaModel


def resize_video(mypk: str) -> None:
    instance = MediaModel.objects.get(pk=mypk)
    media_instance: models.FileField = instance.media
    media_output = "test.mp4"
    buffer = BytesIO()

    for chunk in media_instance.chunks():
        buffer.write(chunk)

    stream_video = ffmpeg.input("pipe:").video.filter("scale", 720, -1)  # resize to 720px width
    stream_audio = ffmpeg.input("pipe:").audio
    process = (
        ffmpeg.output(stream_video, stream_audio, media_output, acodec="aac")
        .overwrite_output()
        .run_async(pipe_stdin=True, quiet=True)
    )
    buffer.seek(0)
    process_out, process_err = process.communicate(input=buffer.getbuffer())
    # (pdb) process_out
    # b''

    # attempting to use `.concat` instead
    process2 = (
        ffmpeg.concat(stream_video, stream_audio, v=1, a=1)
        .output(media_output)
        .overwrite_output()
        .run_async(pipe_stdin=True, quiet=True)
    )
    buffer.seek(0)
    process2_out, process2_err = process2.communicate(input=buffer.getbuffer())
    # (pdb) process2_out
    # b''


  


  As we can see, no matter which approach chosen, the output is an empty binary. The process_err and process2_err both generate the following message :

  


  ffmpeg version N-111491-g31979127f8-20230717 Copyright (c) 2000-2023 the
FFmpeg developers
  built with gcc 13.1.0 (crosstool-NG 1.25.0.196_227d99d)
  configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static
--pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64
--target-os=mingw32 --enable-gpl --enable-version3 --disable-debug
--disable-w32threads --enable-pthreads --enable-iconv --enable-libxml2
--enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp
--enable-lzma --enable-fontconfig --enable-libvorbis --enable-opencl
--disable-libpulse --enable-libvmaf --disable-libxcb --disable-xlib
--enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth
--enable-chromaprint --enable-libdav1d --enable-libdavs2
--disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r
--enable-libgme --enable-libkvazaar --enable-libass --enable-libbluray
--enable-libjxl --enable-libmp3lame --enable-libopus --enable-librist
--enable-libssh --enable-libtheora --enable-libvpx --enable-libwebp
--enable-lv2 --enable-libvpl --enable-openal --enable-libopencore-amrnb
--enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg
--enable-libopenmpt --enable-librav1e --enable-librubberband
--enable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt
--enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --disable-libdrm
--disable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc
--enable-libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2
--enable-libxvid --enable-libzimg --enable-libzvbi
--extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags=
--extra-ldflags=-pthread --extra-ldexeflags= --extra-libs=-lgomp
--extra-version=20230717
  libavutil      58. 14.100 / 58. 14.100
  libavcodec     60. 22.100 / 60. 22.100
  libavformat    60. 10.100 / 60. 10.100
  libavdevice    60.  2.101 / 60.  2.101
  libavfilter     9.  8.102 /  9.  8.102
  libswscale      7.  3.100 /  7.  3.100
  libswresample   4. 11.100 /  4. 11.100
  libpostproc    57.  2.100 / 57.  2.100
 "Input #0, mov,mp4,m4a,3gp,3g2,mj2, frompipe:':\r\n"
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: mp42mp41
    creation_time   : 2020-11-10T15:01:09.000000Z
  Duration: 00:00:04.16, start: 0.000000, bitrate: N/A
  Stream #0:0[0x1](eng): Video: h264 (Main) (avc1 / 0x31637661),
yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 2649 kb/s, 25 fps, 25
tbr, 25k tbn (default)
    Metadata:
      creation_time   : 2020-11-10T15:01:09.000000Z
      handler_name    : ?Mainconcept Video Media Handler
      vendor_id       : [0][0][0][0]
      encoder         : AVC Coding
  Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz,
stereo, fltp, 317 kb/s (default)
    Metadata:
      creation_time   : 2020-11-10T15:01:09.000000Z
      handler_name    : #Mainconcept MP4 Sound Media Handler
      vendor_id       : [0][0][0][0]
Stream mapping:
  Stream #0:0 (h264) -> scale:default (graph 0)
  scale:default (graph 0) -> Stream #0:0 (libx264)
  Stream #0:1 -> #0:1 (aac (native) -> aac (native))
[libx264 @ 00000243a23a1100] using SAR=1/1
[libx264 @ 00000243a23a1100] using cpu capabilities: MMX2 SSE2Fast SSSE3
SSE4.2 AVX FMA3 BMI2 AVX2
[libx264 @ 00000243a23a1100] profile High, level 3.0, 4:2:0, 8-bit
[libx264 @ 00000243a23a1100] 264 - core 164 - H.264/MPEG-4 AVC codec -
Copyleft 2003-2023 - http://www.videolan.org/x264.html - options: cabac=1
ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00
mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11
fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1
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=2 keyint=250 keyint_min=25 scenecut=40
intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0
qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
 "Output #0, mp4, toaa37f8d7685f4df9af85b1cdcd95997e.mp4':\r\n"
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: mp42mp41
    encoder         : Lavf60.10.100
  Stream #0:0: Video: h264 (avc1 / 0x31637661), yuv420p(tv, progressive),
800x450 [SAR 1:1 DAR 16:9], q=2-31, 25 fps, 12800 tbn
    Metadata:
      encoder         : Lavc60.22.100 libx264
    Side data:
      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A
  Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo,
fltp, 128 kb/s (default)
    Metadata:
      creation_time   : 2020-11-10T15:01:09.000000Z
      handler_name    : #Mainconcept MP4 Sound Media Handler
      vendor_id       : [0][0][0][0]
      encoder         : Lavc60.22.100 aac
frame=    0 fps=0.0 q=0.0 size=       0kB time=N/A bitrate=N/A
speed=N/A    \r'
frame=   21 fps=0.0 q=28.0 size=       0kB time=00:00:02.75 bitrate=  
0.1kbits/s speed=4.75x    \r'
[out#0/mp4 @ 00000243a230bd80] video:91kB audio:67kB subtitle:0kB other
streams:0kB global headers:0kB muxing overhead: 2.838559%
frame=  104 fps=101 q=-1.0 Lsize=     162kB time=00:00:04.13 bitrate=
320.6kbits/s speed=4.02x    
[libx264 @ 00000243a23a1100] frame I:1     Avg QP:18.56  size:  2456
[libx264 @ 00000243a23a1100] frame P:33    Avg QP:16.86  size:  1552
[libx264 @ 00000243a23a1100] frame B:70    Avg QP:17.55  size:   553
[libx264 @ 00000243a23a1100] consecutive B-frames:  4.8% 11.5% 14.4%
69.2%
[libx264 @ 00000243a23a1100] mb I  I16..4: 17.3% 82.1%  0.6%
[libx264 @ 00000243a23a1100] mb P  I16..4:  5.9% 15.2%  0.4%  P16..4: 18.3% 
0.9%  0.4%  0.0%  0.0%    skip:58.7%
[libx264 @ 00000243a23a1100] mb B  I16..4:  0.8%  0.3%  0.0%  B16..8: 15.4% 
1.0%  0.0%  direct: 3.6%  skip:78.9%  L0:34.2% L1:64.0% BI: 1.7%
[libx264 @ 00000243a23a1100] 8x8 transform intra:68.2% inter:82.3%
[libx264 @ 00000243a23a1100] coded y,uvDC,uvAC intra: 4.2% 18.4% 1.2% inter:
1.0% 6.9% 0.0%
[libx264 @ 00000243a23a1100] i16 v,h,dc,p: 53% 25%  8% 14%
[libx264 @ 00000243a23a1100] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 19%  6% 70%  1% 
1%  1%  1%  0%  0%
[libx264 @ 00000243a23a1100] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 46% 21% 15%  2% 
5%  4%  3%  3%  1%
[libx264 @ 00000243a23a1100] i8c dc,h,v,p: 71% 15% 13%  1%
[libx264 @ 00000243a23a1100] Weighted P-Frames: Y:30.3% UV:15.2%
[libx264 @ 00000243a23a1100] ref P L0: 46.7%  7.5% 34.6%  7.3%  3.9%
[libx264 @ 00000243a23a1100] ref B L0: 88.0% 10.5%  1.5%
[libx264 @ 00000243a23a1100] ref B L1: 98.1%  1.9%
[libx264 @ 00000243a23a1100] kb/s:177.73
[aac @ 00000243a23a2e00] Qavg: 1353.589


  


  I'm at a loss right now, would love any feedback/solution.

  


• GA360 vs GA4 : Key Differences and Challenges

  20 mai 2024, par Erin

  While the standard Universal Analytics (UA) was sunset for free users in July 2023, Google Analytics 360 (GA360) users could postpone the switch to GA4 for another 12 months. But time is running out. As July is rapidly approaching, GA360 customers need to prepare for the switch to Google Analytics 4 (GA4) or another solution. 

  This comparison post will help you understand the differences between GA360 vs. GA4. We’ll dive beneath the surface, examining each solution’s privacy implications and their usability, features, new metrics and measurement methods.

  What is Google Analytics 4 (Standard) ?

  GA4 is the latest version of Google Analytics, succeeding Universal Analytics. It was designed to address privacy issues with Universal Analytics, which made compliance with privacy regulations like GDPR difficult.

  It completely replaced Universal Analytics for free users in July 2023. GA4 Standard features many differences from the original UA, including :

  • Tracking and analysis are now events-based.
  • Insights are primarily powered by machine learning. (There are fewer reports and manual analysis tools).
  • Many users find the user interface to be too complex compared to Universal Analytics.

  The new tracking, reports and metrics already make GA4 feel like a completely different web analytics platform. The user interface itself also includes notable changes in navigation and implementation. These changes make the transition hard for experienced analysts and digital marketers alike. 

  For a more in-depth look at the differences, read our comparison of Google Analytics 4 and Universal Analytics.

  What is Google Analytics 360

  Google Analytics 360 is a paid version of Google Analytics, mostly aimed at enterprises that need to analyse a large amount of data.

  It significantly increases standard limits on data collection, sampling and processing. It also improves data granularity with more custom events and dimensions.

  Transitioning from Universal Analytics 360 to GA4 360

  You may still use the Universal Analytics tag and interface if you’ve been a Google Analytics 360 customer for multiple years. However, access to Universal Analytics 360 will be discontinued on July 1, 2024. Unlike the initial UA sunset (free version), you won’t be able to access the interface or your data after that, so it will be deleted.

  That means you will have to adapt to the new GA4 user interface, reports and metrics before the sunset or find an alternative solution.

  What is the difference between GA4 360 and free GA4 ?

  The key differences between GA4 360 and free GA4 are higher data limits, enterprise support, uptime guarantees and more robust administrative controls.

  

  GA4 offers most of the same features across the paid and free versions, but there are certain limits on data sampling, data processing and integrations. With the free version, you also can’t define as detailed events using event parameters as you can with GA4 360.

  Higher data collection, accuracy, storage and processing limits

  The biggest difference that GA4 360 brings to the table is more oomph in data collection, accuracy and analysis.

  You can collect more specific data (with 100 event parameters instead of 25 for custom metrics). GA4 360 lets you divide users using more custom dimensions based on events or user characteristics. Instead of 50 per property, you get up to 125 per property.

  And with up to 400 custom audiences, 360 is better for companies that heavily segment their users. More audiences, events and metrics per property mean more detailed insights.

  Sampling limits are also of a completely different scale. The max sample size in GA4 360 is 100x the free version of GA4, with up to 1 billion events per query. This makes analysis a lot more accurate for high-volume users. A slice of 10 million events is hardly representative if you have 200 million monthly events.

  Finally, GA4 360 lets you store all of that data for longer (up to 50 months vs up to 14 months). While new privacy regulations demand that you store user data only for the shortest time possible, website analytics data is often used for year-over-year analysis.

  Enterprise-grade support and uptime guarantees

  Because GA360 users are generally enterprises, Google offers service-level agreements for uptime and technical support response times.

  • Tracking : 99.9% uptime guarantee
  • Reporting : 99% uptime guarantee
  • Data processing : within 4 hours at a 98% uptime guarantee

  The free version of GA4 includes no such guarantees and limited access to professional support in the first place.

  Integrations

  GA4 360 increases limits for BigQuery and Google Ads Manager exports.

  

  The standard limits in the free version are 1 million events per day to BigQuery. In GA4 360, this is increased to billions of events per day. You also get up to 400 audiences for Search Ads 360 instead of the 100 limit in standard GA4.

  Roll-up analytics for agencies and enterprises

  If you manage a wide range of digital properties, checking each one separately isn’t very effective. You can export the data into a tool like Looker Studio (formerly Google Data Studio), but this requires extra work.

  With GA360, you can create “roll-up properties” to analyse data from multiple properties in the same space. It’s the best way to analyse larger trends and patterns across sites and apps.

  Administration and user access controls

  Beyond roll-up reporting, the other unique “advanced features” found in GA360 are related to administration and user access controls.

  

  First, GA360 lets you create custom user roles, giving different access levels to different properties. Sub-properties and roll-up properties are also useful tools for data governance purposes. They make it easier to limit access for specific analysts to the area they’re directly working on.

  You can also design custom reports for specific roles and employees based on their access levels.

  Pricing 

  While GA4 is free, Google Analytics 360 is priced based on your traffic volume. 

  With the introduction of GA4, Google implemented a revised pricing model. For GA4 360, pricing typically begins at USD $50,000/year which covers up to 25 million events per month. Beyond this limit, costs increase based on data usage, scaling accordingly.

  What’s not different : the interface, metrics, reports and basic features

  GA4 360 is the same analytics tool as the free version of GA4, with higher usage limits and a few enterprise features. You get more advanced tracking capabilities and more accurate analysis in the same GA4 packaging.

  If you already use and love GA4 but need to process more data, that’s great news. But if you’re using UA 360 and are hesitant to switch to the new interface, not so much. 

  Making the transition from UA to GA4 isn’t easy. Transferring the data means you need to figure out how to work with the API or use Google BigQuery.

  Plus, you have to deal with new metrics, reports and a new interface. For example, you don’t get to keep your custom funnel reports. You need to use “funnel explorations.”

  Going from UA to GA4 can feel like starting from scratch in a completely new web analytics tool.

  Which version of Google Analytics 4 is right for you ?

  Standard GA4 is a cost-effective web analytics option, but it’s not without its problems :

  • If you’re used to the UA interface, it feels clunky and difficult to analyse.
  • Data sampling is prevalent in the free version, leading to inaccuracies that can negatively affect decision-making and performance.

  And that’s just scratching the surface of common GA4 issues.

  Google Analytics 4 360 is a more reliable web analytics solution for enterprises. However, it suffers from many issues that made the GA4 transition painful for many free UA users last year.

  • You need to rebuild reports and adjust to the new complex interface.
  • To transfer historical data, you must use spreadsheets, the API, or BigQuery.

  You will still lose some of the data due to changes to the metrics and reporting.

  What if neither option is right for you ? Key considerations for choosing a Google Analytics alternative

  Despite what Google would like you to think, GA4 isn’t the only option for website analytics in 2024 — far from it. For companies that are used to UA 360, the right alternative can offer unique benefits to your company.

  Privacy regulations and future-proofing your analytics and marketing

  Although less flagrant than UA, GA4 is still in murky waters regarding compliance with GDPR and other privacy regulations. 

  And the issue isn’t just that you can get fined (which is bad enough). As part of a ruling, you may be ordered to change your analytics platform and protocol, which can completely disrupt your marketing workflow.

  When most marketing teams rely on web analytics to judge the ROI of their campaigns, this can be catastrophic. You may even have to pause campaigns as your team makes the adjustments.

  Avoid this risk completely by going with a privacy-friendly alternative.

  Features beyond basic web analytics

  To understand your users, you need to look at more than just events and conversions.

  That’s why some web analytics solutions have built-in behavioural analytics tools. Features like heatmaps (a visual pattern of popular clicks, scrolling and cursor movement) can help you understand how users interact with specific pages.

  

  Matomo allows you to consolidate behavioural analytics and regular web analytics into a single platform. You don’t need separate tools and subscriptions for heatmaps, session recordings, from analytics, media analytics and A/B testing. You can do all of this with Matomo.

  With insights about visits, sales, conversions, and usability in the same place, it’s a lot easier to improve your website.

  Try Matomo for Free

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

  Start for free

  No credit card required

  Usability and familiar metrics

  The move to event tracking means new metrics, reports and tools. So, if you’re used to Universal Analytics, it can be tricky to transition to GA4. 

  But there’s no need to start from zero, learning to work with a brand-new interface. Many competing web analytics platforms offer familiar reports and metrics — ones your team has gotten used to. This will help you speed up the time to value with a shorter learning curve.

  Why Matomo is a better option than GA4 360 for UA 360 users

  Matomo offers privacy-friendly tracking, built from the ground up to comply with regulations — including IP anonymisation and DoNotTrack settings. You also get 100% ownership of the data, which means we will never use your data for our own profit (unlike Google and other data giants).

  This is a big deal, as breaking GDPR rules can lead to fines of up to 4% of your annual revenue. At the same time, you’ll also future-proof your marketing workflow by choosing a web analytics provider built with privacy regulations in mind.

  Plus, for legacy UA 360 users, the Matomo interface will also feel a lot more intuitive and familiar. Matomo also provides marketing attribution models you know, like first click, which GA4 has removed.

  Finally, you can access various behavioural analytics tools in a single platform — heatmaps, session recordings, form analytics, A/B testing and more. That means you don’t need to pay for separate solutions for conversion rate optimisation efforts.

  And the transition is smooth. Matomo lets you import Universal Analytics data and offers ready-made Google Ads integration and Looker Studio Connector.

  Join over 1 million websites that choose Matomo as their web analytics solution. Try it free for a 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