Recherche avancée

Sur d’autres sites (9650)

• How to track Google AdWords campaigns with Matomo

  19 décembre 2017, par InnoCraft

  In 2016, Google AdWords was the most popular ad service on earth. As a result, it may be your first source for ad spending. Are you interested in knowing whether you are making a profit out of it ? Would you like to know how to track users coming from AdWords with Matomo (Piwik) efficiently ? This is what this article is about.

  

  What you need to know about Google AdWords

  By default, each ad you create in Google AdWords is not tracked. Even worse than that, every click on your ad is identified in Matomo (Piwik) as an organic result coming from Google with the following value : “Keyword not defined”.

  To make it simple, if you do not track your AdWords campaigns both your paid and organic traffic will be biased within your Matomo (Piwik) account. It will be impossible for you to measure your return on investment and it means that you are throwing your money down the drain.

  In order to avoid this, we will show you how to track Google AdWords traffic into Matomo (Piwik).

  How to track paid Google AdWords campaigns into Matomo

  If you want to analyze Google AdWords campaigns within Matomo (Piwik) properly, you need to add additional tracking parameters to the final URL of each of your ads.

  We recommend using the following tool to add the needed additional tracking parameters : https://matomo.org/docs/tracking-campaigns-url-builder/

  You will then be able to push additional data to Matomo (Piwik) such as :

  • pk_campaign : the name of your ad campaign
  • pk_kwd : the keyword associated to this campaign
  • pk_source : the source of your campaign
  • pk_medium : the type of source, in our case either cpc, cpm, cpa
  • pk_content : the content of your ad

  If your campaign URL looks like this : https://your-website.com/, your campaign URL will then look like this after adding the campaign parameters :

  https://your-website.com/?pk_campaign=Name-Of-Your-Campaign&pk_kwd=Your-Keyword&pk_source=google&pk_medium=cpc&pk_content=My-Ad-Headline

  As each ad URL can be fired by different keywords and can correspond to different campaigns or headlines, you will need to customize the campaign parameters for each URL.

  Customizing all of your URLs individually would take you a lot of time under circumstances. That’s why you should know, that each URL parameter can be filled automatically in AdWords with a feature called “Tracking template”.

  Simplifying the campaign URL parameters with tracking templates

  You can define tracking templates either at the account, campaign or ad group level. For example, by using a tracking template at the account level, all your campaigns will have the same landing page with the URL parameters you defined in the tracking template. By defining it at the campaign level, it means that all your ad groups within the campaign will have the same landing page and so on and so forth. Any tracking template defined in a campaign, will overwrite a tracking template defined at the account level.

  Tracking template at the account level

  To edit the template at the account level, you need to click on “Settings”, then click on the “Account” settings tab and define your tracking template pattern. For example :

  https://your-website.com/?url={lpurl}&pk_campaign=AdWords&pk_kwd=Your-Keyword&pk_source=google&pk_medium=cpc&pk_content=My-Ad-Headline

  

  This will apply to all your URLs within your account. So it is only useful if your website domain is the same across all your ads. The URL parameter is compulsory here.

  It can be limiting to have a static value for “pk_campaign” and “pk_kwd” so Google allows you to use dynamic insertion, such as follows :

  https://your-landing-page.com/?url={lpurl}&pk_campaign={campaignid}&pk_kwd={keyword}&pk_source=google&pk_medium=cpc&pk_content={creative}

  The “keyword” means that the data is automatically replaced with the keyword which fired the ad within your account.

  Visit the following page if you want to know more about the different dynamic tags that AdWords supports : https://support.google.com/adwords/answer/6305348#urlinsertion

  Tracking template at the campaign level

  If you wish to define a tracking template at the campaign level, you will find this option within the “Campaign” settings under the campaign URL options :

  

  Tracking template at the Ad Group level

  You can also set it at the Ad Group level within the “Ad Group” settings :

  

  As Google mentions : “If you set up URL options at the campaign level, ad group level, or ad level, those settings will override the account-level options“.

  Now that your URLs are properly configured, you will be able to analyze AdWords traffic performances within Matomo (Piwik) once a click is coming from those sources.

  

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

• How to track Google AdWords campaigns with Piwik

  19 décembre 2017, par InnoCraft

  In 2016, Google AdWords was the most popular ad service on earth. As a result, it may be your first source for ad spending. Are you interested in knowing whether you are making a profit out of it ? Would you like to know how to track users coming from AdWords with Piwik efficiently ? This is what this article is about.

  

  What you need to know about Google AdWords

  By default, each ad you create in Google AdWords is not tracked. Even worse than that, every click on your ad is identified in Piwik as an organic result coming from Google with the following value : “Keyword not defined”.

  To make it simple, if you do not track your AdWords campaigns both your paid and organic traffic will be biased within your Piwik account. It will be impossible for you to measure your return on investment and it means that you are throwing your money down the drain.

  In order to avoid this, we will show you how to track Google AdWords traffic into Piwik.

  How to track paid Google AdWords campaigns into Piwik

  If you want to analyze Google AdWords campaigns within Piwik properly, you need to add additional tracking parameters to the final URL of each of your ads.

  We recommend using the following tool to add the needed additional tracking parameters : https://piwik.org/docs/tracking-campaigns-url-builder/

  You will then be able to push additional data to Piwik such as :

  • pk_campaign : the name of your ad campaign
  • pk_kwd : the keyword associated to this campaign
  • pk_source : the source of your campaign
  • pk_medium : the type of source, in our case either cpc, cpm, cpa
  • pk_content : the content of your ad

  If your campaign URL looks like this : https://your-website.com/, your campaign URL will then look like this after adding the campaign parameters :

  https://your-website.com/?pk_campaign=Name-Of-Your-Campaign&pk_kwd=Your-Keyword&pk_source=google&pk_medium=cpc&pk_content=My-Ad-Headline

  As each ad URL can be fired by different keywords and can correspond to different campaigns or headlines, you will need to customize the campaign parameters for each URL.

  Customizing all of your URLs individually would take you a lot of time under circumstances. That’s why you should know, that each URL parameter can be filled automatically in AdWords with a feature called “Tracking template”.

  Simplifying the campaign URL parameters with tracking templates

  You can define tracking templates either at the account, campaign or ad group level. For example, by using a tracking template at the account level, all your campaigns will have the same landing page with the URL parameters you defined in the tracking template. By defining it at the campaign level, it means that all your ad groups within the campaign will have the same landing page and so on and so forth. Any tracking template defined in a campaign, will overwrite a tracking template defined at the account level.

  Tracking template at the account level

  To edit the template at the account level, you need to click on “Settings”, then click on the “Account” settings tab and define your tracking template pattern. For example :

  https://your-website.com/?url={lpurl}&pk_campaign=AdWords&pk_kwd=Your-Keyword&pk_source=google&pk_medium=cpc&pk_content=My-Ad-Headline

  

  This will apply to all your URLs within your account. So it is only useful if your website domain is the same across all your ads. The URL parameter is compulsory here.

  It can be limiting to have a static value for “pk_campaign” and “pk_kwd” so Google allows you to use dynamic insertion, such as follows :

  https://your-landing-page.com/?url={lpurl}&pk_campaign={campaignid}&pk_kwd={keyword}&pk_source=google&pk_medium=cpc&pk_content={creative}

  The “keyword” means that the data is automatically replaced with the keyword which fired the ad within your account.

  Visit the following page if you want to know more about the different dynamic tags that AdWords supports : https://support.google.com/adwords/answer/6305348#urlinsertion

  Tracking template at the campaign level

  If you wish to define a tracking template at the campaign level, you will find this option within the “Campaign” settings under the campaign URL options :

  

  Tracking template at the Ad Group level

  You can also set it at the Ad Group level within the “Ad Group” settings :

  

  As Google mentions : “If you set up URL options at the campaign level, ad group level, or ad level, those settings will override the account-level options“.

  Now that your URLs are properly configured, you will be able to analyze AdWords traffic performances within Piwik once a click is coming from those sources.

  

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

• ffmpeg h264 interesting bright video fail ?

  23 novembre 2019, par Max Paython

  I am trying streaming with ffmpeg using the information I found here.

  • Server

    ffmpeg -f dshow -i video="john":audio="doe" -vcodec libx264
    
    -preset ultrafast -tune zerolatency -acodec aac -f mpegts udp://localhost:1234

  • Client

    ffmpeg -i udp://localhost:1234?listen test.mp4

  The client will actually live stream the video, but for testing purposes I am writing the output to a file for now.

  Here comes the interesting part. I began the stream(video and audio) in a dark room, everything is fine. I turn on the room’s lights and the client cries with many errors. I later checked the output, it is very corrupted indeed on the light turned-on parts. What could be the reason behind this ? I am posting the errors here if it could be of assistance.

  Some of the errors :

  udp://localhost:1234?listen: corrupt decoded frame in stream 0trate= 845.6kbits/s dup=1250 drop=0 speed=1.08x
  
      Last message repeated 1 times
  
  [h264 @ 0000026c4af69400] Invalid NAL unit 1, skipping.7.61 bitrate= 864.7kbits/s dup=1441 drop=0 speed=1.07x
  
  [h264 @ 0000026c4af69400] Invalid level prefix
  
  [h264 @ 0000026c4af69400] error while decoding MB 18 8
  
  [h264 @ 0000026c4af69400] concealing 911 DC, 911 AC, 911 MV errors in P frame
  
  [h264 @ 0000026c4af4b780] Invalid NAL unit 1, skipping.
  
  [h264 @ 0000026c4af4b780] negative number of zero coeffs at 10 14
  
  [h264 @ 0000026c4af4b780] error while decoding MB 10 14
  
  [h264 @ 0000026c4af4b780] concealing 679 DC, 679 AC, 679 MV errors in P frame
  
  udp://localhost:1234?listen: corrupt decoded frame in stream 0
  
      Last message repeated 1 times
  
  [h264 @ 0000026c4ba1e1c0] Invalid NAL unit 1, skipping.8.21 bitrate= 858.0kbits/s dup=1460 drop=0 speed=1.07x
  
  [h264 @ 0000026c4ba1e1c0] out of range intra chroma pred mode
  
  [h264 @ 0000026c4ba1e1c0] error while decoding MB 34 18
  
  [h264 @ 0000026c4ba1e1c0] concealing 495 DC, 495 AC, 495 MV errors in P frame
  
  [h264 @ 0000026c4bb16840] top block unavailable for requested intra mode
  
  [h264 @ 0000026c4bb16840] error while decoding MB 10 0
  
  [h264 @ 0000026c4bb16840] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  udp://localhost:1234?listen: corrupt decoded frame in stream 0
  
  [h264 @ 0000026c4bb16cc0] Invalid NAL unit 0, skipping.8.58 bitrate= 853.9kbits/s dup=1463 drop=0 speed=1.06x
  
  [h264 @ 0000026c4bb16cc0] corrupted macroblock 16 28 (total_coeff=-1)
  
  [h264 @ 0000026c4bb16cc0] error while decoding MB 16 28
  
  [h264 @ 0000026c4bb16cc0] concealing 113 DC, 113 AC, 113 MV errors in P frame
  
  [h264 @ 0000026c4bb17140] cbp too large (84) at 12 0
  
  [h264 @ 0000026c4bb17140] error while decoding MB 12 0
  
  [h264 @ 0000026c4bb17140] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  [mpegts @ 0000026c4aeb8d80] PES packet size mismatch

  Edit : As suggestion, I added these parameters to the server.

  -b:v 1M -bufsize 2M

  Now the errors are mostly gone. Except one time where it seemed like it occured just as I was turning off the lights, although I could not reproduce it after trying 4-5 times.

  Errors :

  [h264 @ 000002646f0d2f80] cbp too large (118) at 23 1422.25 bitrate= 659.5kbits/s dup=368 drop=0 speed=1.33x
  
  [h264 @ 000002646f0d2f80] error while decoding MB 23 14
  
  [mpegts @ 000002646e578d80] PES packet size mismatch
  
  [h264 @ 000002646f0d2f80] concealing 666 DC, 666 AC, 666 MV errors in P frame
  
  [h264 @ 000002646f0d0f80] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  [aac @ 000002646e64d640] Number of bands (59) exceeds limit (43).
  
  Error while decoding stream #0:1: Invalid data found when processing input
  
  [aac @ 000002646e64d640] Multiple frames in a packet.
  
  [aac @ 000002646e64d640] Reserved bit set.
  
  [aac @ 000002646e64d640] Number of bands (31) exceeds limit (29).
  
  Error while decoding stream #0:1: Invalid data found when processing input
  
  [h264 @ 000002646e5e11c0] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  udp://localhost:1234?listen: corrupt decoded frame in stream 0trate= 633.1kbits/s dup=368 drop=0 speed=1.35x
  
      Last message repeated 2 times

  The errors decreased because I increased the bitrate ? (I don’t know the default bitrate by the way). Bright decoding fails because it carries more information, data ? (same in raw video, but maybe file is heavier encoded bright frames)