Know Where Your Visitors Have Been: beencounter
| « Back to all posts | Share, Save or Email |
Tel Aviv (Israel) based beencounter is a service unlike any you have ever seen we suspect. By “hacking” your web visitor’s browser history files, beencounter provides interesting insights into your audience. An API makes this information actionable for personalization and targeting efforts.
What does beencounter do?
beencounter (the little “b” is their branding, not a typo) is, in their own words, a “Behavioral Targeting and Behavioral Tracking” service. Built around a single line Javascript tag, beencounter basically gives you access to your site visitor’s browser history files. And while they cannot tell you all the places your visitors have been, by providing the service with a list of URLs, beencounter can tell you whether your site visitors have been to those URLs sometime in the past.
Here you can see the results for Web Analytics Demystified over a few weeks:
What this report tells me is that during the timeframe I selected about 18% of my visitors had also been to the main Google Analytics page, about 6% had been to Omniture’s home page, and about 4% had passed through blogger Avinash Kaushik’s blog main page.
Pretty nifty, huh?
How does beencounter work?
beencounter is doing something surprisingly simple: they are taking advantage of a known hack of the browser Document Object Model (DOM) that identifies URLs that have been previously visited. The way this manifests normally is showing visited links on a page as a different color than unvisited links. You can also see this information if you open your browser history.
All you have to do is provide beencounter a list of URLs that you want to watch out for and they do the rest. What’s more is they provide an easy-to-use API so that you can actually query the visitor’s browser in real-time and see if they have been to a site or group of sites:
Once you’ve added your sites, beencounter will provide a Site ID, and then just a little bit of Javascript is all you need (and the “is good but we are better” example text comes from beencounter, not us):
Sweet, huh?
What makes beencounter different?
I don’t follow behavioral targeting solutions very closely, but I’ve never seen a solution that provides this much programatic access to insights into visitor behavior across the Internet. When I saw the application I immediately thought of a dozen cool things I could do with only a tiny bit of programming.
Don’t get me wrong: beencounter has some particular challenges … specifically the fact that many people who learn about the solution are likely to think beencounter is incredibly invasive and crosses the line regarding consumer privacy. For example, I am watching for people going to ZAAZ and the WAA, but I could just as easily try and determine who in my audience spends time at Playboy.com or one of the many gambling sites out there.
Fortunately Nir Ben Levy and his team at beencounter had the same thought, and they have an active program to block risque, inappropriate, or otherwise potentially invasive sites. Mr. Ben Levy said they have over 2,000 “blacklisted” sites in a variety of domains, perhaps most importantly including financial services domains where someone could use this service for phishing or other nefarious activities. They manually maintain the blacklist which I’m sure makes for interesting conversation at beencounter HQ.
Who will benefit from beencounter?
In terms of benefits to the web analytics community a few immediately go to the top of the list:
- If you have a powerful segmentation tool you could use the beencounter API to dynamically populate custom variables with the list of sites and/or API IDs for post-hoc segmentation. For example, I could create a segment in Omniture Insights of “people who love Avinash Kaushik but not the Web Analytics Association”
- If you’re interested in measuring “loyalty” to a site, you could mine beencounter via the APIs to determine what percentage of visitors are also visiting your competitor’s sites (e.g., “disloyal”.) This is particularly cool because loyalty, as used in web analytics today, is a pretty bastardized term to say the least.
- From a targeting and testing perspective, it would be pretty simple to write a dynamic rendering engine that swapped out key site messages based on the results of calls to the beencounter API. For example, we might have a different homepage message for people we know have been to Gartner or Forrester, and we could then test differential messages using web analytics. While not a proper A/B test (unless you really randomized the audiences) this would likely yield some interesting data.
On point #3, given that the pricing plan that includes API access starts at $49.95 per month, for motivated individuals beencounter is likely the cheapest behavioral targeting solution in the world.
Things we like about beencounter:
- Provides amazing access to visitor information and offsite audience behavior
- Very simple to implement and use for folks with even basic Javascript skills
- UI is easy to understand (nothing fancy) and includes export to Excel
Things we’d like to see from beencounter:
- More information about their “blacklist”, including access to the list, and more information about their efforts to prevent abuse
- Faster servers and an uptime SLA (we have seen some slow response from their Javascript) OR a server-side option so that we could run locally and thusly manage our own uptime/response
- An option to have their script “walk” the DOM and look for pattern matches, not exact matches exclusively
Learn more about beencounter’s service at http://www.beencounter.com
Posted by Eric on Monday, February 22nd, 2010 | 29 responses | Add a Comment | Share, Save or Email



