Atlan Release Notes Product Updates logo
Back to Homepage Subscribe to Updates

Product Updates

See the latest new features, improvements, and product updates

Labels

  • All Posts
  • Assets
  • Glossary
  • Insights
  • Workflows
  • Governance
  • Admin & Integrations
  • Reporting Center
  • Developers
  • Fix
  • Improvement
  • New

Jump to Month

  • February 2026
  • January 2026
  • December 2025
  • November 2025
  • October 2025
  • September 2025
  • August 2025
  • July 2025
  • June 2025
  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • June 2022
  • May 2022
GovernanceAdmin & IntegrationsNew
today

Analyze Atlan product usage using Atlan Lakehouse

🎉 What’s new

As a data leader, you'll want to understand how your teams are adopting and using Atlan.

We've added a new usage_analytics namespace/schema to Atlan Lakehouse that exposes product telemetry captured from Atlan’s UI – every page view, user action, and identity snapshot – so you can understand how your teams interact with Atlan and measure adoption, engagement, retention and beyond.

Previously, you had to rely on custom charts and exports to understand who was active, which features were used, and how engagement changed over time. Now, curated product usage tables live directly in your Lakehouse, so you can analyze product usage using the same SQL and tools you already use and trust.

✨ Let’s dig deeper

In practice, this means you can turn raw Atlan activity into clear, visual insights about how your teams work with data:

  • Track active users over time by workspace, role, or team so you can see whether onboarding and enablement actually stick.
  • Understand feature adoption by looking at which core workflows (like search, lineage, glossary, or queries) are used most, and where usage drops off.
  • Monitor engagement patterns (daily, weekly, monthly activity) to spot healthy teams, identify dormant groups, and time interventions before adoption slips.
  • Build retention views that show how frequently users come back after their first week or month, and which behaviors correlate with long-term value.
  • Join usage analytics with your own business data (for example, teams, departments, or customers) so you can see which parts of the organization get the most value from Atlan.

Because everything lives in your Lakehouse, you can plug these tables into your favorite compute platform or data visualization tool, so you can build reports and AI applications to understand how Atlan usage evolves across teams, features, and time.

👏 Give it a shot

You can start exploring usage analytics data for your Atlan tenant today:

  • First, make sure Lakehouse is enabled for your Atlan tenant
  • In your Lakehouse environment, look for the usage_analytics namespace/schema alongside your existing Atlan metadata schemas
    • Use your preferred compute platform to run SQL queries against the usage_analytics tables to inspect active users, features, or time ranges
    • Connect your BI or reporting tool to your compute engine to build dashboards that visualize active users, feature adoption, and retention for your Atlan tenant
    • If you use Claude as your AI assistant, run the same usage analytics queries conversationally using the atlan-usage-analytics skills repository so you can ask questions in natural language instead of writing SQL.
  • Check out sample queries for product usage analytics in our use case documentation.

📘 Learn more

Visit the docs to learn more about the usage_analytics schema, including tables, use cases, and sample queries you can use to drive product usage analytics use cases.