diff --git a/configuration/analytics.mdx b/configuration/analytics.mdx
index 9e83bfc..bf58d4c 100644
--- a/configuration/analytics.mdx
+++ b/configuration/analytics.mdx
@@ -13,7 +13,7 @@ Currently, Flipt has support for reporting data into:
 The data that gets reported into the storage backends are currently:
 - Flag Evaluation Count
 
-All of these analytics are viewable on the UI, and users can look back up to 12 hours of data for each metric.
+All of these analytics are viewable on the UI, and users can look back up to 24 hours of data for each metric.
 
 ![UI For Analytics](/images/configuration/analytics_quick_view.png)
 
@@ -21,6 +21,14 @@ The image above shows the past 30 minutes of evaluation(s) count for the flag `f
 
 ## Considerations
 
-It is important to note that you are **required** to create a database called `flipt_analytics` so that Flipt will have a logically isolated instance to report data into without interrupting any of your possible existing data in other databases.
+### Database
 
-The reason for this is not just a separation of concerns on a general level, but for possible data migrations and other related things via data on a technical level.
+It is important to note that we do *recommend** for you to a separate database for analytics produced by Flipt so that the data can logically isolated from the rest of your Clickhouse data.
+
+The reason for this is not just a separation of concerns on a general level, but for possible data migrations and other related things via data on a technical level if changes do arise on our end.
+
+### Origin of Analytics
+
+Analytics are only produced currently as they pass through the server, which means if you use the [server sdks](/integration/server/rest) or the various [grpc sdks](/integration/server/grpc), analytical data will be sent to the backing store.
+
+For client-side evaluation no metrics will be sent into clickhouse, but we are working on a feature to get it supported.