A bitly hash that identifies a unique URL.
To understand how this target works, consider a case where two independent users generate a link to a page; let's use datasift.com as our example page. The two users each receive a unique hash. These unique hashes enable bitly to track statistics for each user's link independently. The links both lead to datasift.com ultimately, but they are different.
To keep track of the overall statistics for links to that page, bitly generates one extra hash, which encompasses everyone's bitly links to the page. You can filter on this hash using bitly.url_hash.
|Use this target:||For this purpose:|
|bitly.share.hash||Filter on one particular user's link to datasift.com (and ignore everyone else's links to datasift.com.|
|bitly.url_hash||Filter for all bitly links to datasift.com.|
An example of a hash is R7lbKz. Hashes appear directly in the URLs that bitly generates. Click on this one now to try it: http://bit.ly/R7lbKz.
Consider this use case: when a user visits the bitly website and requests a shortened link, bitly returns a link that includes the hash that you can filter on in bitly.share.hash. In this example, suppose that bitly.share.hash is R7lbKz.
Bitly does not give any information about bitly.hash. So, we need a way to find the bitly.url_hash corresponding to a known bitly.share_hash. This is a one-to-many relationship.
Fortunately, there's an easy way to use DataSift to find a bitly.url_hash if you know the bitly.share.hash. First, filter for clicks on a bitly.share.hash. We'll use our example, which resolves to datasift.com:
bitly.share.hash == "R7lbKz"
As soon as you receive one interaction, stop your stream and examine the JSON output.
In there, you'll find an element that tells you the value of bitly.url_hash. Suppose it's 123456.
Then you can filter against bitly.url_hash to find all the clicks to the destination, not just clicks on the link identified by bitly.share_hash:
bitly.url_hash == "123456"
Remember, bitly.share.hash tells you when anyone clicks on a link generated by bitly for a particular user to a particular page. The user and the page are not specified but they are fixed. In other words, it is user-specific information.
In contrast, bitly.url_hash contains page-specific information. It tells you when anyone clicks on a link generated by any user to that page. The page, of course, is still fixed but the user is no longer fixed; DataSift includes all of the bitly links that go to the page, no matter who generated them.
Target service: Bitly
Always exists: No