Recherche avancée

Sur d’autres sites (14530)

• Make better marketing decisions with attribution modeling

  19 décembre 2017, par InnoCraft — Community, Plugins

  Do you suspect some traffic sources are not getting the rewards they deserve ? Do you want to know how much credit each of your marketing channel actually gets ?

  When you look at which referrers contribute the most to your goal conversions or purchases, Piwik shows you only the referrer of the last visit. However, in reality, a visitor often visits a website multiple times from different referrers before they convert a goal. Giving all credit to the referrer of the last visit ignores all other referrers that contributed to a conversion as well.

  You can now push your marketing analysis to the next level with attribution modeling and finally discover the true value of all your marketing channels. As a result, you will be able to shift your marketing efforts and spending accordingly to maximize your success and stop wasting resources. In marketing, studying this data is called attribution modeling.

  Get the true value of your referrers

  Attribution is a premium feature that you can easily purchase from the Piwik marketplace.

  Once installed, you will be able to :

  • identify valuable referrers that you did not see before
  • invest in potential new partners
  • attribute a new level of conversion
  • make this work very easily by filling just a couple of form information

  Identify valuable referrers that you did not see before

  You probably have hundreds or even thousands of different sources listed within the referrer reports. We also guess that you have the feeling that it is always the same referrers which are credited of conversions.
  Guess what, those data are probably biased or at least are not telling you the whole story.
  Why ? Because by default, Piwik only attributes all credit to the last referrer.

  

  It is likely that many non credited sources played a role in the conversion process as well as people often visit your website several times before converting and they may come from different referrers.

  This is exactly where attribution modeling comes into play. With attribution modeling, you can decide which touchpoint you want to study. For example, you can choose to give credit to all the referrers a single visitor came from each time the user visits your website, and not only look at the last one. Without this feature, chances are, that you have spent too much money and / or efforts on the wrong referrer channels in the past because many referrers that contributed to conversions were ignored. Based on the insights you get by applying different attribution models, you can make better decisions on where to shift your marketing spending and efforts.

  Invest in potential new partners

  Once you apply different attribution models, you will find out that you need to consider a new list of referrers which you before either over- or under-estimated in terms of how much they contributed to your conversions. You probably did not identify those sources before because Piwik shows only the last referrer before a conversion. But you can now also look at what these newly discovered referrers are saying about your company, looking for any advertising programs they may offer, getting in contact with the owner of the website, and more.

  Apply up to 6 different attribution models

  By default, Piwik is attributing the conversion to the last referrer only. With attribution modeling you can analyze 6 different models :

  • Last Interaction : the conversion is attributed to the last referrer, even if it is a direct access.
  • Last Non-Direct : the conversion is attributed to the last referrer, but not in the case of a direct access.
  • First Interaction : the conversion is attributed to the first referrer which brought you the visit.
  • Linear : whatever the number of referrers which brought you the conversion, they will all get the same value.
  • Position Based : first and last referrer will be attributed 40% each the conversion value, the remaining 60% is divided between the rest of the referrers.
  • Time Decay : this attribution model means that the closer to the date of the conversion is, the more your last referrers will get credit.

  Those attribution models will enable you to analyze all your referrers deeply and increase your conversions.

  Let’s look at an example where we are comparing two models : “last interaction” and “first interaction”. Our goal is to identify whether some referrers that we are currently considering as less important, are finally playing a serious role in the total amount of conversions :

  

  Comparing Last Interaction model to First Interaction model

  Here it is interesting to observe that the website www.hongkiat.com is bringing almost 90% conversion more with the first interaction model rather than the last one.

  As a result we can look at this website and take the following actions :

  • have a look at the message on this website
  • look at opportunities to change the message
  • look at opportunities to display extra marketing messages
  • get in contact with the owner to identify any other communication opportunities

  The Multi Channel Attribution report

  Attribution modeling in Piwik does not require you to add any tracking code. The only thing you need is to install the plugin and let the magic happen.
  Simple as pie is the word you should keep in mind for this feature. Once installed, you will find the report within the goal section, just above the goals you created :

  

  The Multi Attribution menu

  There you can select the attribution model you would like to apply or compare.

  Attribution modeling is not just about playing with a new report. It is above all an opportunity to increase the number of conversions by identifying referrers that you may have not recognized as valuable in the past. To grow your business, it is crucial to identify the most (and least) successful channels correctly so you can spend your time and money wisely.

  Learn more about Multi Channel Conversion Attribution

• avfilter/vf_deshake : replace qsort with AV_QSORT

  31 octobre 2015, par Ganesh Ajjanagadde

  avfilter/vf_deshake : replace qsort with AV_QSORT
  qsort is called indirectly in filter_frame, suggesting its performance
  
  criticality. AV_QSORT is substantially faster due to the inlining of the
  
  comparison callback. Thus, the increase in performance should be worth
  
  the increase in binary size.
  This optimization is just a low hanging fruit. The trac ticket 1430 is
  
  a request for an improved deshake filter.
  Sample benchmark (x86-64, Haswell, GNU/Linux) :
  
  File : original from https://trac.ffmpeg.org/ticket/1430
  
  command : ffmpeg -stream_loop 8 -i file.webm -vf deshake=rx=64:ry=64 -f null -
  Timer truncated at 1024 runs.
  
  new :
  
  28260 decicycles in qsort,       1 runs,      0 skips
  
  35570 decicycles in qsort,       2 runs,      0 skips
  
  39010 decicycles in qsort,       4 runs,      0 skips
  
  46897 decicycles in qsort,       8 runs,      0 skips
  
  40442 decicycles in qsort,      16 runs,      0 skips
  
  41611 decicycles in qsort,      32 runs,      0 skips
  
  40345 decicycles in qsort,      64 runs,      0 skips
  
  38967 decicycles in qsort,     128 runs,      0 skips
  
  38647 decicycles in qsort,     256 runs,      0 skips
  
  40238 decicycles in qsort,     512 runs,      0 skips
  
  39676 decicycles in qsort,    1024 runs,      0 skips
  old :
  
  1740280 decicycles in qsort,       1 runs,      0 skips
  
   923560 decicycles in qsort,       2 runs,      0 skips
  
   511330 decicycles in qsort,       4 runs,      0 skips
  
   309720 decicycles in qsort,       8 runs,      0 skips
  
   194900 decicycles in qsort,      16 runs,      0 skips
  
   142686 decicycles in qsort,      32 runs,      0 skips
  
   112516 decicycles in qsort,      64 runs,      0 skips
  
    98166 decicycles in qsort,     128 runs,      0 skips
  
    88147 decicycles in qsort,     256 runs,      0 skips
  
    88706 decicycles in qsort,     512 runs,      0 skips
  
    86783 decicycles in qsort,    1024 runs,      0 skips
  Reviewed-by : Nicolas George <george@nsup.org>
  
  Reviewed-by : Michael Niedermayer <michael@niedermayer.cc>
  
  Signed-off-by : Ganesh Ajjanagadde <gajjanagadde@gmail.com>
  

  • [DH] libavfilter/vf_deshake.c

• doc/developer : revise mailing list section

  4 décembre 2017, par Jim DeLaHunt

  doc/developer : revise mailing list section
  The Developer Documentation had instructions to
  
  subscribe to the ffmpeg-cvslog email list. But that is
  
  no longer accurate. For the purposes in this section —
  
  review of patches, discussion of development issues —
  
  ffmpeg_devel is the appropriate email list. Some developers
  
  may want to monitor ffmpeg-cvslog, but it is not mandatory.
  This is v3 of this doc, based on discussion in thread
  
  <https://ffmpeg.org/pipermail/ffmpeg-devel/2017-November/220528.html> ;
  
  and in response to docs Maintainer comments in
  
  <https://ffmpeg.org/pipermail/ffmpeg-devel/2017-December/221596.html>.
  1. In doc/developer.texi, add a new section about
  
  ffmpeg-devel, based on existing text from ffmpeg-cvslog
  
  section regarding discussion of patches and of
  
  development issues. Reflect wording from discussion at
  
  <https://ffmpeg.org/pipermail/ffmpeg-devel/2017-November/221199.html> ;
  
  but with copy-editing to make wording more concise.
  2. In doc/developer.texi, rewrite the ffmpeg-cvslog section
  
  to match the current usage of ffmpeg-cvslog. Some
  
  developers choose to follow this list, but it is not
  
  mandatory.
  There are a lot of improvements possible to the
  
  Developer Documentation page, beyond this refactoring.
  
  However, making those improvements is a much bigger
  
  and more difficult task.  This change is "low hanging
  
  fruit".
  Signed-off-by : Jim DeLaHunt <from.ffmpeg-dev@jdlh.com>
  
  Signed-off-by : Timothy Gu <timothygu99@gmail.com>
  

  • [DH] doc/developer.texi