Recherche avancée

Sur d’autres sites (6291)

• How to configure and validate a Funnel in Piwik Analytics

  16 janvier 2017, par InnoCraft — Community

  In the last blog post we have covered how the conversion Funnel plugin enriches your Piwik experience. This post will focus on how to configure and validate your funnel in Piwik so you get the correct data when you view the funnel reports. When you set up a funnel, it is crucial to have it configured correctly as the funnel report will be only as good as its configuration. When we built this Funnel feature, we focused on making the configuration and validation real simple because it is so important to get it right.

  To recap quickly : A Funnel defines a series of steps that you expect your visitors to take on their way to converting a goal or a sale. Funnels, a premium feature for Piwik developed by InnoCraft, lets you define funnels so you can improve your websites and mobile apps based on this data. Learn more about Funnel.

  Configuring a funnel

  As you will notice Funnels integrates nicely into the Piwik Goals management. You can configure a funnel whenever you create or update a goal. You can access the Goals Management either via “Administration => Goals” or via the reporting menu “Goals => Manage”. Then click on either “Add a new goal” or select an existing goal to edit it. At the bottom of the goal form, you will see a new row letting you configure a funnel. As with all our premium features we focused on displaying lots of inline help and explain directly in the UI what a funnel is about, what the steps are in order to configure a funnel, how a funnel helps you and more. This lets you use the Funnel feature even if you have never created or analyzed a funnel before.

  Preparing your Funnel configuration

  Before starting to configure a Funnel we usually have a brainstorm session identifying the funnels on a website or app and the paths we expect users to take there. Once we have identified each step, we click through those identified pages in our website and we note the URLs for each page as the URLs will be needed when you configure a funnel.

  Setting up a Goal

  Once we have finished the planning phase it is time to log into Piwik. We start by either adding a new goal or selecting an existing goal. If you are unfamiliar with setting up goals, have a look at the Piwik Goals user guide. At the bottom of a goal form when you create or update a goal, you can configure your funnel. The UI will first explain you everything about Funnels, what they are, how they help you and which steps you need to take in order to configure it.

  Configuring Funnel steps

  We start by configuring the steps we have identified in the planning phase. Those are the steps we expect our users to take when they convert a goal or purchase something. Now we need to add a step for each page we expect users to take, each step consists of a name and a pattern.

  The name will be shown to you in the funnel reporting so think of a good name that describes each step best, for example “Product”, “Cart”, “Checkout” and “Order”.

  The pattern is needed to define when a visitor will enter this step. Here it comes in handy to have already notes for each URL from the planning phase. You can select lots of different patterns based on “URL Path”, “URL” and “URL parameter”. For example “URL starts with”, “Path ends with”, “URL contains”, “URL matches the regular expression”, and more. Most tools make this configuration unnecessarily hard because they only allow you to choose from one or two patterns (only complicated pattern like regular expressions) and they don’t let you validate whether the URL you have in mind actually matches the pattern. There are three ways to validate your step configurations.

  

  Validating funnel steps

  When we configure a funnel, we validate our steps in the following three ways.

  1. Via the help icon next to the step configuration

  When you click on the help icon, you will receive valuable tips about configuring steps, what “required” means and how to match popular pages. It will also show you a list of all URLs that were tracked in your Piwik in the past and match your specified pattern. For example say you specify a pattern “Path starts with /products”, then Piwik will list all URLs that were tracked in the past matching this pattern. This lets you validate whether your pattern actually matches the URLs you had in mind. It will also show you if the pattern doesn’t match any known URL which can indicate that your configuration may be wrong.

  

  2. Via the URL validator

  Below the steps configuration you find a form field that lets you enter any URL.

  

  We recommend to enter each URL that you have noted before in the planning phase. Once you enter a URL, the configurations will be validated immediately and the result will be shown to you in the step configuration. When a step matches your specified URL, the background will become green, when a step does not match the URL, the background will be red.

  

  If the URL does not match the expected step, simply change your step configuration and the steps will be re-validated as you change the configuration. This way you will see instantly as soon as you got the configuration right.

  What you don’t want is that either all of your steps don’t match (red background) or that several steps match a certain URL (green background). When several step match one URL, then one visitor might enter several funnel steps on just one page. This usually indicates a problem with the step configuration.

  3. Manual funnel validation

  After we have created or updated the goal (more about this soon), we always test a funnel configuration manually. This means we now open our website and click through the pages that we hand in mind and check afterwards whether the steps we took actually appear in the funnel report as expected. This is just another safety net to make sure your funnel configuration is right.

  It is really crucial to have a correct funnel configuration as otherwise the shown data in the funnel reports might not be as helpful. That’s why we focused so much on making the validation part real easy.

  Activating and saving the funnel

  Once you are happy with your configuration, it is time to activate your funnel. As soon as you activate your funnel, a report for this funnel will be generated and the links and reports for this funnel will be visible in the UI. If you are later no longer interested in the funnel, simply deactivate the funnel so it won’t appear in the reporting UI anymore.

  

  To save your funnel configuration simply click on either “Add goal” or “Update goal”. The funnel will be automatically saved whenever you update your goal.

  Goals Management

  The funnel plugin also enriches the list of goals in the Piwik goal management. At a glance you can see whether a funnel for a goal is configured and activated (green tick in the funnel column), whether a funnel is configured but not activated (grey tick in the funnel column) or whether no funnel is configured for a goal (no tick at all).

  

  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.

• Concatenate / Join MP4 files using ffmpeg and windows command line batch NOT LINUX

  17 juillet 2014, par julesverne

  I’ve written a batch script that attempts to take a generic introductory title video (MP4) that runs for 12 seconds and attaches it to the beginning of 4 other MP4 videos (same video but each has a different language audio track)

  According to ffmpeg syntax here : http://ffmpeg.org/trac/ffmpeg/wiki/How%20to%20concatenate%20%28join,%20merge%29%20media%20files the concat demuxer needs to be run from a text file that looks like this :

  # this is a comment
  
  file '/path/to/file1'
  
  file '/path/to/file2'
  
  file '/path/to/file3'

  I believe everything in my script up until the point of joining the files appears to be working correctly. But I get this error :

  [concat @ 04177d00] Line 2: unknown keyword ''C:\Users\Joe\1May\session3\readyforfinalconversion\frenchfile.mp4'
  
  filelistFrench.txt: Invalid data found when processing input
  
  [concat @ 03b70a80] Line 2: unknown keyword ''C:\Users\Joe\1May\session3\readyforfinalconversion\spanishfile.mp4'
  
  filelistSpanish.txt: Invalid data found when processing input
  
  [concat @ 0211b960] Line 2: unknown keyword ''C:\Users\Joe\1May\session3\readyforfinalconversion\basquefile.mp4'
  
  filelistBasque.txt: Invalid data found when processing input
  
  [concat @ 03a20a80] Line 2: unknown keyword ''C:\Users\Joe\1May\session3\readyforfinalconversion\Englishfile.mp4'
  
  filelistEnglish.txt: Invalid data found when processing input

  I believe the issue lies in the text file I’m creating. Please excuse my n00b ignorance, but sometimes new script makers like myself get confused about developer jargon and may take things literally.

  So when I look at that example text file they gave, am I correct in thinking THIS is what my text file should look like ?

  # this is a comment
  
  Titlefile.mp4 'C:\Users\Joe\1May\session3\readyforfinalconversion\Titlefile.mp4'
  
  Englishfile.mp4 'C:\Users\Joe\1May\session3\readyforfinalconversion\Englishfile.mp4'

  Again, am I being too literal ? are the quotations correct ? Are the slashes correct ? In the example they provide the slashes in the path are / instead of normal windows \ . I’ll provide the entire script in case it helps.

  @echo off
  
  
  
  setlocal EnableDelayedExpansion
  
  
  
  rem Create an array of languages
  
  set i=0
  
  for %%a in (French Spanish Basque English) do (
  
     set /A i+=1
  
     set term[!i!]=%%a
  
  )
  
  
  
  rem Get the title video file name from user
  
  
  
  set /p titlevideofilename=What is the title video file 
  
  
  
  name?
  
  
  
  rem create a path variable for the title video file
  
  
  
  set pathtotitlevideo=%~dp0%titlevideofilename%
  
  
  
  rem Get the names of the different language video files to append to the title video
  
  rem create a path variable for each different language video files
  
  
  
  for /L %%i in (1,1,4) do (
  
     set /p language[%%i]=what is the name of the !term
  
  
  
  [%%i]! file you want to append after the title video?
  
     set pathtofile[%%i]=%~dp0!language[%%i]!
  
  )
  
  
  
  rem create data file for ffmpeg based on variable data
  
  
  
  for /L %%i in (1,1,4) do (
  
      echo # this is a comment>>filelist!term[%
  
  
  
  %i]!.txt
  
      echo file '%pathtotitlevideo%'>>filelist!term[%
  
  
  
  %i]!.txt
  
      echo file '!pathtofile[%%i]!'>>filelist!term[%
  
  
  
  %i]!.txt
  
  )
  
  
  
  cls
  
  
  
  rem join files using ffmpeg concat option
  
  
  
  for /L %%i in (1,1,4) do (
  
     c:\ffmpeg\ffmpeg\bin\ffmpeg.exe -loglevel error -f 
  
  
  
  concat -i filelist!term[%%i]!.txt -c copy !language[%
  
  
  
  %i]!.!term[%%i]!.withtitle.mp4
  
  )
  
  
  
  endlocal
  
  
  
  :eof
  
  exit

  EDIT
  Thanks to @foxidrive making me look at the simplicity of it... it occurred to me that Apparently I wasn’t being literal enough. I made these 3 changes and script works perfectly now
  1 : "file" in there example literally meant the word "file"
  2 : needed the use of single quotes not double quotes as it shows in there example.
  3 : Used "\" instead of "/" as they have in there example.

  So NOW my code to create the text files looks like this :

  rem create data file for ffmpeg based on variable data
  
  
  
  for /L %%i in (1,1,4) do (
  
      echo # this is a comment>>filelist!term[%
  
  
  
  %i]!.txt
  
      echo file '%pathtotitlevideo%'>>filelist!term[%
  
  
  
  %i]!.txt
  
      echo file '!pathtofile[%%i]!'>>filelist!term[%
  
  
  
  %i]!.txt
  
  )

  So NOW my text file looks like this :

  # this is a comment    
  
  file 'C:\Users\Joe\1May\session3\readyforfinalconversion\Titlefile.mp4'
  
  file 'C:\Users\Joe\1May\session3\readyforfinalconversion\Englishfile.mp4'

• Revision f76f52df61 : Limit Key frame Intra modes checks. Most of the focus so far has been on inter

  22 août 2013, par Paul Wilkins

  Changed Paths :
   Modify /vp9/encoder/vp9_onyx_if.c

  
   Modify /vp9/encoder/vp9_onyx_int.h

  
   Modify /vp9/encoder/vp9_rdopt.c

  
  
  Limit Key frame Intra modes checks.

  Most of the focus so far has been on inter frames.

  At high speed settings the key frame is now taking a high %
  of the cycles.

  This patch puts in some masking to reduce the number
  of INTRA modes searched during key frame coding (as already
  happens for inter frames) at higher speed settings

  TODO : Develop this further with either adaptive rd thresholds
  when choosing which intra modes to consider or some other
  heuristic.

  Impact.
  At high speed settings on some clips the key frame was starting
  to dominate. In a coding of the first 50 frames of AKIYO at speed
  2 limiting the key frame intra modes to DC or TM_PRED resulted in
   30% overall speedup. For Bus the number was lower at 4-5%.

  Change-Id : I7bde68aee04995f9d9beb13a1902143112e341e2