SPThom
Nov 21st, 2005, 01:41 PM
Hey all. Just a little idea I've been fiddling with, and thought I'd share.
Instead of relying on server logs (ex. Libsyn) or third-party forwarders (ex. PodTrac) for tracking & collecting statistical information, why not implement an XML-based tracking system that we can include with our RSS feeds?
I ask, "why not", because I'm trying to lay the goundwork to do so.
Unlike commercial solutions and web-host solutions, podfair's tracking solution puts the control in your hands. Using the podfair XML Namespace in your XML feed, you will be able to specify one or more "tracker" URLs that can be located anywhere on the Internet. When listeners hit your feed using a podfair-enabled podcatcher, said podcatcher will transmit to the trackers about subscriptions, cancellations, downloads, "previews" (unsubscribed downloads), complete listens, partial listens, and more.
Think of the implications. Because this is based on an XML namespace (and trackers can be implemented via HTTP GET, POST, SOAP, etc.) it means tracking can go everywhere. Podcatchers, and even flash-based podcast players, can submit tracking information to any number of sites--ad managers, podcast directories, your own website or blog... The choices are endless.
And it provides statistics that make sense. It takes the guesswork out of which downloads are from legitimate subscribers, which are from casual listeners, and which are a result of the iTunes preview "bloat". You can even see how many subscribers listen through the entire runtime of episodes, and how many listen multiple times.
That information is from my site, podfair.com, which I've set up mostly as a home for this project. Also noteworthy is an abstract (http://www.podfair.com/forums/viewtopic.php?t=5) with examples of how the trackers could be added to feeds.
I'm not looking to sell you something, and I wouldn't even if this was anything more than an "idea", which is all it is at this point. But I would like the input of anyone with experience working with XML namespaces, SOAP, REST, programming Windows or OSX apps, etc. Or simply anyone interested in keeping podcasting as "open" as possible.
Instead of relying on server logs (ex. Libsyn) or third-party forwarders (ex. PodTrac) for tracking & collecting statistical information, why not implement an XML-based tracking system that we can include with our RSS feeds?
I ask, "why not", because I'm trying to lay the goundwork to do so.
Unlike commercial solutions and web-host solutions, podfair's tracking solution puts the control in your hands. Using the podfair XML Namespace in your XML feed, you will be able to specify one or more "tracker" URLs that can be located anywhere on the Internet. When listeners hit your feed using a podfair-enabled podcatcher, said podcatcher will transmit to the trackers about subscriptions, cancellations, downloads, "previews" (unsubscribed downloads), complete listens, partial listens, and more.
Think of the implications. Because this is based on an XML namespace (and trackers can be implemented via HTTP GET, POST, SOAP, etc.) it means tracking can go everywhere. Podcatchers, and even flash-based podcast players, can submit tracking information to any number of sites--ad managers, podcast directories, your own website or blog... The choices are endless.
And it provides statistics that make sense. It takes the guesswork out of which downloads are from legitimate subscribers, which are from casual listeners, and which are a result of the iTunes preview "bloat". You can even see how many subscribers listen through the entire runtime of episodes, and how many listen multiple times.
That information is from my site, podfair.com, which I've set up mostly as a home for this project. Also noteworthy is an abstract (http://www.podfair.com/forums/viewtopic.php?t=5) with examples of how the trackers could be added to feeds.
I'm not looking to sell you something, and I wouldn't even if this was anything more than an "idea", which is all it is at this point. But I would like the input of anyone with experience working with XML namespaces, SOAP, REST, programming Windows or OSX apps, etc. Or simply anyone interested in keeping podcasting as "open" as possible.