To provide the level and granularity of reporting, coupled with the expansive options of filters layers, Sublytics has optimized the way that data is being utilized by using a data lake model.
What is a Data Lake?
A data lake is a central repository of data that allows Sublytics to deposit all the data being collected into one central place.
Each individual report can then pull directly from the "lake" to build the analytics based the data needed for that report.
Our approach is first of its kind leveraging the capabilities of a data lake but applied to data that updates whereas standard uses are for data that never changes. The data lake powers users to run very large date ranges with very granular data filters applied.
Why is a Data Lake important?
You can run large scale reports, with millions of records, outputting the metrics you are use to with Sublytics and filtering how you want in a matter of seconds.
This also allows Sublytics to rapidly deploy new reports and dashboard visualizations that will load with optimized speed and performance.
What does this mean for my data?
Depending on the size of data, there may be a minimal delay of the data available within the report.
How will I know if my data is up to date?
If you are running a large data analysis more than 5 days, there will be a minimal delay.
Next to the data picker will be a status update of how recent the data that you are viewing is.
-
- Data Updated: When the data was last updated
- Next Update: The estimated time the next refresh will begin
Here you can see Data Updated: 14 minutes ago. This means that any new or modified records that are used in this report since the last update will not be included.
(click to expand)
Need real-time* analytics? Not a problem.
If the date range is less than 5 days worth of data, all data in the report is real-time* and no delay is present.
Here you can see Data Updated: Up To Date
(click to expand)
* Real-Time Analytics
Third Party Data Connections will always have 1 hour delay
What data is delayed?
Here are some examples to understand the latency of data refresh:
- Running a 6 month LTV analysis, if the data was updated 14 minutes ago, any new or modified records that are used in this report within the past 14 mins will not be included in the report.
- Looking at new sales today, all data as soon as it hits the Sublytics system (any new or modified records). This is an example of a "real-time" report, since that date is set for a single day, no data delay is present