Recherche avancée

Sur d’autres sites (6417)

• How to measure the performance of a newsletter (or any email) with Matomo

  19 décembre 2017, par InnoCraft

  To be able to grow your business, it is crucial to track all your marketing efforts. This includes all newsletters and emails that you share with people outside of your business. Otherwise, you won’t be able to know which of your daily efforts are yielding results.

  Are you wondering if it is possible to track the performance of an emailing campaign in Matomo (Piwik) efficiently ? Would you like to know if it is technically easy ? No worries, here is a “How to” tutorial showing you how easily you can track an emailing in Matomo properly.

  Different tracking levels for different needs

  There are many things that you may be interested to track, for example :

  

  1. How many users opened your email
  2. How many users interacted with the links in your email
  3. How many users interacted on your website through your email

  Let’s have a look at each of these levels.

  Step 1 – Tracking email and newsletter openings in Matomo

  Tracking email openings requires to add an HTML code to your newsletter. It works through what we call a tracking pixel, a tiny image of 1×1 that is transparent so the user will not be able to see it.
  In order to install it, here is an example of what this code looks like :

  <img src="https://piwik.example.com/piwik.php?idsite=YOUR_PIWIK_WEBSITE_ID&rec=1&bots=1&url=https%3A%2F%2Fexample.com%2Femail-opened%2Fnewsletter_XYZ&action_name=Email%20opened&_rcn=internal%20email%20name&_rck=newsletter_XYZ" style="border:0;” alt="" />

  The Matomo tracking pixel explained

  The above URL is composed of the following URL parameters which are part of our Tracking API :

  • idsite : Corresponds to the ID of the website you would like to track.
  • rec : You need to have rec=1 in order for the request to be actually recorded.
  • bots : Set it to 1 to include all the connections made to this request, bots included.
  • url : corresponds to the URL you would like to display in Matomo (Piwik) every time the email is opened.
  • action_name : This is the page name you would like to be tracked when the email is opened.
  • _rcn : The name you would like to give to your campaign.
  • _rck : The keyword you may like to use in order to summarize the content of your newsletter.

  You may have noticed some special characters here such as “%20”, “%2F”. That’s because the URL is encoded. We strongly recommend you to do so in order for your tracking not to break. Many tools are available on the web in order to encode your URLs such as https://www.urlencoder.org/.

  If you would like to access the previous tracking code easily, keep in mind that you can always find the tracking code generator within the “Matomo admin panel → Tracking code” :

  

  You can find more information about it on our guide at : How do I track how many users open and read my newsletter emails (using a pixel / beacon) ?

  As a result, the information will be pushed as following for any user who opens your email :

  

  To not bias your regular page views on your website with newsletter openings, we recommend tracking newsletter openings into a new website.

  Tracking even more data : the user ID example

  You can go deeper in your URL tracking by inserting other parameters such as the user id if you have this information within your emailing database. One of the main benefit of tracking the User ID is to connect data across multiple devices and browsers for a given user.

  You only need to add the following parameter &uid=XXX where XXX equals the dynamic value of the user ID :

  

  Make sure that UID from your emailing provider is the same as the one used on your website in order for your data to be consistent.

  Important note : some email providers are loading email messages by default which results in an opening even if the user did not actually open the email.

  Step 2 – Measure the clicks within your emailing

  Tracking clicks within an email lets you know with which content readers interacted the most. We recommend tracking all links in all your emails as a campaign, whether it is a newsletter, a custom support email, an email invoice, etc. You might be surprised to see which of your emails lead to conversions and if they don’t, try to tweak those emails, so they might in the future.

  Tracking clicks This works thanks to URL campaign tracking. In order to perform this action, you will need to add Matomo (Piwik) URL parameters to all your existing link URLs :

  • Website URL : for example “www.your-website.com”.
  • Campaign name : for example “pk_campaign=emailing”. Represents the name you would like to give to your campaign.
  • Campaign keyword : for example “pk_keyword=name-of-your-article”. Represents the name you would like to give to your content.
  • Campaign source : for example “pk_source=newsletter”. Represents the name of the referrer.
  • Campaign medium : for example “pk_medium=email”. Represents the type of referrer you are using.
  • Campaign content : for example “pk_content=title”. Represents the type of content.

  You can find more information about campaign url tracking in our “Tracking marketing campaigns with Matomo” guide.

  Here is a sample showing you how you can differentiate some links in a newsletter, all pointing to the same URL :

  

  Once you have added these URL parameters to each of your link, Matomo (Piwik) will clearly indicate the referrer of this specific campaign when a user clicks on a link in the newsletter and visits your website.

  Important note : if you do not track your campaigns, it will result in a bad interpretation of your data within Matomo (Piwik) as you will get webmail services or direct entries as referrer instead of your newsletter campaign.

  Step 3 – Measure emailing performances on your website

  Thanks to Matomo (Piwik) URL campaign parameters, you can now clearly identify the traffic brought through your emailing. You can now specifically isolate users who come from emails by creating a segment :

  

  Once done, you can either have a look at each user specifically through the visitor log report or analyze it as a whole within the rest of the reports.

  You can even measure your return on investment directly if goals have been defined. In order to know more about how to track goals within Matomo (Piwik).

  Did you like this article ?

  If you enjoyed reading this article, do not hesitate to share it around you. Moreover, if there are any topics you would like to write us about in particular, just drop us an email and we will be more than happy to write about it.

  The post How to measure the performance of a newsletter (or any email) with Matomo appeared first on Analytics Platform - Matomo.

• Concatenating video using FFMPEG wrapper class [duplicate]

  21 décembre 2017, par alan samuel

  This question already has an answer here :

  • Parsed_concat_1 @ 02ad98e0 Failed to configure output pad on Parsed_concat_1 ffmpeg
    
    1 answer
    
  • how to use ffmpeg to apply 1:1 SAR before concat on large complex filter
    
    1 answer
    

  I am trying to concatenate video using NReco.VideoConverter wrapper class made for FFMPEG.

  I have three video files with the same frame rate and same frame size.

  Here is what I have done.

          string toconcatfile = @"C:\Users\Alan\Desktop\Black.mp4";
  
          string output1 = @"C:\Users\Alan\Desktop\output1.mp4";
  
          string output2 = @"C:\Users\Alan\Desktop\output2.mp4";
  
          string finaloutput = @"C:\Users\Alan\Desktop\finaloutput.mp4";

  All the three videos have a frame rate of 25 and Video frame size yet it fails when I add in toconcatfile to the final conversion method.

  It works when its just output1 and output2 meaning there must be a different setting in toconcatfile.

  Here is what I have tried.

          FFMpegConverter fFMpeg = new FFMpegConverter();
  
  
  
  
  
          //Slices first video
  
          ConvertSettings settings = new ConvertSettings
  
          {
  
              VideoFrameRate = 25,
  
              VideoFrameSize = FrameSize.hd480,
  
              MaxDuration = startcut,
  
              AudioSampleRate = 44100
  
  
  
          };
  
  
  
          //Slices second video
  
          ConvertSettings settings2 = new ConvertSettings
  
          {
  
              VideoFrameRate = 25,
  
              VideoFrameSize = FrameSize.hd480,
  
              Seek = endcut,
  
              AudioSampleRate = 44100
  
  
  
          };
  
          //Copies framerate and size from the previous video to the concatenation video
  
          ConvertSettings settings3 = new ConvertSettings
  
          {
  
              VideoFrameRate = 25,
  
              VideoFrameSize = FrameSize.hd480,
  
              MaxDuration = 4,
  
              AppendSilentAudioStream = true,
  
              AudioSampleRate = 44100
  
  
  
          };
  
  
  
  
  
    string newblack = @"C:\Users\Alan\Desktop\newblack.mp4";
  
  
  
          //Slice method called
  
          fFMpeg.ConvertMedia(pathtofile, Format.mp4, output1, Format.mp4, settings);
  
          fFMpeg.ConvertMedia(pathtofile, Format.mp4, output2, Format.mp4, settings2);
  
          fFMpeg.ConvertMedia(toconcatfile, Format.mp4, newblack, Format.mp4, settings3);
  
  
  
          String[] inputfiles = new String[2];
  
          inputfiles[0] = output1;
  
          inputfiles[1] = newblack;
  
          //inputfiles[1] = output2;
  
  
  
  
  
          ConcatSettings concatSettings = new ConcatSettings
  
          {
  
              //CustomOutputArgs = output1+" "+ toconcatfile+ " "+output2+ " -filter_complex \"[0:v:0][0:a:0][1:v:0][1:a:0][2:v:0][2:a:0]concat=n=3:v=1:a=1[outv][outa]\" -map \"[outv]\" - map \"[outa]\""
  
          };
  
  
  
          fFMpeg.ConcatMedia(inputfiles, finaloutput, Format.mp4, concatSettings);

  Can anyone help ?

  Edit : I get the exception message - "Invalid argument (exit code : 1)",

  Here is the output log of FFMPEG

          FFMPEG LOG ITEM - ffmpeg version 3.2.2 Copyright (c) 2000-2016 the 
  
              FFmpeg developers
  
  FFMPEG LOG ITEM -   built with gcc 5.4.0 (GCC)
  
  FFMPEG LOG ITEM -   configuration: --enable-gpl --enable-version3 --enable-
  
  
  
  dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --
  
  
  
  enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
  
  FFMPEG LOG ITEM -   libavutil      55. 34.100 / 55. 34.100
  
  FFMPEG LOG ITEM -   libavcodec     57. 64.101 / 57. 64.101
  
  FFMPEG LOG ITEM -   libavformat    57. 56.100 / 57. 56.100
  
  FFMPEG LOG ITEM -   libavdevice    57.  1.100 / 57.  1.100
  
  FFMPEG LOG ITEM -   libavfilter     6. 65.100 /  6. 65.100
  
  FFMPEG LOG ITEM -   libswscale      4.  2.100 /  4.  2.100
  
  FFMPEG LOG ITEM -   libswresample   2.  3.100 /  2.  3.100
  
  FFMPEG LOG ITEM -   libpostproc    54.  1.100 / 54.  1.100
  
  FFMPEG LOG ITEM - Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\Users\Alan\Desktop\output1.mp4':
  
  FFMPEG LOG ITEM -   Metadata:
  
  FFMPEG LOG ITEM -     major_brand     : isom
  
  FFMPEG LOG ITEM -     minor_version   : 512
  
  FFMPEG LOG ITEM -     compatible_brands: isomiso2avc1mp41
  
  FFMPEG LOG ITEM -     encoder         : Lavf57.56.100
  
  FFMPEG LOG ITEM -   Duration: 00:00:30.02, start: 0.000000, bitrate: 543 kb/s
  
  FFMPEG LOG ITEM -     Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 852x480 [SAR 3893:2872 DAR 276403:114880], 407 kb/s, SAR 12800:9443 DAR 320:133, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
  FFMPEG LOG ITEM -     Metadata:
  
  FFMPEG LOG ITEM -       handler_name    : VideoHandler
  
  FFMPEG LOG ITEM -     Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 129 kb/s (default)
  
  FFMPEG LOG ITEM -     Metadata:
  
  FFMPEG LOG ITEM -       handler_name    : SoundHandler
  
  FFMPEG LOG ITEM - Input #1, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\Users\Alan\Desktop\newblack.mp4':
  
  FFMPEG LOG ITEM -   Metadata:
  
  FFMPEG LOG ITEM -     major_brand     : isom
  
  FFMPEG LOG ITEM -     minor_version   : 512
  
  FFMPEG LOG ITEM -     compatible_brands: isomiso2avc1mp41
  
  FFMPEG LOG ITEM -     encoder         : Lavf57.56.100
  
  FFMPEG LOG ITEM -   Duration: 00:00:04.02, start: 0.000000, bitrate: 19 kb/s
  
  FFMPEG LOG ITEM -     Stream #1:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 852x480 [SAR 160:213 DAR 4:3], 7 kb/s, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
  FFMPEG LOG ITEM -     Metadata:
  
  FFMPEG LOG ITEM -       handler_name    : VideoHandler
  
  FFMPEG LOG ITEM -     Stream #1:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 2 kb/s (default)
  
  FFMPEG LOG ITEM -     Metadata:
  
  FFMPEG LOG ITEM -       handler_name    : SoundHandler
  
  FFMPEG LOG ITEM - Input #2, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\Users\Alan\Desktop\output2.mp4':
  
  FFMPEG LOG ITEM -   Metadata:
  
  FFMPEG LOG ITEM -     major_brand     : isom
  
  FFMPEG LOG ITEM -     minor_version   : 512
  
  FFMPEG LOG ITEM -     compatible_brands: isomiso2avc1mp41
  
  FFMPEG LOG ITEM -     encoder         : Lavf57.56.100
  
  FFMPEG LOG ITEM -   Duration: 00:01:34.22, start: 0.000000, bitrate: 1058 kb/s
  
  FFMPEG LOG ITEM -     Stream #2:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 852x480 [SAR 3893:2872 DAR 276403:114880], 923 kb/s, SAR 12800:9443 DAR 320:133, 25 fps, 25 tbr, 12800 tbn, 50 tbc (default)
  
  FFMPEG LOG ITEM -     Metadata:
  
  Exception thrown: 'NReco.VideoConverter.FFMpegException' in NReco.VideoConverter.dll
  
  FFMPEG LOG ITEM -       handler_name    : VideoHandler
  
  FFMPEG LOG ITEM -     Stream #2:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
  FFMPEG LOG ITEM -     Metadata:
  
  FFMPEG LOG ITEM -       handler_name    : SoundHandler
  
  FFMPEG LOG ITEM - [Parsed_concat_0 @ 04ded5e0] Input link in1:v0 parameters (size 852x480, SAR 160:213) do not match the corresponding output link in0:v0 parameters (852x480, SAR 12800:9443)
  
  FFMPEG LOG ITEM - [Parsed_concat_0 @ 04ded5e0] Failed to configure output pad on Parsed_concat_0
  
  FFMPEG LOG ITEM - Error configuring complex filters.
  
  FFMPEG LOG ITEM - Invalid argument

• How to measure the performance of a newsletter (or any email) with Piwik

  19 décembre 2017, par InnoCraft — Community

  To be able to grow your business, it is crucial to track all your marketing efforts. This includes all newsletters and emails that you share with people outside of your business. Otherwise, you won’t be able to know which of your daily efforts are yielding results.

  Are you wondering if it is possible to track the performance of an emailing campaign in Piwik efficiently ? Would you like to know if it is technically easy ? No worries, here is a “How to” tutorial showing you how easily you can track an emailing in Piwik properly.

  Different tracking levels for different needs

  There are many things that you may be interested to track, for example :

  

  1. How many users opened your email
  2. How many users interacted with the links in your email
  3. How many users interacted on your website through your email

  Let’s have a look at each of these levels.

  Step 1 – Tracking email and newsletter openings in Piwik

  Tracking email openings requires to add an HTML code to your newsletter. It works through what we call a tracking pixel, a tiny image of 1×1 that is transparent so the user will not be able to see it.
  In order to install it, here is an example of what this code looks like :

  <img src="https://piwik.example.com/piwik.php?idsite=YOUR_PIWIK_WEBSITE_ID&rec=1&bots=1&url=https%3A%2F%2Fexample.com%2Femail-opened%2Fnewsletter_XYZ&action_name=Email%20opened&_rcn=internal%20email%20name&_rck=newsletter_XYZ" style="border:0;” alt="" />

  The Piwik tracking pixel explained

  The above URL is composed of the following URL parameters which are part of our Tracking API :

  • idsite : Corresponds to the ID of the website you would like to track.
  • rec : You need to have rec=1 in order for the request to be actually recorded.
  • bots : Set it to 1 to include all the connections made to this request, bots included.
  • url : corresponds to the URL you would like to display in Piwik every time the email is opened.
  • action_name : This is the page name you would like to be tracked when the email is opened.
  • _rcn : The name you would like to give to your campaign.
  • _rck : The keyword you may like to use in order to summarize the content of your newsletter.

  You may have noticed some special characters here such as “%20”, “%2F”. That’s because the URL is encoded. We strongly recommend you to do so in order for your tracking not to break. Many tools are available on the web in order to encode your URLs such as https://www.urlencoder.org/.

  If you would like to access the previous tracking code easily, keep in mind that you can always find the tracking code generator within the “Piwik admin panel → Tracking code” :

  

  You can find more information about it on our guide at : How do I track how many users open and read my newsletter emails (using a pixel / beacon) ?

  As a result, the information will be pushed as following for any user who opens your email :

  

  To not bias your regular page views on your website with newsletter openings, we recommend tracking newsletter openings into a new website.

  Tracking even more data : the user ID example

  You can go deeper in your URL tracking by inserting other parameters such as the user id if you have this information within your emailing database. One of the main benefit of tracking the User ID is to connect data across multiple devices and browsers for a given user.

  You only need to add the following parameter &uid=XXX where XXX equals the dynamic value of the user ID :

  

  Make sure that UID from your emailing provider is the same as the one used on your website in order for your data to be consistent.

  Important note : some email providers are loading email messages by default which results in an opening even if the user did not actually open the email.

  Step 2 – Measure the clicks within your emailing

  Tracking clicks within an email lets you know with which content readers interacted the most. We recommend tracking all links in all your emails as a campaign, whether it is a newsletter, a custom support email, an email invoice, etc. You might be surprised to see which of your emails lead to conversions and if they don’t, try to tweak those emails, so they might in the future.

  Tracking clicks This works thanks to URL campaign tracking. In order to perform this action, you will need to add Piwik URL parameters to all your existing link URLs :

  • Website URL : for example “www.your-website.com”.
  • Campaign name : for example “pk_campaign=emailing”. Represents the name you would like to give to your campaign.
  • Campaign keyword : for example “pk_keyword=name-of-your-article”. Represents the name you would like to give to your content.
  • Campaign source : for example “pk_source=newsletter”. Represents the name of the referrer.
  • Campaign medium : for example “pk_medium=email”. Represents the type of referrer you are using.
  • Campaign content : for example “pk_content=title”. Represents the type of content.

  You can find more information about campaign url tracking in our “Tracking marketing campaigns with Piwik” guide.

  Here is a sample showing you how you can differentiate some links in a newsletter, all pointing to the same URL :

  

  Once you have added these URL parameters to each of your link, Piwik will clearly indicate the referrer of this specific campaign when a user clicks on a link in the newsletter and visits your website.

  Important note : if you do not track your campaigns, it will result in a bad interpretation of your data within Piwik as you will get webmail services or direct entries as referrer instead of your newsletter campaign.

  Step 3 – Measure emailing performances on your website

  Thanks to Piwik URL campaign parameters, you can now clearly identify the traffic brought through your emailing. You can now specifically isolate users who come from emails by creating a segment :

  

  Once done, you can either have a look at each user specifically through the visitor log report or analyze it as a whole within the rest of the reports.

  You can even measure your return on investment directly if goals have been defined. In order to know more about how to track goals within Piwik.

  Did you like this article ?

  If you enjoyed reading this article, do not hesitate to share it around you. Moreover, if there are any topics you would like to write us about in particular, just drop us an email and we will be more than happy to write about it.