Google Analytics summarized simply with Arc
How often do you check your analytics: Once a day? Once a week? Less?
When we launched QuickBit we looked at Google Analytics everyday. Whoever checked first posted the numbers into Slack and we all congratulated ourselves on our growth. We wanted to stay on top of the progress and really start using the data to give our users a better experience. But, as the days turned to months, we got distracted. We were working on new products that took all our focus.
For a small team like ours, checking analytics never felt like our highest priority.
We were disappointed in ourselves. We were too distracted pushing new ideas forward to see what was happening right in front of us. Our products are important and our users are the key to our success. We should be more aware of our app analytics. But we weren’t, and we weren’t alone. We decided to solve our own problem and create a simple service to help our small remote team with analytics: Arc.
Arc started by summarizing our blog’s Google Analytics in Slack so we didn’t have to go looking for data ourselves. We started simple and only focused on website visitors. Even that basic information got us talking about our site and thinking more about how we could use analytics to improve our products. After a few weeks of staying on top of our analytics, we were still excited to see the summaries in our Slack channel. We felt great about solving our own issue with a very simple solution and realized that we should start to share this with other people having the same problems.
So, if you want to simplify analytics, check out Arc. Let’s face it, most people don’t want to analyze graphs and tables. Arc explains your analytics with short, easy to read messages that everyone understands. This keeps your team informed and enables everyone to make better customer decisions.
Arc quietly been public for about a month, so this is just the beginning. Get in touch with us at firstname.lastname@example.org and let us know what Arc can do for you.
Originally published at blog.unioncode.com on February 17, 2016.