By choosing to measure in-feed RSS advertising with oversold site metrics tools…it just make things even wilder. The reality is that there are serious technical limitations to consider when planning how to measure success at advertising to this target audience. Without proper planning however, marketers are left with a measurement gap of epic proportions.

First a quick primer to frame this classic situation. As a trained marketer, there are basically two different objectives of advertising and your ad creative typically can do one of the following well:

1. Branding. In other words, making an impression and/or changing perceptions. Often very important but very difficult to accurately measure. For this reason, measuring branding is more complex and almost always requires either a custom-study or syndicated (shared, usually generic) sample-based research. Right now, ad effectiveness services like Dynamic Logic, InsightExpress, Nielsen and ComScore are not yet working with RSS feed networks. This means that qualitative audience research requires a custom study that is considerate of the RSS user’s environment – this may incur additional costs.
2. Response. In the other corner is the quantitative measurement of tangible results such as sales, leads, impressions, clicks, time spent and the like. While it is much easier to technically measure the entire universe of such activities, in-feed RSS advertising success is a double-edge sword. Clicks (response) may be huge and the Clickthrough Rates great (relative to banners); with so much industry hand-wringing over declining CTR, clearly having a bounty of clicks is a good problem to have these days!

The Measurement Crater

For the purposes of this series, let’s say that you just want to measure response as the primary success metric for an RSS ad campaign. Unfortunately, if you or your client are depending on a JavaScript-tag based landing page tool to measure consumer response, you will likely experience something akin to this:

What happened? Wondering where did the clicks go? How many visits from suchnsuch.com’s RSS feed? Did they buy? Did they come back? Curious as to why you can’t determine what they did after they landed? As am I.

Newsflash: JavaScript tag-based Site Metrics have Limitations

Online marketers that are primarily interested in measuring response from an RSS campaign just found one. While many enterprise site metrics vendors brag about their simple, “just add our tag to your footer” implementation (Omniture, Google Analytics, Coremetrics)…if only it was that easy to get usable information.

The harsh technical reality is that JS tag-based systems require the browser to execute their special tag when the landing page is rendered. That is very different than server-side site metrics tools that track every access by definition. The main problem with relying exclusively on these tag-based approaches is that they cannot count accesses that originate from JS-disabled borwsers or altogether JS-incompatible applications. In other words, these popular site metrics tools essentially are blind to and ignore browsers and any traffic (including robots and spiders) that do not execute JS; I’m not going to get into the cookie deletion argument either.

Suffice to say with RSS advertising to Technfluentials, tracking non-JS accesses becomes your problem. To put it in marketing terms, here’s why:

1. Techfluentials use standalone desktop RSS Feed Readers/Aggregators (non-browser applications).
2. Techfluentials access the Web via mobile deivices in a browser environment that is even less likely to execute JS tags (my Treo 755p uses Palm Blazer 4.5, which offers the disable option).
3. Techfluentials ALSO deliberately/religiously disable JS in their browsers (not to mention deleting cookies).

In other words, your most valuable segment is missing from the numbers. What to do about it?

To Be Continued…

RSS Advertising Part III – Solutions to this Mess