Recherche avancée

Sur d’autres sites (10137)

• How you can use the Piwik AOM plugin to improve your data and make better online marketing decisions

  13 septembre 2017, par André Kolell — Plugins, AdWords, Bing, Case Study, Criteo, eccommerce tracking, Facebook Ads, how to install piwik analytics, how-to piwik, integration, piwik, Taboola

  Hi, this is André, one of the authors of the Piwik Advanced Online Marketing plugin, which has just hit 5,000 downloads on the Piwik marketplace. In this blog post I’ll show you how Piwik AOM improves your data and enables you to make better online marketing decisions.

  Piwik itself is excellent in tracking all kinds of visitor data, like where a visitor is coming from and what he’s doing on your page or app (pageviews, events, conversions). But what Piwik did not yet take a closer a look at, is how much you’ve invested into your marketing activities and how profitable they are.

  With the Piwik AOM plugin you can integrate data like advertising costs, advertising campaign names, ad impressions etc. from advertising platforms (such as Google AdWords, Microsoft Bing, Criteo, Facebook Ads and Taboola) and individual campaigns (such as such as cost per view/click/acquisition and fixed price per months deals) into Piwik and combine that data with individual Piwik visits.

  Piwik AOM adds a new marketing performance report to Piwik giving you a great overview of all your marketing activities with drill-down functionality :

  

   

  When taking a look at a specific visitor, Piwik AOM shows you the exact cost of acquiring a specific visit :

  

   

  Leveraging Piwik AOM’s full potential

  But although you can access Piwik AOM’s valuable data directly in the Piwik UI for ad-hoc analyses, Piwik AOM’s true strength comes into play when working with the raw data in an external business intelligence application of your choice, where you can further integrate Piwik AOM’s data with your most accurate backend data (like conversion’s contribution margins after returns, new vs. existing customer, etc.).

  Piwik AOM offers some API endpoints that allow you to fetch the data you need but you can also retrieve it directly from Piwik AOM’s aom_visits table, which includes all visits, all allocated advertising costs and advertising campaign details. As there is never data being deleted from aom_visits, the table can easily be connected to your ETL tool with its last update timestamp column. A third way to get data out of Piwik AOM is by developing your own Piwik plugin and listening to the AOM.aomVisitAddedOrUpdated event, which is posted whenever an aom_visits record is added or updated.

  Integrating Piwik AOM’s data with your backend data in the business intelligence application of your choice allows you to evaluate the real performance of your online marketing campaigns when applying different conversion attribution models, conduct customer journey analyses, create sophisticated forecasts and whatever you can think of.

  AOM Use case

  A company that followed this approach, is FINANZCHECK.de, one of Germany’s leading loan comparison websites. At the eMetrics summit 2016 in Berlin, Germany, I gave a talk about FINANZCHECK’s architectural online marketing setup. Until recently, FINANZCHECK used Pentaho data integration to integrate data from Piwik, Piwik AOM and additional internal tools like its proprietary CRM software into Jaspersoft, its data warehouse an BI solution. The enriched data in Jaspersoft was not only used for reporting to various stakeholders but also for optimising all kinds of marketing activities (e.g. bids for individual keywords in Google AdWords) and proactive alerting. Not long ago, FINANZCHECK started an initiative to improve its setup even further – I’ll hopefully be able to cover this in a more detailed case study soon.

  Roadmap

  In the past, we had the chance to make great progress in developing this plugin by solving specific requirements of different companies who use Piwik AOM. During the next months, we plan to integrate more advertising platforms, reimplement Facebook Ads, improve the support of individual campaigns and work on the general plugin stability and performance.

  Before you install Piwik AOM

  Before installing Piwik AOM, you should know that its initial setup and even its maintenance can be quite complex. Piwik AOM will heavily modify your Piwik installation and you will only benefit from Piwik AOM if you are willing to invest quite some time into it.

  If you are not familiar with Piwik’s internals, PHP, MySQL, database backups, cronjobs, creating API accounts at the advertising platforms or adding parameters to your advertising campaign’s URLs, you should probably not install it on your own (at least not in your production environment).

  Piwik AOM has successfully been tested with up to 25k visitors a day for a period of more than two years, running on an AWS server with 4 GB RAM, once CPU and a separate AWS RDS MySQL database.

  Ideas and Support

  If you have ideas for new features or need support with your Piwik AOM installation or leveraging your marketing data’s potential in general, feel free to get in touch with the plugin’s co-author Daniel or me. You can find our contact details on the plugin’s website http://www.advanced-online-marketing.com.

  How to get the Piwik AOM plugin ?

  The Piwik AOM plugin is freely available through the Piwik marketplace at https://plugins.piwik.org/AOM

  Did you like this article ? If yes do not hesitate to share it or give your feedback about the topic you would like us to write about.

• ffmpeg codec error on audio file

  31 juillet 2013, par foosion

  I have some m4a files that will not play properly using the google music player app on my Android phone, although they play fine on most everything else. I thought the problem was the container and thought "ffmpeg -i bad.m4a -codec copy good.m4a" might help. However, when I run on the problem files, I get error messages. Running this command on non-problem files has not generated error messages.

  Please suggest ways to fix (other than re-encoding).

      [D:\temp\dl]ffmpeg -i "01 - The Day Begins.m4a" -codec copy day.m4a
  
  ffmpeg version N-55066-gc96b3ae Copyright (c) 2000-2013 the FFmpeg developers
  
    built on Jul 29 2013 18:05:45 with gcc 4.7.3 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-av
  
  isynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enab
  
  le-iconv --enable-libass --enable-libbluray --enable-libcaca --enable-libfreetyp
  
  e --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --ena
  
  ble-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-l
  
  ibopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libsp
  
  eex --enable-libtheora --enable-libtwolame --enable-libvo-aacenc --enable-libvo-
  
  amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --
  
  enable-libxvid --enable-zlib
  
    libavutil      52. 40.100 / 52. 40.100
  
    libavcodec     55. 19.100 / 55. 19.100
  
    libavformat    55. 12.102 / 55. 12.102
  
    libavdevice    55.  3.100 / 55.  3.100
  
    libavfilter     3. 82.100 /  3. 82.100
  
    libswscale      2.  4.100 /  2.  4.100
  
    libswresample   0. 17.103 /  0. 17.103
  
    libpostproc    52.  3.100 / 52.  3.100
  
  [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000002da300] stream 0, timescale not set
  
  Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '01 - The Day Begins.m4a':
  
    Metadata:
  
      major_brand     : m4a
  
      minor_version   : 0
  
      compatible_brands: M4A mp4isom
  
      creation_time   : 2003-07-06 20:27:46
  
      track           : 1
  
      genre           : Rock
  
      title           : The Day Begins
  
      artist          : Moody Blues
  
      album           : Days of Future Passed
  
      date            : 1967
  
    Duration: 00:05:50.83, start: 0.000000, bitrate: 166 kb/s
  
      Stream #0:0(eng): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 15
  
  9 kb/s
  
      Metadata:
  
        creation_time   : 2003-07-06 20:27:46
  
        handler_name    : Apple Sound Media Handler
  
      Stream #0:1(eng): Data: none (mp4s / 0x7334706D)
  
      Metadata:
  
        creation_time   : 2003-07-06 20:27:46
  
        handler_name    : Apple MPEG-4 Scene Media Handler
  
      Stream #0:2(eng): Data: none (mp4s / 0x7334706D)
  
      Metadata:
  
        creation_time   : 2003-07-06 20:27:46
  
        handler_name    : Apple MPEG-4 ODSM Media Handler
  
      Stream #0:3: Video: png, rgb24, 240x240 [SAR 2834:2834 DAR 1:1], 90k tbr, 90
  
  k tbn, 90k tbc
  
  [ipod @ 000000000031dd40] track 0: could not find tag, codec not currently suppo
  
  rted in container
  
  Output #0, ipod, to 'day.m4a':
  
    Metadata:
  
      major_brand     : m4a
  
      minor_version   : 0
  
      compatible_brands: M4A mp4isom
  
      date            : 1967
  
      track           : 1
  
      genre           : Rock
  
      title           : The Day Begins
  
      artist          : Moody Blues
  
      album           : Days of Future Passed
  
      encoder         : Lavf55.12.102
  
      Stream #0:0: Video: png, rgb24, 240x240 [SAR 2834:2834 DAR 1:1], q=2-31, 90k
  
   tbn, 90k tbc
  
      Stream #0:1(eng): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, 159 kb/s
  
  
  
      Metadata:
  
        creation_time   : 2003-07-06 20:27:46
  
        handler_name    : Apple Sound Media Handler
  
  Stream mapping:
  
    Stream #0:3 -> #0:0 (copy)
  
    Stream #0:0 -> #0:1 (copy)
  
  Could not write header for output file #0 (incorrect codec parameters ?): Error
  
  number -1 occurred

• Official RealVideo Specifications

  29 juillet 2010, par Multimedia Mike — General

  A little birdie tipped me off to a publicly-accessible URL on the Helix community site (does anyone actually use Helix ?) that contains a bunch of specifications for RealVideo 8 and 9. I have been sifting through the documents to see exactly what they contain as the different files seem to be higher revisions of the same documents. Here is the title, date, and version of each PDF document :

  • RNDecoderPerformanceARM.pdf : Decoder Performance on StrongARM and XScale ; May 12, 2003 ; Version 1.1
  • rv89_decoder_summary.pdf : RealVideo 8/9 Combo Decoder Summary ; October 23, 2002 ; Version 1.0
  • rv9_dec_external_spec_v14.pdf : RealVideo 9 External Specification ; November 7, 2003 ; Version 1.4
  • rv8_dec_external_spec_v20.pdf : RealVideo 8 External Specification ; September 19, 2002 ; Version 2.0
  • RV8DecoderExternalSpecificationv201.pdf : RealVideo 8 External Specification ; October 20, 2006 ; Version 2.01
  • RV8DecoderExternalSpecificationv202.pdf : RealVideo 8 External Specification ; April 23, 2007 ; Version 2.02
  • RV8DecoderExternalSpecificationv203.pdf : RealVideo 8 External Specification ; July 20, 2007 ; Version 2.03
  • RV8DecoderExternalSpecificationv21.pdf : RealVideo 8 External Specification ; September 11, 2007 ; Version 2.1
  • RV9DecoderExternalSpecificationv15.pdf ; RealVideo 9 External Specification ; January 26, 2002 ; Version 1.5
  • RV9DecoderExternalSpecificationv16.pdf ; RealVideo 9 External Specification ; August 17, 2005 ; Version 1.6
  • RV9DecoderExternalSpecificationv18.pdf ; RealVideo 9 External Specification ; September 11, 2007 ; Version 1.8

  Additionally, there is an Excel spreadsheet entitled realvideo-faq.xls that appears to contain some general tech support advice for using Real’s official code. There are also 3 ZIP archives which contain profiling information about the official source code (post processing and entropy decoding top the charts which is no big surprise).

  I guess the latest version of each document (the ones dated September 11, 2007) are worth mirroring. Unfortunately, those latest document versions use a terrible font.