Recherche avancée

Sur d’autres sites (5765)

• How to create video using avcodec from jpeg images of type OpenCV::Mat ?

  23 juillet 2015, par theateist

  I have colored jpeg images of OpenCV::Mat type and I create from them video using avcodec. The video that I get is upside-down, black & white and each row of each frame is shifted and I got diagonal line. What could be the reason for such output ?
  Follow this link to watch the video I get using avcodec.
  I’m using acpicture_fill function to create avFrame from cv::Mat frame !

  P.S.
  Each cv::Mat cvFrame has width=810, height=610, step=2432
  I noticed that avFrame (that is filled by acpicture_fill) has linesize[0]=2430
  I tried manually setting avFrame->linesizep0]=2432 and not 2430 but it still didn’t helped.

  ======== CODE =========================================================

  AVCodec *encoder = avcodec_find_encoder(AV_CODEC_ID_H264);
  
  AVStream *outStream = avformat_new_stream(outContainer, encoder);
  
  avcodec_get_context_defaults3(outStream->codec, encoder);
  
  
  
  outStream->codec->pix_fmt = AV_PIX_FMT_YUV420P;
  
  outStream->codec->width = 810;
  
  outStream->codec->height = 610;
  
  //...
  
  
  
  SwsContext *swsCtx = sws_getContext(outStream->codec->width, outStream->codec->height, PIX_FMT_RGB24,
  
                                      outStream->codec->width, outStream->codec->height,  outStream->codec->pix_fmt, SWS_BICUBIC, NULL, NULL, NULL);
  
  
  
  for (uint i=0; i < frameNums; i++)
  
  {
  
      // get frame at location I using OpenCV
  
      cv::Mat cvFrame;
  
      myReader.getFrame(cvFrame, i); 
  
      cv::Size frameSize = cvFrame.size();    
  
      //Each cv::Mat cvFrame has  width=810, height=610, step=2432
  
  
  
  
  
  1.  // create AVPicture from cv::Mat frame
  
  2.  avpicture_fill((AVPicture*)avFrame, cvFrame.data, PIX_FMT_RGB24, outStream->codec->width, outStream->codec->height);
  
  3avFrame->width = frameSize.width;
  
  4.  avFrame->height = frameSize.height;
  
  
  
      // rescale to outStream format
  
      sws_scale(swsCtx, avFrame->data, avFrame->linesize, 0, outStream->codec->height, avFrameRescaledFrame->data, avFrameRescaledFrame ->linesize);
  
  encoderRescaledFrame->pts=i;
  
  avFrameRescaledFrame->width = frameSize.width;
  
      avFrameRescaledFrame->height = frameSize.height;
  
  
  
  av_init_packet(&avEncodedPacket);
  
      avEncodedPacket.data = NULL;
  
      avEncodedPacket.size = 0;
  
  
  
      // encode rescaled frame
  
      if(avcodec_encode_video2(outStream->codec, &avEncodedPacket, avFrameRescaledFrame, &got_frame) < 0) exit(1);
  
      if(got_frame)
  
      {
  
          if (avEncodedPacket.pts != AV_NOPTS_VALUE)
  
              avEncodedPacket.pts =  av_rescale_q(avEncodedPacket.pts, outStream->codec->time_base, outStream->time_base);
  
          if (avEncodedPacket.dts != AV_NOPTS_VALUE)
  
              avEncodedPacket.dts = av_rescale_q(avEncodedPacket.dts, outStream->codec->time_base, outStream->time_base);
  
  
  
          // outContainer is "mp4"
  
          av_write_frame(outContainer, & avEncodedPacket);
  
  
  
          av_free_packet(&encodedPacket);
  
      }
  
  }

  UPDATED

  As @Alex suggested I changed the lines 1-4 with the code below

  int width = frameSize.width, height = frameSize.height; 
  
  avpicture_alloc((AVPicture*)avFrame, AV_PIX_FMT_RGB24, outStream->codec->width, outStream->codec->height);
  
  for (int h = 0; h < height; h++)
  
  {
  
       memcpy(&(avFrame->data[0][h*avFrame->linesize[0]]), &(cvFrame.data[h*cvFrame.step]), width*3);
  
  }

  The video (here) I get now is almost perfect. It’s NOT upside-down, NOT black & white, BUT it seems that one of the RGB components is missing. Every brown/red colors became blue (in original images it should be vice-verse).
  What could be the problem ? Could rescaling(sws_scale) to AV_PIX_FMT_YUV420P format causes this ?

• How to build FFMPEG lib with android ndk

  27 janvier 2017, par S. Le Galloudec

  I introduce my problem : I’m a student working on a project asked by a company to my school.
  My part is to develop an android application (i have to use c++) who can make an authentication, ask to an api wich camera the client can watch, then display in real time the stream of the IP camera (using RTSP protocol)

  To be honnest i’m pretty lost. I’ve found the library FFMPEG, wich looks like useful to my project. If i got it right, the library can display a stream from a camera. So i built the library for my project, and then i tried to include it in my program.

  I did it the same way i did to include the library curl that i already use.

  But when i try to run my program, i got this message :

  FAILURE : Build failed with an exception.

  • What went wrong :
    Execution failed for task ’:app:externalNativeBuildDebug’.
    Build command failed.
    Error while executing ’/local/Android/Sdk/cmake/3.6.3155560/bin/cmake’ with arguments —build /local/Bureau/Projet2/videosurveillance/Application_Android/App_Android/app/.externalNativeBuild/cmake/debug/x86 —target lecteur
    [1/1] Linking CXX shared library ../obj/x86/liblecteur.so
    FAILED : : && /local/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ -target i686-none-linux-android -gcc-toolchain /local/Android/Sdk/ndk-bundle/toolchains/x86-4.9/prebuilt/linux-x86_64 —sysroot=/local/Android/Sdk/ndk-bundle/platforms/android-9/arch-x86 -fPIC -g -DANDROID -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -Wa,—noexecstack -Wformat -Werror=format-security -fno-exceptions -fno-rtti -std=gnu++11 -O0 -fno-limit-debug-info -Wl,—build-id -Wl,—warn-shared-textrel -Wl,—fatal-warnings -Wl,—no-undefined -Wl,-z,noexecstack -Qunused-arguments -Wl,-z,relro -Wl,-z,now -shared -Wl,-soname,liblecteur.so -o ../obj/x86/liblecteur.so CMakeFiles/lecteur.dir/src/main/cpp/lecteur.cpp.o ../../../../../distribution/ffmpeg/x86/lib/libswscale.a -lz /local/Android/Sdk/ndk-bundle/platforms/android-9/arch-x86/usr/lib/liblog.so -lm "/local/Android/Sdk/ndk-bundle/sources/cxx-stl/gnu-libstdc++/4.9/libs/x86/libgnustl_static.a" && :
    /local/Bureau/Projet2/videosurveillance/Application_Android/App_Android/app/src/main/cpp/lecteur.cpp:19 : error : undefined reference to ’avcodec_configuration’
    clang++ : error : linker command failed with exit code 1 (use -v to see invocation)
    ninja : build stopped : subcommand failed.

    Try :
    Run with —stacktrace option to get the stack trace. Run with —info or —debug option to get more log output.

  And i know that the problem comes from my cmakelist, or from my tree. But i don’t see the mistake, so if you could help me. Here is my cmakelist :

  cmake_minimum_required(VERSION 3.4.1)
  
  
  
  set(distribution_DIR ${CMAKE_SOURCE_DIR}/../distribution)
  
  
  
  
  
  add_library(lib-curl STATIC IMPORTED)
  
  
  
  add_library(ffmpeg SHARED IMPORTED)
  
  
  
  set_target_properties(lib-curl PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/curl/lib/${ANDROID_ABI}/libcurl.a)
  
  
  
  set_target_properties(ffmpeg PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libavcodec.a)
  
  
  
  set_target_properties(ffmpeg PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libavdevice.a)
  
  
  
  set_target_properties(ffmpeg PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libavfilter.a)
  
  
  
  set_target_properties(ffmpeg PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libavformat.a)
  
  
  
  set_target_properties(ffmpeg PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libavutil.a)
  
  
  
  set_target_properties(ffmpeg PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libpostproc.a)
  
  
  
  set_target_properties(ffmpeg PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libswresample.a)
  
  
  
  set_target_properties(ffmpeg PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libswscale.a)
  
  
  
  
  
  
  
  
  
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=gnu++11")
  
  
  
  
  
  add_library( # Sets the name of the library.
  
           downloader
  
           SHARED
  
           src/main/cpp/downloader.cpp
  
            #src/main/cpp/downloader.h
  
            )
  
  
  
  
  
  add_library( # Sets the name of the library.
  
           getrequest
  
           SHARED
  
           src/main/cpp/getrequest.cpp
  
            #src/main/cpp/getrequest.h
  
            )
  
  
  
  add_library( # Sets the name of the library.
  
           lecteur
  
           SHARED
  
           src/main/cpp/lecteur.cpp
  
            #src/main/cpp/lecteur.h
  
            )
  
  
  
  target_include_directories(downloader PRIVATE
  
                         ${distribution_DIR}/curl/include)
  
  
  
  target_include_directories(getrequest PRIVATE
  
                         ${distribution_DIR}/curl/include)
  
  
  
  target_include_directories(lecteur PRIVATE
  
                         ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/include)
  
  
  
  
  
  find_library( # Sets the name of the path variable.
  
            log-lib
  
  
  
            log )
  
  
  
  target_link_libraries( # Specifies the target library.
  
                     downloader
  
                     lib-curl
  
                     z
  
                     ${log-lib}
  
                     )
  
  
  
  target_link_libraries( # Specifies the target library.
  
                     getrequest
  
                     lib-curl
  
                     z
  
                     ${log-lib}
  
                     )
  
  
  
  target_link_libraries( # Specifies the target library.
  
                     lecteur
  
                     ffmpeg
  
                     z
  
                     ${log-lib}
  
                     )

  If you want to understand how i made my cmake, and what looks like my program you can check here : https://github.com/samylegalloudec/android-ndk-ffmepg

  Hope i was clear

  Best regards

  Edit n°1 :

  I think i’ve made a mistake in my cmakelist.txt so i fixed it (i guess) this way :

  cmake_minimum_required(VERSION 3.4.1)
  
  
  
  set(distribution_DIR ${CMAKE_SOURCE_DIR}/../distribution)
  
  
  
  
  
  add_library(lib-curl STATIC IMPORTED)
  
  
  
  
  
  
  
  set_target_properties(lib-curl PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/curl/lib/${ANDROID_ABI}/libcurl.a)
  
  
  
  add_library(ffmpeg-codec STATIC IMPORTED)
  
  set_target_properties(ffmpeg-codec PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libavcodec.a)
  
  
  
  add_library(ffmpeg-device STATIC IMPORTED)
  
  set_target_properties(ffmpeg-device PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libavdevice.a)
  
  
  
  add_library(ffmpeg-filter STATIC IMPORTED)
  
  set_target_properties(ffmpeg-filter PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libavfilter.a)
  
  
  
  add_library(ffmpeg-format STATIC IMPORTED)
  
  set_target_properties(ffmpeg-format PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libavformat.a)
  
  
  
  add_library(ffmpeg-util STATIC IMPORTED)
  
  set_target_properties(ffmpeg-util PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libavutil.a)
  
  
  
  add_library(ffmpeg-postproc STATIC IMPORTED)
  
  set_target_properties(ffmpeg-postproc PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libpostproc.a)
  
  
  
  add_library(ffmpeg-sample STATIC IMPORTED)
  
  set_target_properties(ffmpeg-sample PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libswresample.a)
  
  
  
  add_library(ffmpeg-scale STATIC IMPORTED)
  
  set_target_properties(ffmpeg-scale PROPERTIES IMPORTED_LOCATION ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/lib/libswscale.a)
  
  
  
  
  
  
  
  
  
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=gnu++11")
  
  
  
  
  
  add_library( # Sets the name of the library.
  
           downloader
  
           SHARED
  
           src/main/cpp/downloader.cpp
  
            #src/main/cpp/downloader.h
  
            )
  
  
  
  
  
  add_library( # Sets the name of the library.
  
           getrequest
  
           SHARED
  
           src/main/cpp/getrequest.cpp
  
            #src/main/cpp/getrequest.h
  
            )
  
  
  
  add_library( # Sets the name of the library.
  
           lecteur
  
           SHARED
  
           src/main/cpp/lecteur.cpp
  
            #src/main/cpp/lecteur.h
  
            )
  
  
  
  target_include_directories(downloader PRIVATE
  
                         ${distribution_DIR}/curl/include)
  
  
  
  target_include_directories(getrequest PRIVATE
  
                         ${distribution_DIR}/curl/include)
  
  
  
  target_include_directories(lecteur PRIVATE
  
                         ${distribution_DIR}/ffmpeg/${ANDROID_ABI}/include)
  
  
  
  
  
  find_library( # Sets the name of the path variable.
  
            log-lib
  
  
  
            log )
  
  
  
  target_link_libraries( # Specifies the target library.
  
                     downloader
  
                     lib-curl
  
                     z
  
                     ${log-lib}
  
                     )
  
  
  
  target_link_libraries( # Specifies the target library.
  
                     getrequest
  
                     lib-curl
  
                     z
  
                     ${log-lib}
  
                     )
  
  
  
  target_link_libraries( # Specifies the target library.
  
                     lecteur
  
                     ffmpeg-codec
  
                     ffmpeg-device
  
                     ffmpeg-filter
  
                     ffmpeg-format
  
                     ffmpeg-util
  
                     ffmpeg-postproc
  
                     ffmpeg-sample
  
                     ffmpeg-scale
  
                     z
  
                     ${log-lib}
  
                     )

  Now i have another message :

  FAILURE : Build failed with an exception.

  • What went wrong :
    Execution failed for task ’:app:externalNativeBuildDebug’.
    Build command failed.
    Error while executing ’/local/Android/Sdk/cmake/3.6.3155560/bin/cmake’ with arguments —build /local/Bureau/Projet2/videosurveillance/Application_Android/App_Android/app/.externalNativeBuild/cmake/debug/x86 —target lecteur
    [1/1] Linking CXX shared library ../obj/x86/liblecteur.so
    FAILED : : && /local/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ -target i686-none-linux-android -gcc-toolchain /local/Android/Sdk/ndk-bundle/toolchains/x86-4.9/prebuilt/linux-x86_64 —sysroot=/local/Android/Sdk/ndk-bundle/platforms/android-9/arch-x86 -fPIC -g -DANDROID -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -Wa,—noexecstack -Wformat -Werror=format-security -fno-exceptions -fno-rtti -std=gnu++11 -O0 -fno-limit-debug-info -Wl,—build-id -Wl,—warn-shared-textrel -Wl,—fatal-warnings -Wl,—no-undefined -Wl,-z,noexecstack -Qunused-arguments -Wl,-z,relro -Wl,-z,now -shared -Wl,-soname,liblecteur.so -o ../obj/x86/liblecteur.so CMakeFiles/lecteur.dir/src/main/cpp/lecteur.cpp.o ../../../../../distribution/ffmpeg/x86/lib/libavcodec.a ../../../../../distribution/ffmpeg/x86/lib/libavdevice.a ../../../../../distribution/ffmpeg/x86/lib/libavfilter.a ../../../../../distribution/ffmpeg/x86/lib/libavformat.a ../../../../../distribution/ffmpeg/x86/lib/libavutil.a ../../../../../distribution/ffmpeg/x86/lib/libpostproc.a ../../../../../distribution/ffmpeg/x86/lib/libswresample.a ../../../../../distribution/ffmpeg/x86/lib/libswscale.a -lz /local/Android/Sdk/ndk-bundle/platforms/android-9/arch-x86/usr/lib/liblog.so -lm "/local/Android/Sdk/ndk-bundle/sources/cxx-stl/gnu-libstdc++/4.9/libs/x86/libgnustl_static.a" && :
    /local/Android/Sdk/ndk-bundle/toolchains/x86-4.9/prebuilt/linux-x86_64/lib/gcc/i686-linux-android/4.9.x/../../../../i686-linux-android/bin/ld : warning : shared library text segment is not shareable
    /local/Android/Sdk/ndk-bundle/toolchains/x86-4.9/prebuilt/linux-x86_64/lib/gcc/i686-linux-android/4.9.x/../../../../i686-linux-android/bin/ld : error : treating warnings as errors
    clang++ : error : linker command failed with exit code 1 (use -v to see invocation)
    ninja : build stopped : subcommand failed.

  • Try :
    Run with —stacktrace option to get the stack trace. Run with —info or —debug option to get more log output.

• How Funnel for Piwik Analytics enriches your Piwik experience giving you ultimate insights and debugging capabilities

  13 janvier 2017, par InnoCraft — Community

  No matter what type of website or app you have, whether you are trying to get your users to sign up for something or sell products, there is a certain number of steps your visitors have to go through. On every step you lose visitors and therefore potential revenue and conversions. Therefore it is critical to know where your visitors actually follow those steps in your website or app, where you lose them and where your visitors maybe get confused. By defining a funnel, you can improve your conversion rates, sales and revenue as you can exactly determine where you lose your visitors in converting your goal or a sale.

  A Funnel defines a series of steps that you expect your visitors to take on their way to converting a goal. Funnels, a premium feature for Piwik developed by InnoCraft, lets you create funnels to get the data you need to improve your websites and mobile apps. Learn more about Funnel.

  In this blog post we will cover the reports the Funnel plugin provides. The next blog post shows you how to configure and validate your funnel in Piwik.

  

  Integration in Goal reports

  At Piwik and InnoCraft, we usually start looking into our goal reports. Funnel integrates directly into each goal reporting page giving you a quick overview how your funnel is doing. This saves us a lot of time as we don’t have to separately look into each funnel page and only takes us maybe an additional second to keep an eye on our funnels. By clicking on the headline or “View funnel report” link, you can directly go to the funnel report to get a more detailed report if you notice any spike in the evolution of the conversions or conversion rate.

  

  Getting an overall Funnel overview

  Next we usually go to the “Funnel Overview” page where it shows a list of all activated Funnels and their performance over time. You will find the look familiar as it is similar to the “Goals Overview” page. If we find something unusual there, for example any spikes, we usually directly click on the headline of the Funnel to go to the detailed Funnel report. You can also choose a funnel from the left reporting menu or search for a funnel by entering the shortcut “f”.

  

  Viewing a funnel report

  A funnel reporting page looks very similar to a Goal reporting page. It starts with an evolution graph and sparklines showing you the performance of your funnel over time.

  

  In the evolution graph you can select the metrics you want to plot. We usually have an eye on the funnel conversion rate and the number of “Funnel entries” or the number of “Funnel conversions”. The conversion rate alone does not show you how your funnel is performing. Imagine the rate is always stable at around 20% and you might think everything is alright, but if the number of visitors that take part in your funnel goes down, you might have a problem as the number of funnel conversions actually decreases even though the rate is the same. So we recommend to not only have a look at the conversion rate. The report will remember the metrics you want to plot each time you open it so you don’t have to re-select them over and over again.

  

  The funnel overview

  In the funnel overview we are giving you more details about the funnel and goal related conversion metrics so you don’t have to switch between the goal and funnel report and compare them easily.

  When you analyze a funnel report, you might not always remember how the funnel is configured. Even though you specify names for each step you sometimes need to know on which pages a certain step will be activated. By clicking on the funnel summary link you can quickly look into the funnel configuration and also see all important metrics at a glance in a simple table without having to scroll.

  

  You might also notice the Visitor Log link which will show you all actions for all visitors that have entered this funnel. This lets you really understand how your visitors navigate through your website and how they proceeded, exited or converted your funnel on a visitor level.

  

  The Funnel visualization

  Below the funnel overview you can visually see where your visitors entered, proceeded, converted and exited your funnel. We kept the UI clean so you can focus on the important things.

  Most tools only give you the pages where visitors have entered your funnel but we do better and also show you the list of external referrers used by visitors to enter your funnel directly (marketing campaigns, search engines or other websites). Also we do not only show only the top 5 pages but up to 100 pages and 50 referrers (more can be configured if needed). When you hover a row, you will not only see the number of hits but also the percentage each row has contributed to the entries. Here you want to look and understand how your visitors enter your funnel and based on the data maybe invest in successful referrers, campaigns and pages. If the pages or referrers you expect to see there don’t show up, your users might not understand the path you had in mind for them.

  

  Next you may notice how many visits have gone through each step, in this case 3487 visits. The green and red bar lets you quickly identify how many of your visitors have proceeded to the next step (green) compared to how many have exited the funnel at this step (red). Ideally, most of the bar is green and not red indicating that more visitors proceed to the next step than they exit.

  

  Now the next feature is really valuable. When you hover the step title or the number of visits, you will notice that two icons appear :

  

  Those two little icons are really powerful and give you even more insights to really dig into all the data. The left icon shows you the visitor log showing all actions of each visitor that have participated in this particular funnel step. This means for each step you get to see all the details and actions of each visitor. This lets you really debug and understand problems in your funnel.

  At InnoCraft, we understand that plain numbers are often not so valuable. Only the evolution over time, when you put the numbers in relation to something else you can really understand how your website is doing. The icon to the right lets you do exactly this, it lets you view the row evolution for each funnel step. We are sure you will enjoy this feature. It lets you explore how each funnel step is doing over time. For example the number of entries for a step or how many proceeded to the next step from here over time. Here you ideally want to see that the “Proceeded Rate” increases over time, meaning more and more visitors actually proceed to the next step instead of exiting it.

  

  We are sure you will really love those features that give you just those extra insights that other tools don’t give you.

  On the right you can find out where your visitors went to, if they did not proceed any further in the funnel. This lets you better understand why they left the funnel and did not proceed any further.

  

  At the end of the funnel report you find again the number of conversions and the conversion rate. Here we recommend looking into the visitor log when you hover the name of the last step as you can analyze how each visitor converted this funnel in detail.

  

  Applying segments

  Funnels lets you apply any Piwik segment to the Funnel report allowing you to dice your visitors multiplying the value you get out of Funnel. For example you may want to apply a segment and analyze the funnel for visitors that have visited your website or mobile app for the first time vs. recurring visitors. Sometimes it may be interesting how visitors from different countries go through your funnel, the possibilities are endless. We really recommend to take advantage of segments to understand your different target groups even better.

  The plugin also adds some new segments to your Piwik letting you segment any Piwik report by visitors that have participated in a funnel or participated in a particular funnel step. For example you could go to the “Visitors => Locations” report and apply a segment for your funnel to see which countries have participated or converted most in your funnel.

  Widgets, Scheduled Reports, and more.

  This is not where the fun ends. Funnels defines new widgets that you can add to your dashboard or export it into a third party website. You can set up scheduled reports to receive the Funnel report automatically via email or sms or download the report to share it with your colleagues. It works also very well with Custom Alerts and you can view the Funnel report in the Piwik Mobile app. You can manage Funnels via HTTP API and also fetch all Funnel reports via the HTTP Reporting API. The plugin is really nicely integrated into Piwik we will need some more blog posts to show you all the ways Funnels advances your Piwik experience and how it lets you dig into all the data so you can increase your conversions and sales based on this data.

  How to get Funnels and related features

  You can get Funnels on the Piwik Marketplace. If you want to learn more about Funnels you might be also interested in the Funnel User Guide and the Funnel FAQ.

  Similar to Funnels we also offer Users Flow which lets you visualize the flow of your users and visitors across several interactions.