To explain which dashboards and datasets we support in Lookout Analytics, what kind of help you can expect, and what parts are shared responsibility between us and our customers.

Lookout Analytics essential dashboards and custom dashboards.

The person with the “Billing and subscription” management permission in your instance of Lookout can add, remove, or change Analytics seats for users. The decision to give access to Analytics depends on your organisational structure, policies, budget, and risk profile.

We will not add, remove, or change seats for you. However, if there is no person with the “Billing and subscription” management permission in your instance of Lookout, we will help you configure this permission for the key contact of your account.

We provide full support for all essential dashboards built and maintained by us, including:

Support means answering questions about the data powering the dashboards, troubleshooting access issues, troubleshooting data integrity issues, and troubleshooting performance issues.

We do not provide support for custom dashboards, but we do provide limited support to Analytics Superusers who can build and maintain custom dashboards.

Please appreciate custom dashboards are essentially an interpretation of your business requirements, the data input by your users into Lookout, the configuration of your instance of Lookout, and how we structure data inside Lookout. Therefore, questions and troubleshooting about accuracy, integrity, and performance are most appropriately directed to the Analytics Superusers who build and maintain your custom dashboards.

We will support Analytics Superusers with questions about our datasets, troubleshooting data integrity issues, and troubleshooting performance issues.

We provide two datasets for querying your Lookout data. The gold, curated dataset is called lookout_analytics and powers the essential dashboards. The bronze, edge dataset is called lookout_analytics_edge and is only available to Analytics Superusers. Both datasets can be used in custom dashboards, but it’s important to understand the distinction between them.

Relationships between tables follow the Ruby on Rails schema naming conventions. For example, fct_visits.membership_id is the foreign key which referes to dim_memberships.id.

We currently have an internal service level objective to refresh data at 7 AM, 12 PM, 4 PM, and 8 PM AEST (UTC+10). We do not currently make guarantees about this service level, but in practice we achieve this objective. We include a last refresh timestamp at the bottom of our essential dashboards. This is the same refresh timestamp for all our datasets.

Please appreciate regularly refreshing hundreds of gigabytes of data is no small feat, and is common for these kinds of data pipelines to only refresh once a day. We are by care, for care, so we understand the imperative of having access to up-to-date data. We are currently evaluating new methods for refreshing data, but it’s unlikely to ever be real-time.

Analytics is designed for reporting on your dataset in aggregate—or by segment—not for tracking individual clients or workers. Most tables include a link property that connects directly to the corresponding record in your Lookout instance.

In response to our risk assessment, we currently redact or omit personally identifiable information (PII)—such as names, dates of birth, and free-form text—from the dataset to help safeguard sensitive data.

If you require access to PII as part of your aggregate reporting, we recommend using our Data Export tool or the BYOBI Data Pipeline add-on.

This is an add-on for service proviers who are looking to further customise and integrate Lookout’s datasets into their business using familiar tools such as Microsoft PowerBI and Microsoft OneLake.

BYOBI Data Pipeline is built from the same dataset as Analytics, except PII is available.