Are you seeing errors on your website or peekin.io? There are a lot of console error on peekin.io that are due to the html being sandboxed and there is no way around that.
Otherwise I can take a look :)
--
As for the product itself: I'm not sure—are you saying you'd use it to watch your user "proactively" or when they ask for support?
I get what you're saying—I guess what I'm trying to understand is whether a regular user has an unspoken expectation that browsing or using a web app is "private"--in which case that expectation is already broken most of the times by usage of analytics and, less often by session recording tech--or whether it is like walking in a store: no one is bothering you but you know that there's someone that might be seeing what you are doing, and if you stand in front of an item long enough someone is gonna come over asking if you need any help.
Apps like intercom already allow you to specify "triggers" so that when the user does something you can send them a message. I'm not sure how many people actually realize that it is an automated message.
By the way, what I meant with scalability is that if you have up to say 10-15 users at a time you can keep track of them easily, if it's more you either need more people or the whole monitoring station becomes worthless
Regarding it being creepy—I'm not sure how I see it myself.
In a way it's a lot more creepier that advertising companies know your tastes and have a shitload of info about you--sometimes more than you do.
At the end of the day we only track the HTML the site owner provides in the first place, and stuff like mouse movements within the page, without it ever being recorded.
On the other hand, I agree that the fact that you "see" the page being used and not just collect metadata could be deemed very creepy.
Hey everyone,
I created a tool to personalize a webpage with geolocational data using only HTML.
You can do things like showing / hiding content based on the location of the user, or incorporate their location into a headline or text, with an elegant, ruby-looking syntax.
If it produces an email it is pretty accurate. It checks various possibilities, and returns the valid ones. If only one is returned you can be pretty sure it is a valid email. You can use the social links to see if the email is associated to a facebook / twitter account.
It does check that the domain is not "catch-all", or that it doesn't simply ignore our queries.
Are you seeing errors on your website or peekin.io? There are a lot of console error on peekin.io that are due to the html being sandboxed and there is no way around that.
Otherwise I can take a look :)
--
As for the product itself: I'm not sure—are you saying you'd use it to watch your user "proactively" or when they ask for support?
Thank you!