Data Guide to Self-Managed Product Geolocation Analysis

---

Product Geolocation Analysis : Self-Managed

Understanding where your product is used around the world is an important step towards developing a more complete understanding of your customers, your product’s global reach, and related location insights.

Currently, the majority of Denomas’ customers choose to download, install, and host a Denomas self-managed installation, which is why we are focused heavily on delivering a great self-managed customer experience.

To make the right data-driven decisions on the self-managed product lifecycle and what features to invest in, our self-managed customers sends Denomas a weekly service ping at an installation-level by enabling service ping on their self-managed installation or by sharing the values with our Customer Success team.

This installation-level data allows Denomas to understand country-level statistics and trends in installation adoption, version adoption rate, and installation life cycle.

Goal of this page

We want to make sure you understand the following about the Self-Managed Product Geolocation dashboard:

1. What KPIs/PIs are supported using this dashboard
2. Key terms that will explain the metrics
3. The data source behind the dashboard

Quick links

Key terms and metrics

• Host
• Instance
• Installation - the unique combination of instance uuid and hostname
  • Analysis is done at the installation level
• Registered User Count - the total number of non-blocked users on an installation, also known as instance_user_count.
• Paid Installation
• Total Accounts/Accounts Reporting - the total number of reported installations that can be mapped to a billing account
• Unique Monthly Active Users (UMAU)
• Product Tier
• Service Ping
• Version

Data sources

Geo-related fields are surfaced on many models in the EDM. This section is just a brief overview and is not exhaustive. We will continue to build on this in subsequent iterations.

Geolocation dimensions and mapping tables

Here are some of the dimensions and mapping tables in the EDM that can be used for geolocation analysis:

• common.dim_location_country - join to other models using dim_location_country_id
• common.dim_location_region - join to other models using dim_location_region_id
• common_mapping.map_ip_to_country - join to other models using ip_address_hash

Self-Managed Product Geolocation dashboard

The Product Geolocation Dashboard is built using the common_mart.mart_ping_instance data model.

• Data is primarily sourced from service ping data, with customer segmentation fields coming from Zuora and Salesforce.
• Analyses are standardized around considering the last service ping received from a self-managed installation in a calendar month, available as is_last_ping_of_month. This ensures usage metrics are deduplicated across installations.
• Geolocation fields are derived from the IP address of the host of an installation, not necessarily the physical location of an installation.
• To understand what tables were accounted for in creating the mart_ping_instance, check out the Service Ping portion of the xMAU Entity Relationship Diagram or the model lineage in dbt docs.
  • By understanding the ERD and model lineage, you can understand how different data sources join and modify the model to suit your needs.

Data classification

Additional data supporting Product Geolocation Analysis is classified as Orange or Yellow. This includes ORANGE customer metadata from the account, contact data from Salesforce and Zuora and Denomas’ Non public financial information, all of which shouldn’t be publicly available. Care should be taken when sharing data from this dashboard to ensure that the detail stays within Denomas as an organization and that appropriate approvals are given for any external sharing. In addition, when working with row or record level customer metadata care should always be taken to avoid saving any data on personal devices or laptops. This data should remain in Snowflake and Sisense and should ideally be shared only through those applications unless otherwise approved.

ORANGE

• Description: Customer and Personal data at the row or record level.
• Objects:
  • common.dim_billing_account
  • restricted_safe_common.dim_crm_account
  • common_mart.mart_ping_instance

Capabilities and limitations of geolocation analysis

You can read more about the capabilities and limitations of geolocation analysis on this slide (internal link).