Recherche avancée

Sur d’autres sites (9863)

• Why Matomo is a serious alternative to Google Analytics 360

  12 décembre 2018, par Jake Thornton — Marketing
  There’s no doubt about it, the free version of Google Analytics offers great value when it comes to making data-driven decisions for your business. But as your business starts to grow, so does the need for a more powerful web analytics tool.

  Why would I need to use a different web analytics tool ? It’s because Google Analytics (free version) is very limited when it comes to meeting the needs of a fast growing business whose website plays a pivotal role in converting its customers.

  This is where the Google Analytics 360 suite comes in, which is designed to meet the needs of businesses looking to get more accurate and insightful metrics.

  So what’s holding a growing business back from using Google Analytics 360 ?

  While GA360 sounds like a great option when upgrading your web analytics platform, we have found there are three core reasons holding businesses back from taking the leap :

  • Businesses can’t bear to swallow the US$150,000+ price tag (per year !) that comes with upgrading
  • Businesses can’t rely on GA360 to give them all the insights they need
  • Businesses want more control and ownership of their data

  Thankfully there are (only a few) alternatives and as the leading open-source alternative to Google Analytics, we hope to share insights on why Matomo Analytics can be the perfect solution for anyone at this crossroads in their web analytics journey.

  First, what does Google Analytics 360 offer that Google Analytics (free) doesn’t ?

  There’s no doubt about it, the GA360 suite is designed for larger sized businesses with demanding data limits, big budgets to use across the Google Marketing Platform (Google Adwords, DoubleClick etc.) and to get more advanced reporting visualisations and options.
  

  Data Sampling

  Data sampling is the elephant in the room when it comes to comparing GA360 with the freemium version. This is an entire article in its own right but at a basic level, Google Analytics samples your data (makes assumptions based on patterns) once the number of traffic visiting your website reaches a certain limit.

  Google Analytics provides the following information :

  Ad-hoc queries of your data are subject to the following general thresholds for sampling :

  Analytics Standard : 500k sessions at the property level for the date range you are using

  Analytics 360 : 100M sessions at the view level for the date range you are using

  In short, sampled data means inaccurate data. This is why as businesses grow, GA360 becomes a more attractive prospect because there’s no point making data-driven business decisions based on inaccurate data. This is a key weapon Google uses when selling to large businesses, however, this may not seem as concerning if you’re a small business within the sampled data range. For small businesses though, make sure you know the full extent of how this can affect your metrics, for example, your ecommerce data could be sampled, hence your GA reporting not matching your CRM/Ecommerce store data.

  Benefit of using Matomo : There is no data sampling anywhere in Matomo Analytics, that’s why we say 100% Accurate Data reporting across all plans.

  

  Integration with the Google Marketing Platform

  Yes ok, we’ll admit it, GA does a great job at integrating seamlessly with its own products like Google Ads, Google Optimize etc. with a touch of Salesforce integration ; while GA360 takes this to another level compared to it’s freemium version (integration with Google Search 360, Google Display & Video 360 etc.)

  But… what about non-Google advertising platforms ? Well with Google being a dominant leader as a search engine, web browser, email provider, social media channel ; sometimes Google needs to keep its best interests at heart.

  Google is an online advertising giant and a bonus of Google Search 360 is that you can integrate your Bing Ads, Baidu and Yahoo Japan Search campaigns but that’s about it when it comes to integrations from its direct competitors. 

  Benefit of using Matomo : No biased treatment. You can integrate your Google, Yahoo and Bing search consoles for accurate search engine reporting, and in early 2019, Matomo will be releasing a Google Ads, Bing Ads and Facebook Ads Manager integration feature.

  Roll-Up Reporting
  

  Roll-up reporting lets you combine multiple accounts and properties into one view. This is a great benefit when upgrading from GA freemium to GA360. For example, if you’re a digital agency with multiple clients or you manage multiple websites under the one account, the roll-up reporting feature is wonderful when you need to combine data and reporting, instantly.

  Benefit of using Matomo : Matomo’s got this covered ! Roll-up reporting is available in the Matomo Business package (starting at $29 per month) for cloud hosting or you can purchase as a Premium Feature for On-Premise starting at $99 per year.

  Staying in full control of your data

  Who would have thought that one of biggest reasons people choose Matomo isn’t because of anything that leads to a higher ROI, but for the fact that users want more control of their data.
  

  Matomo’s philosophy around data ownership is simple, you own your data, no one else. If you choose to host Matomo Analytics On-Premise then you are in complete control because your data is stored on your own servers where no one can gain access to it in whichever country you choose.

  So what about when you cloud host Matomo ? For users who don’t have the technical knowledge to host Matomo On-Premise, you can still have 100% data ownership and fully respect your user’s privacy when choosing to host Matomo Analytics through our cloud service.

  The difference between cloud hosting Matomo Analytics vs Google Analytics is that when you choose Matomo, we acknowledge you own the data and we have no right to access it. This means we can’t on-sell it to third-parties, we can’t claim ownership of it, you can export your data at anytime (how awesome is that !) and you can migrate between cloud hosting and hosting on-premise for ultimate flexibility whenever you want.

  Matomo also prides itself in allowing its users to be GDPR compliant with ease with a powerful GDPR Manager.

  Businesses can’t rely on Google Analytics 360 to give them all the insights they need

  Unlike Google Analytics 360, Matomo blends its Premium Web Analytics platform with Conversion Optimization features to allow its users to fully evaluate the user-experience on your website.

  Matomo is designed to be a complete analytics platform, meaning you have everything you need all in the one place which gives you greater insights and better business outcomes.

  
  These features include :

  Premium Web Analytics – You can still (accurately) measure all the basic metrics you love and are familiar with in Google Analytics like Location, Referrer traffic, Multi Attribution, Campaign Tracking and Ecommerce etc.

  Conversion Optimization – Eliminate the need for multiple analytics tools to get what Google Analytics doesn’t offer. These features include Heatmaps, Session Recordings, Form Analytics and more – giving you the best chance possible to convert more traffic by evaluating the user-experience.

  By having one tool for all your features you can integrate metrics, have one single view for all your data and it’s easy to use.

  Enhanced SEO – Get more insights into the performance of your search campaigns with unbiased search engine reporting, keyword ranking positions, integration with multiple search consoles and crawling stats. Google Analytics offers limited features to help with your SEO campaigns and only integrates with Google products.

  Visitor Profiles – Get a detailed life-time evaluation of every user who visits your website.

  Tag Manager – A powerful open-source Tag Manager tool to embed your third-party marketing tags. By being open-source and with our commitment to giving you 100% data ownership, you can always ensure you are in full control.

  Full Matomo vs Google Analytics 360 Comparison Table

  Just putting it out there ...

  Google leads the market with its freemium tool which offers great insights for businesses (fyi – Matomo has a forever free analytics tool too !), but when it comes to upgrading to get accurate reporting (kind of a big deal), owning your own data (a huge deal !) and having a complete range of features to excel ROI for your business, Matomo Analytics is often a preferred option to the Google Analytics 360 suite.

  Matomo is designed to be easy to use, is fully flexible and gives users full peace of mind by respecting user privacy. Want to learn more about the benefits of Matomo ?

• Q&A : An interview with Matomo founder, Matthieu Aubry

  20 novembre 2018, par Joselyn Khor — About, Community

  Hey everyone ! Joselyn here. As always the views of our community remain top of mind. So to make sure you guys know the thinking behind these new projects, we reached out to Matomo’s founder, Matthieu, to ask questions you might want answered. Please check it out below !

  Hi guys, it’s Matthieu ! Here to answer some questions about the rebrand and the future of Matomo and Innocraft.

  What’s upcoming ?

  We’ve been busy implementing our rebrand into all aspects of Matomo and there’s also our new website, which is launching today ! The new website will help people better understand what Matomo is and how they can benefit from using modern web analytics.

  Why was Matomo and Innocraft brought onto one website ?

  In the past the separation caused a bit of confusion so we’re taking this as a chance to unite both the business brand, Innocraft and community brand, Matomo, on one website. Putting our focus on one brand, Matomo, makes it easier for people to see us with fresh eyes. We have a community side as well as a business side and while the community is still incredibly important to us, we find we have a powerful analytics tool that is capable of helping businesses too.

  Is Matomo becoming commercial or turning corporate ?

  No. nothing is changing. Matomo is still an open-source project and community. Although we’ll have a pricing page and “start free trial” on the new website brought over from Innocraft.cloud, the Matomo community will still play the biggest part on the Matomo website. We have dedicated sections focused on Community and On-Premise.

  The rebrand exercise helped us gain a refreshed perspective. After reflecting on how far we’ve come, we can feel more confident about Matomo Analytics itself as a platform. We believe it’s a great chance to bring that confidence into the brand and vision. We are proud that it’s an awesome open-source platform and at the same time it’s also powerful as a tool for businesses.

  Why is there no ‘download for free’ button on the homepage ?

   

  
  We feel many users coming to the site will get confused about our hosting options (Cloud and On-Premise) which is something you don’t usually consider when choosing an analytics tool.

  The reason for us to not have that button is when people see a “download for free” button on the homepage next to a “try it for free” button, it creates confusion. For those who do choose to download Matomo often become confused when they are left with a .zip file unaware how to install it and the technical requirements of self-hosting. We feel presenting our users with the simplest installation option first will give them the best chance possible to try Matomo to its full potential, without cost.

  And you can still find the link to Download Matomo in the footer of each page.
  

   

  Is Matomo still free to download and have forever ?

  Absolutely. The free open-source download can be found on the On-Premise section of the website, or download Matomo here.

  Why is it important to have a business behind the project ?

  There’s the reality that we have to make money in order for the Matomo project to survive … and thrive. The reason we still need a business side (Innocraft) is to fund and sustain the Matomo project. Whenever people purchase premium features, this helps finance the development of Matomo for our community.

  Because of the business we’re able to continually maintain and develop Matomo for you guys as well as future users. For example, the next release Matomo 3.8.0 is already mostly developed and will bring lots of interesting features too, like the two-factor authentication, Brute Force Protection, failed tracking requests reporting, lots of JavaScript tracker improvements, a new total summary row below reports, and many more security fixes, bug fixes, and other new features.

  So we see a business being very helpful in supporting our open-source community. Without a business side, our free, open-source project would not be able to survive.

  How will you protect the Matomo project ?

  We’ve ensured the Matomo project will be protected for the future as we wish to turn it into a not-for-profit foundation.

  We’ve also got a safeguard where the open-source code will stay under a GPL license forever. This is so we can guarantee, that no matter what happens, the Matomo project itself will stay completely free software.

  Is there a way for people to help ?

  There are heaps of ways to help ! You can help other Matomo users in the forums, contribute to fixes on GitHub, leave a great review (e.g. alternativeTo), help look for bugs with our Security Bounty Programme or participate and spread the word about Matomo in our community social media pages – Mastodon, Facebook, Twitter. Telling your friends about us would be very helpful too !

  What’s planned for the future ?
  We’ve worked hard to become the #1 open-source analytics platform (1.4 million websites use Matomo today), but now we need to empower even more individuals and businesses to take back control of their own data.

  Showing our community that we have a powerful platform is crucial, but alongside that our values are what define us. User privacy is still of utmost importance and we’re here to make it known that power needs to rest in the hands of people and not large corporations.

  You can rest easy knowing you’re doing your part in using trustworthy and dependable tools. By joining many other companies who are growing this movement to decentralise the Internet, we can build a safer, online world together.

  Join this analytics revolution and let us know what you think about Matomo !

• FFmpeg avcodec_decode_video2 decode RTSP H264 HD-video packet to video picture with error

  29 mai 2018, par Nguyen Ba Thi

  I used FFmpeg library version 4.0 to have simple C++ program, in witch is a thread to receive RTSP H264 video data from IP-camera and display it in program window.

  Code of this thread is follow :

  DWORD WINAPI GrabbProcess(LPVOID lpParam)
  
  // Grabbing thread
  
  {
  
    DWORD i;
  
    int ret = 0, nPacket=0;
  
    FILE *pktFile;
  
    // Open video file
  
    pFormatCtx = avformat_alloc_context();
  
    if(avformat_open_input(&pFormatCtx, nameVideoStream, NULL, NULL)!=0)
  
        fGrabb=-1; // Couldn't open file
  
    else
  
    // Retrieve stream information
  
    if(avformat_find_stream_info(pFormatCtx, NULL)<0)
  
        fGrabb=-2; // Couldn't find stream information
  
    else
  
    {
  
        // Find the first video stream
  
        videoStream=-1;
  
        for(i=0; inb_streams; i++)
  
          if(pFormatCtx->streams[i]->codec->codec_type==AVMEDIA_TYPE_VIDEO)
  
          {
  
            videoStream=i;
  
            break;
  
          }
  
        if(videoStream==-1)
  
            fGrabb=-3; // Didn't find a video stream
  
        else
  
        {
  
            // Get a pointer to the codec context for the video stream
  
            pCodecCtxOrig=pFormatCtx->streams[videoStream]->codec;
  
            // Find the decoder for the video stream
  
            pCodec=avcodec_find_decoder(pCodecCtxOrig->codec_id);
  
            if(pCodec==NULL)
  
                fGrabb=-4; // Codec not found
  
            else
  
            {
  
                // Copy context
  
                pCodecCtx = avcodec_alloc_context3(pCodec);
  
                if(avcodec_copy_context(pCodecCtx, pCodecCtxOrig) != 0)
  
                    fGrabb=-5; // Error copying codec context
  
                else
  
                {
  
                    // Open codec
  
                    if(avcodec_open2(pCodecCtx, pCodec, NULL)<0)
  
                        fGrabb=-6; // Could not open codec
  
                    else
  
                    // Allocate video frame for input
  
                    pFrame=av_frame_alloc();
  
                    // Determine required buffer size and allocate buffer
  
                    numBytes=avpicture_get_size(pCodecCtx->pix_fmt, pCodecCtx->width,
  
                        pCodecCtx->height);
  
                    buffer=(uint8_t *)av_malloc(numBytes*sizeof(uint8_t));
  
                    // Assign appropriate parts of buffer to image planes in pFrame
  
                    // Note that pFrame is an AVFrame, but AVFrame is a superset
  
                    // of AVPicture
  
                    avpicture_fill((AVPicture *)pFrame, buffer, pCodecCtx->pix_fmt,
  
                        pCodecCtx->width, pCodecCtx->height);
  
  
  
                    // Allocate video frame for display
  
                    pFrameRGB=av_frame_alloc();
  
                    // Determine required buffer size and allocate buffer
  
                    numBytes=avpicture_get_size(AV_PIX_FMT_RGB24, pCodecCtx->width,
  
                        pCodecCtx->height);
  
                    bufferRGB=(uint8_t *)av_malloc(numBytes*sizeof(uint8_t));
  
                    // Assign appropriate parts of buffer to image planes in pFrameRGB
  
                    // Note that pFrameRGB is an AVFrame, but AVFrame is a superset
  
                    // of AVPicture
  
                    avpicture_fill((AVPicture *)pFrameRGB, bufferRGB, AV_PIX_FMT_RGB24,
  
                        pCodecCtx->width, pCodecCtx->height);
  
                    // initialize SWS context for software scaling to FMT_RGB24
  
                    sws_ctx_to_RGB = sws_getContext(pCodecCtx->width,
  
                        pCodecCtx->height,
  
                        pCodecCtx->pix_fmt,
  
                        pCodecCtx->width,
  
                        pCodecCtx->height,
  
                        AV_PIX_FMT_RGB24,
  
                        SWS_BILINEAR,
  
                        NULL,
  
                        NULL,
  
                        NULL);
  
  
  
                    // Allocate video frame (grayscale YUV420P) for processing
  
                    pFrameYUV=av_frame_alloc();
  
                    // Determine required buffer size and allocate buffer
  
                    numBytes=avpicture_get_size(AV_PIX_FMT_YUV420P, pCodecCtx->width,
  
                        pCodecCtx->height);
  
                    bufferYUV=(uint8_t *)av_malloc(numBytes*sizeof(uint8_t));
  
                    // Assign appropriate parts of buffer to image planes in pFrameYUV
  
                    // Note that pFrameYUV is an AVFrame, but AVFrame is a superset
  
                    // of AVPicture
  
                    avpicture_fill((AVPicture *)pFrameYUV, bufferYUV, AV_PIX_FMT_YUV420P,
  
                        pCodecCtx->width, pCodecCtx->height);
  
                    // initialize SWS context for software scaling to FMT_YUV420P
  
                    sws_ctx_to_YUV = sws_getContext(pCodecCtx->width,
  
                        pCodecCtx->height,
  
                        pCodecCtx->pix_fmt,
  
                        pCodecCtx->width,
  
                        pCodecCtx->height,
  
                        AV_PIX_FMT_YUV420P,
  
                        SWS_BILINEAR,
  
                        NULL,
  
                        NULL,
  
                        NULL);
  
                  RealBsqHdr.biWidth = pCodecCtx->width;
  
                  RealBsqHdr.biHeight = -pCodecCtx->height;
  
                }
  
            }
  
        }
  
    }
  
    while ((fGrabb==1)||(fGrabb==100))
  
    {
  
        // Grabb a frame
  
        if (av_read_frame(pFormatCtx, &packet) >= 0)
  
        {
  
          // Is this a packet from the video stream?
  
          if(packet.stream_index==videoStream)
  
          {
  
              // Decode video frame
  
              int len = avcodec_decode_video2(pCodecCtx, pFrame, &frameFinished, &packet);
  
              nPacket++;
  
              // Did we get a video frame?
  
              if(frameFinished)
  
              {
  
                  // Convert the image from its native format to YUV
  
                  sws_scale(sws_ctx_to_YUV, (uint8_t const * const *)pFrame->data,
  
                      pFrame->linesize, 0, pCodecCtx->height,
  
                      pFrameYUV->data, pFrameYUV->linesize);
  
                  // Convert the image from its native format to RGB
  
                  sws_scale(sws_ctx_to_RGB, (uint8_t const * const *)pFrame->data,
  
                      pFrame->linesize, 0, pCodecCtx->height,
  
                      pFrameRGB->data, pFrameRGB->linesize);
  
                  HDC hdc=GetDC(hWndM);
  
                  SetDIBitsToDevice(hdc, 0, 0, pCodecCtx->width, pCodecCtx->height,
  
                      0, 0, 0, pCodecCtx->height,pFrameRGB->data[0], (LPBITMAPINFO)&RealBsqHdr, DIB_RGB_COLORS);
  
                  ReleaseDC(hWndM,hdc);
  
                  av_frame_unref(pFrame);
  
              }
  
          }
  
          // Free the packet that was allocated by av_read_frame
  
          av_free_packet(&packet);
  
        }
  
     }
  
     // Free the org frame
  
    av_frame_free(&pFrame);
  
    // Free the RGB frame
  
    av_frame_free(&pFrameRGB);
  
    // Free the YUV frame
  
    av_frame_free(&pFrameYUV);
  
  
  
    // Close the codec
  
    avcodec_close(pCodecCtx);
  
    avcodec_close(pCodecCtxOrig);
  
  
  
    // Close the video file
  
    avformat_close_input(&pFormatCtx);
  
    avformat_free_context(pFormatCtx);
  
  
  
    if (fGrabb==1)
  
        sprintf(tmpstr,"Grabbing Completed %d frames", nCntTotal);
  
    else if (fGrabb==2)
  
        sprintf(tmpstr,"User break on %d frames", nCntTotal);
  
    else if (fGrabb==3)
  
        sprintf(tmpstr,"Can't Grabb at frame %d", nCntTotal);
  
    else if (fGrabb==-1)
  
        sprintf(tmpstr,"Couldn't open file");
  
    else if (fGrabb==-2)
  
        sprintf(tmpstr,"Couldn't find stream information");
  
    else if (fGrabb==-3)
  
        sprintf(tmpstr,"Didn't find a video stream");
  
    else if (fGrabb==-4)
  
        sprintf(tmpstr,"Codec not found");
  
    else if (fGrabb==-5)
  
        sprintf(tmpstr,"Error copying codec context");
  
    else if (fGrabb==-6)
  
        sprintf(tmpstr,"Could not open codec");
  
    i=(UINT) fGrabb;
  
    fGrabb=0;
  
    SetWindowText(hWndM,tmpstr);
  
    ExitThread(i);
  
    return 0;
  
  }
  
  // End Grabbing thread  

  When program receive RTSP H264 video data with resolution 704x576 then decoded video pictures are OK. When receive RTSP H264 HD-video data with resolution 1280x720 it look like that first video picture is decoded OK and then video pictures are decoded but always with some error.

  Please help me to fix this problem !

  Here is problems brief :
  I have an IP camera model HI3518E_50H10L_S39 (product of China).
  Camera can provide H264 video stream both at resolution 704x576 (with RTSP URI "rtsp ://192.168.1.18:554/user=admin_password=tlJwpbo6_channel=1_stream=1.sdp ?real_stream") or 1280x720 (with RTSP URI "rtsp ://192.168.1.18:554/user=admin_password=tlJwpbo6_channel=1_stream=0.sdp ?real_stream").
  Using FFplay utility I can access and display them with good picture quality.
  For testing of grabbing from this camera, I have a simple (above mentioned) program in VC-2005. In "Grabbing thread" program use FFmpeg library version 4.0 for opening camera RTSP stream, retrieve stream information, find the first video stream... and prepare some variables.
  Center of this thread is loop : Grab a frame (function av_read_frame) - Decode it if it’s video (function avcodec_decode_video2) - Convert to RGB format (function sws_scale) - Display to program window (GDI function SetDIBitsToDevice).
  When proram run with camera RTSP stream at resolution 704x576, I have good video picture. Here is a sample :
  704x576 sample
  When program run with camera RTSP stream at resolution 1280x720, first video picture is good :
  First good at res.1280x720
  but then not good :
  not good at res.1280x720
  Its seem to be my FFmpeg function call to avcodec_decode_video2 can’t fully decode certain packet for some reasons.