91–100 of 213 posts
Poor man's analytics: events, client side, server side, whatever. Set up a separate DB with one big table, many columns for properties. One server call to write an event (a row), one ajax call to write from the client, throw it wherever you need. A bit of good old simple SQL for queries and reporting, and you are done.
Or a table with two columns, Key and Value. Index by key. Specify keys in code with constants. No need to alter table when adding new metrics.
Earlier quoted context omitted.
Everyone, not just web startups, is sick of IE8 and earlier. As the other commenter described, it's a lot of effort. I think when it comes to bigger organizations (such as Google not officially support IE8 anymore), it's to force laggard corporate offices to at least upgrade to IE9, if not Chrome or Firefox.
In 5 years everyone is going to be complaining that people use WebKit. And why they haven't upgraded to HerpyHouse. Oh technology...
http://royal.pingdom.com/wp-content/uploads/2011/12/111206-c...
Full article:
http://royal.pingdom.com/2011/12/06/comparing-chrome-and-fir...
Poor man's analytics: events, client side, server side, whatever. Set up a separate DB with one big table, many columns for properties. One server call to write an event (a row), one ajax call to write from the client, throw it wherever you need. A bit of good old simple SQL for queries and reporting, and you are done.
Then you have a lot of form data including passwords in your poor-manDB
I think it can actually work quite well, provided you can setup a separate service just for analytics. It's not too unreasonable to assume there are sites already doing this since the concept of a central repository that you alone control (and isn't provided by a third party) can be appealing.
Also, you have to worry less about privacy and just concentrate on keeping your own systems and services secure.
First: The service sounds great. Something I would sign up for. But I don't really get the pricing structure: What if I have less then 2500 unique users/month? Do I pay $25? Is it free? If it's $25 what then if I have more than 2500 but less than 20000 users? Is it $150 then?
Right now the way we price is pro-rate it for people who are between tiers. For example, if you have 3000 uniques per month, then you'll pay $28.75 ($25 for the first 2500 users, and then $3.75 pro-rated for 500 additional users on the next tier). If you have below 2500 users, you just pay for the portion of that $25 that you use (a site with 1000 users would pay $10). We're updating our pricing page to clarify this.
Anyone who'd use your service can look up their existing active user counts and plan accordingly -- much easier than estimating data points. However, you're going to lose some people if you require mental gymnastics to get an estimate based on arbitrary tiers and pro-rated pricing.
Poor man's analytics: events, client side, server side, whatever. Set up a separate DB with one big table, many columns for properties. One server call to write an event (a row), one ajax call to write from the client, throw it wherever you need. A bit of good old simple SQL for queries and reporting, and you are done.
@Founders of Heap:
I would love to do beta test for you guys. When do you guys open the gates for beta?
I suggest to test the text on orange button. From "Request an invite" to: "Get exclusive access" "Learn more" "Take a better look" "Find why N is for you" "Join our FREE client club." "Get a FREE account" Note that free account != free product. Just give then login details.
"Get a FREE account" Note that free account != free product. Just give then login details. Wow, that's really sleazy. I really hope nobody actually uses that idea.
Poor man's analytics: events, client side, server side, whatever. Set up a separate DB with one big table, many columns for properties. One server call to write an event (a row), one ajax call to write from the client, throw it wherever you need. A bit of good old simple SQL for queries and reporting, and you are done.
Or a table with two columns, Key and Value. Index by key. Specify keys in code with constants. No need to alter table when adding new metrics.
If there's something wrong with your DBMS where the alter table to add a row is an expensive or dangerous operation, just add a new table for every attribute, having lots of tables in a database is no worse than having lots of variables in a program.
If your DBA gets angry at you for adding new tables all the time, get a new DBA.
