Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/2/d178525413/htdocs/electronic/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/2/d178525413/htdocs/electronic/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/2/d178525413/htdocs/electronic/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/2/d178525413/htdocs/electronic/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/2/d178525413/htdocs/electronic/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/2/d178525413/htdocs/electronic/wp-includes/http.php on line 61
Measuring blogs: The New, the Best, the Odd, the Linked and the Forgotten < life under electronic conditions
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/kses.php on line 1002

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/kses.php on line 1003

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/functions.php on line 55

Measuring blogs: The New, the Best, the Odd, the Linked and the Forgotten


Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/link-template.php on line 107

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/link-template.php on line 132

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/link-template.php on line 107

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/2/d178525413/htdocs/electronic/wp-includes/link-template.php on line 132

Social media measurement should take into account that there are different types of blog posts with different readers, expectations and usage patterns.

In seminars I often employ a little number play and compare how many people are reading e.g. a German food magazine and how many people are reading a blog on the same topic. More often than not the blog wins.

But then again this comparison is fundamentally flawed because both media - the magazine and the blog - are consumed in very different ways. Magazines come in issues. This sounds simple, but has serious consequences for measuring reach. Here, only the last issue counts. It does not count how often older issues are read.

Blogs are different. First, there are no issues but only atoms - single entries, which are updated in a more or less regular way. But when counting the reach or success of a blog, there are at least five types of blog posts that are important to measure:

  1. The New: When measuring the visitors or page impressions of a blog, new articles always appear on the first places. They are shown on the top of the blog’s title page and are feed through the RSS readers to your subscribers. But they lose impace, the longer the intervall you are measuring. When measuring a single day’s success, blog posts written on this day will almost certainly have the most visitors. But if you’re analysing a whole month, it can look very different.
  2. The Best: Every blog has posts that have something special to them, may it be a very brilliant formulation, a great heading or summing up a long discussion. Those posts also rank very high because they are linked by other blogs or appear at the top in search requests.
  3. The Odd: Every day, blog posts get hits, that are old and do not belong to your top posts. This is because someone did a search and Google put your post very high because it appears to be very relevant to the terms.
  4. The Linked: Sometimes another blogger, maybe a prominent one, is linking to an oder entry of your blog. Suddenly there is a lot of traffic to a post that is already a few months old.
  5. The Forgotten: This is the rest of your blog. All those blog posts that rest hidden in the depths of your blog’s archive. But they can be rediscovered and join the categories of the odd or the linked.

Social Media Measurement should reflect those different types of blog posts in their methodology because it may be the case that they represent different blog readers, expectations and usage patterns. This could also be an important typology for optimizing social media marketing campains and for targeting advertising campaigns on blogs. Do you need to focus on the new, the best, the odd or the linked?

Share this post:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • Furl
  • Ma.gnolia
  • MisterWong
  • NewsVine
  • TwitThis
  • Yigg
  • Pownce
  • Reddit
  • Slashdot
  • StumbleUpon
  • Wikio
  • LinkedIn
  • Spurl