View-based popularity metrics
Understand how Tableau Cloud usage translates into popularity signals in Atlan. This page covers the supported assets, how attributes are mapped, the scoring logic used to calculate popularity, and the time windows applied to measure engagement.
When can popularity metrics be populated
Popularity is only populated when all of the following conditions are met:
- Source is Tableau Cloud. Tableau Server doesn't expose the Content Exploration API.
- Tableau REST API version is 3.17 or higher (Tableau Cloud December 2022 release or later).
- Authentication uses Personal access token or Basic. JWT bearer authentication isn’t supported. For more details, see why JWT bearer authentication isn’t supported.
- The authenticating user has the Site Administrator Explorer role on the site being crawled.
If any condition isn't met, the crawl completes successfully but popularity attributes aren't populated.
Supported asset types
| Tableau asset | Atlan asset type |
|---|---|
| Workbook | TableauWorkbook |
| Dashboard | TableauDashboard |
| Worksheet | TableauWorksheet |
| Published data source | TableauDatasource |
| Flow | TableauFlow |
Embedded data sources, projects, sites, calculated fields, and data source fields don't have independent usage metrics in Tableau.
Popularity attributes
The table below maps Tableau view data to Atlan asset properties and shows where each attribute is surfaced in Atlan.
| Source data | Atlan property | Where in Atlan |
|---|---|---|
All-time view count (hitsTotal) | sourceReadCount | Asset preview popularity popover, overview sidebar |
| Derived from windowed view counts | popularityScore | Asset preview popularity indicator, sort menu |
| Windowed view counts (14-day, 30-day, 90-day, 365-day) | tableauSourceReadCounts | Asset preview popularity popover, overview sidebar |
Score formula
Popularity score is calculated using a weighted, time-decayed view count model. Each time window contributes incrementally, and older activity is progressively down-weighted.
period_2w = hits_last_two_weeks
period_2w_1m = max(0, hits_last_one_month - hits_last_two_weeks)
period_1m_3m = max(0, hits_last_three_months - hits_last_one_month)
period_3m_12m = max(0, hits_last_twelve_months - hits_last_three_months)
period_older = max(0, hits_total - hits_last_twelve_months)
weighted =
0.40 * period_2w
+ 0.25 * period_2w_1m
+ 0.20 * period_1m_3m
+ 0.10 * period_3m_12m
+ 0.05 * period_older
popularityScore = round(log(1 + weighted) * 10, 4)
Time window weights
Each incremental period contributes differently to the final score based on recency:
| Time window | Weight |
|---|---|
| Last 2 weeks | 0.40 |
| Weeks 2 to 4 | 0.25 |
| Months 1 to 3 | 0.20 |
| Months 3 to 12 | 0.10 |
| Older than 12 months | 0.05 |
Windowed view counts
Atlan records view counts in tableauSourceReadCounts across fixed time windows. Each value represents the total views within a complete window, anchored to the time of ingestion during the crawl.
| Window | Days |
|---|---|
| Last 2 weeks | 14 |
| Last 1 month | 30 |
| Last 3 months | 90 |
| Last 12 months | 365 |
Values are recalculated on each crawl and overwrite previously stored counts.
See also
- How Tableau popularity works: Score formula design, JWT limitation, and how Tableau popularity differs from miner-based connectors.
- What does Atlan crawl from Tableau: Full set of Tableau assets and properties Atlan extracts.
- Interpret usage metrics: How popularity metrics surface across connectors in Atlan.