Can I make a suggestion for a future release please. I personally think it would be ace, if you could view the stats of the bit.ly url in umbraco without going off to the bit.ly site.
Maybe you could have a dashboard on the content section that lists all the generated bit.ly urls (traverse nodes to find the property) and then generate a graph for each or something.
Not really thought through the exact details how it should work, but if you could make it happen you would definately have a killer package !
I have a technically related question to bit.ly. Since the I'm directed to bit.ly when I click on a link and then redirected to the target page, is it right that the target page can't track from where I'm actually coming? The referrer would be bit.ly right?
I was going to incorporate some stats (or at least the basic info) directly into the data-type property editor (so that you can see it per content page, rather than having a separate dashboard section) - but I was eager to get this version "out there", rather than sit on it for a couple of weeks.
When I next get some "free" time, I'll take a look at the Bit.ly API, see what juicy data we can pull back! (Bit.ly API documentation)
@Timsn, I believe Bit.ly does forward the referrer headers on to the target URL. (Don't quote me on that ... but if I find the link where I read it, I'll post it here)
Hiya Lee, I understand getting something out the door versus all the bells & whistles, but I definately think its worth considering however you decide to implement it.
Suggestion - Stat Graphs
Hiya Lee good work with this bit.ly datatype.
Can I make a suggestion for a future release please.
I personally think it would be ace, if you could view the stats of the bit.ly url in umbraco without going off to the bit.ly site.
Maybe you could have a dashboard on the content section that lists all the generated bit.ly urls (traverse nodes to find the property) and then generate a graph for each or something.
Not really thought through the exact details how it should work, but if you could make it happen you would definately have a killer package !
Warren :)
That would be indeed very nice.
I have a technically related question to bit.ly. Since the I'm directed to bit.ly when I click on a link and then redirected to the target page, is it right that the target page can't track from where I'm actually coming? The referrer would be bit.ly right?
Hi Warren, thanks for the feedback!
I was going to incorporate some stats (or at least the basic info) directly into the data-type property editor (so that you can see it per content page, rather than having a separate dashboard section) - but I was eager to get this version "out there", rather than sit on it for a couple of weeks.
When I next get some "free" time, I'll take a look at the Bit.ly API, see what juicy data we can pull back! (Bit.ly API documentation)
Cheers, Lee.
@Timsn, I believe Bit.ly does forward the referrer headers on to the target URL. (Don't quote me on that ... but if I find the link where I read it, I'll post it here)
Hiya Lee,
I understand getting something out the door versus all the bells & whistles, but I definately think its worth considering however you decide to implement it.
Warren :)
Following up on my little mid-week lobbying statement (here is the tweet) ... you showed your love ... so I've added stats support.
The stats is based on the example provided by the Bit.ly stats module, using the Javascript Client API.
http://bit.ly/app/demos/statsTable.html
Enjoy!
- Lee
is working on a reply...