dorkitude/paragraphs cut.txt

## paragraphs cut.txt
Most analytics tools are made to help app makers study what users are doing in some specific type of app. This kind of tool works okay, provided your app looks enough like the others apps the tool was built for, and your users’ behaviors are enough like the behaviors in those other apps. What if your app is unique, and the questions you have are unique? (Before Keen, the state of the art was to build your own Observatory from scratch.)

The data model breadth of those tools may not be enough for you. What if user behavior in the app layer is only a part of your business? What if you want to study your marketing website copy, your paid acquisition funnel, the response time performance of your your webservices layer, all in the same system? (Before Keen, the state of the art was to build your own Observatory from scratch.)

What if you want other humans — your customers, your partners, your merchants, or just other departments in your company — to get value from the same data? What if you wanted applications to get value from the data and drive automated actions? (Before Keen, the state of the art was to take screenshots of reporting tools and send them around, until you get fed up with it and build your own Observatory from scratch.)

Whereas at Keen IO, we provide a syntax that allows any human (or robot) to record any event that is happening, with a broad amount of state (literally 1,000 properties per event), gathering a running log of all of those events over time, just by hooking into our APIs. We also provide a set of APIs for enriching that data, shipping it around to other services, and running computation across that data. Developers can combine these building blocks in infinite permutations to solve the problems they actually have, and to study their universe as they see it.
	Most analytics tools are made to help app makers study what users are doing in some specific type of app. This kind of tool works okay, provided your app looks enough like the others apps the tool was built for, and your users’ behaviors are enough like the behaviors in those other apps. What if your app is unique, and the questions you have are unique? (Before Keen, the state of the art was to build your own Observatory from scratch.)

	The data model breadth of those tools may not be enough for you. What if user behavior in the app layer is only a part of your business? What if you want to study your marketing website copy, your paid acquisition funnel, the response time performance of your your webservices layer, all in the same system? (Before Keen, the state of the art was to build your own Observatory from scratch.)

	What if you want other humans — your customers, your partners, your merchants, or just other departments in your company — to get value from the same data? What if you wanted applications to get value from the data and drive automated actions? (Before Keen, the state of the art was to take screenshots of reporting tools and send them around, until you get fed up with it and build your own Observatory from scratch.)

	Whereas at Keen IO, we provide a syntax that allows any human (or robot) to record any event that is happening, with a broad amount of state (literally 1,000 properties per event), gathering a running log of all of those events over time, just by hooking into our APIs. We also provide a set of APIs for enriching that data, shipping it around to other services, and running computation across that data. Developers can combine these building blocks in infinite permutations to solve the problems they actually have, and to study their universe as they see it.