|
|
|
|
|
by michokest
4279 days ago
|
|
As a second-time founder, I found Mixpanel to be the most expensive piece of SaaS we were using in our stack: at barely 30k users, it was already far more expensive than our whole hosting bill combined! Then I switched solutions for a while, looking for a good combination that'd give me Facebook attribution data plus user behavior. So far, I haven't found my ideas combination and in a way, Amazon doesn't change that. I find that solutions like segment.io are great in the way that you can install their SDK just once, and have that proxy the events to all other SDKs. For now that's what I chose to do, to avoid week-long delays for approval publishing our apps in the app store. |
|
We instead started throwing all of our events into Google big query. You can steam events directly into a table or proxy then through your server to add more metadata. You can even use mixpanels great open source client libraries and point them at your servers.
Initially I was worried that we would miss mixpanels built in analysis and tools but we honestly preferred querying a database with SQL better. The tricky queries are the funnels but once you wrote the query once you can just save the template. The only thing we had to build was a chrome extension that could graph the results of an arbitrary query.