# Feature usage explore The Feature usage explore has one row for every active visitor, every day they visited and every feature. A feature is a page type or a click type: a page view of a page type, such as Page: Pricing, or a click of a click type, such as Click: Add to cart. Unclassified and Other are not features. Use it for the adoption, frequency and first use of each feature. ## Good to know - Every active visitor has a row for every feature on every day they visited, used or not. A rate is one feature's only when you filter to it or group by **Feature**, and **Features per visitor** is the one rate made to read every feature at once. - Features follow your published page types and click types, which apply to all your history. - A visitor is a device, Safari keeps the device cookie for 7 days, and only visits on an allowed origin count. ## Used on dashboards Charts on these [dashboards](/docs/analytics/dashboards) are built on the Feature usage explore: - **Product and app usage**: Usage and Features ## Dimensions The Feature usage explore has 29 dimensions. ### The day ::field-table | Dimension | Type | Description | | --- | --- | --- | | Active | Date | A day the visitor visited, in UTC, and its ISO week and month. A date range on it chooses the days, and with them the active visitors every rate here is over. Time intervals: Day, Week, Month. | | Week | Date | The ISO week, from Monday, of the row's day. | | Week complete | Boolean | Whether the row's ISO week has ended, so the days a visitor used a feature in it can no longer grow. | | New or returning | String | New on the day of the visitor's first visit, in UTC, and Returning on every later day they visited. | :: ### The feature ::field-table | Dimension | Type | Description | | --- | --- | --- | | Feature | String | A page type (Page: Pricing) or a click type (Click: Add to cart), as Kontala classifies pages and clicks. Every active visitor has a row for each on every day they visited. | | Feature kind | String | Page for a page type, Click for a click type. | | Feature name | String | The feature without its kind: the page type's or the click type's label. | | Used it | Boolean | Whether the visitor used the feature that day: viewed a page of its type, or clicked something of its type. | | Uses that day | Number | How many page views of its type, or clicks of its type, the visitor made that day. | | Days used that week | Number | On how many days of the row's ISO week the visitor used the feature, 0 to 7. | | Days used in the week | String | How often in the week the visitor used the feature: on 1 day, 2 days, 3-4 days or 5-7 days. Empty in a week they did not. | | First used | Timestamp | When the visitor first used the feature, on any of their visits. Empty if they never have. Time intervals: Raw, Day, Week, Month. | | Days to first use | Number | Days from the visitor's first visit to their first use of the feature, at a fraction of a day. Empty if they never used it. | | Time to first use | String | How long after the visitor's first visit they first used the feature: within the first 24 hours (0 days), 1-6 days, 7-29 days or 30 days or more. Empty if they never used it. | :: ### How the visitor arrived ::field-table | Dimension | Type | Description | | --- | --- | --- | | Acquisition channel | String | How the visitor's first visit arrived, by the rules of Channel in the page view explore: the channel that acquired them. | | Acquisition source | String | Where the first visit came from, as the Visits explore's Source reads it. | | Acquisition medium | String | How the first visit came, as the Visits explore's Medium reads it. | | Acquisition campaign | String | The campaign the first visit's link carried. | | Acquisition campaign ID | String | The ad platform's campaign id the first visit's link carried as utm_id. | | Landing page type | String | The page type of the page the first visit landed on. | | Device id kept | String | How long the visitor's browser keeps the device cookie between visits: 7 days on Safari and on every browser on iOS, longer elsewhere. | :: ### Geo ::field-table | Dimension | Type | Description | | --- | --- | --- | | Country | String | The visitor's country as a two-letter code, such as GB, from their IP address. IP Geolocation by DB-IP (https://db-ip.com/), CC-BY 4.0. A dashboard showing this must display that attribution. | | Country name | String | The country's name in English, as the Unicode CLDR gives it, read from Country's code; a code CLDR does not name reads as itself. IP Geolocation by DB-IP (https://db-ip.com/), CC-BY 4.0. A dashboard showing this must display that attribution. | | Continent | String | One of seven continents, read from Country by the UN's regions: North America includes Central America and the Caribbean. Russia is Europe; Turkey, Cyprus, Georgia, Armenia and Azerbaijan are Asia, as the UN files them. IP Geolocation by DB-IP (https://db-ip.com/), CC-BY 4.0. A dashboard showing this must display that attribution. | :: ### Browser environment ::field-table | Dimension | Type | Description | | --- | --- | --- | | Device class | String | Bucketed from window width, not from the User-Agent. A narrow desktop window reads as mobile, which is the honest answer for a layout question; Device type answers the hardware one. | :: ### Browser, operating system and device ::field-table | Dimension | Type | Description | | --- | --- | --- | | Device type | String | Desktop, mobile, tablet or smart tv, from the User-Agent header, and unknown where it names no platform: the hardware, where Device class is the layout the window's width gives. A tablet asking for desktop sites, as Safari on iPad does by default, reads as desktop. | | Browser | String | The browser, from the User-Agent header. A browser built on Chromium that does not name itself there, such as Brave, Arc or a desktop app, reads as Chrome. A page opened inside an app reads as the app where it names itself, such as Instagram or the Google app, and as In-app browser where it does not. An app's own screens, from Kontala's SDK, read as App. | | Operating system | String | The operating system, from the User-Agent header; iOS includes iPadOS. There is no version beside it, because browsers freeze theirs: Windows 11 reports Windows 10 and every Mac reports macOS 10.15. An iPad asking for desktop sites, as Safari on iPad does by default, reads as macOS, and many Android tablets read as Linux the same way. | :: ### Data source and quality ::field-table | Dimension | Type | Description | | --- | --- | --- | | Site | String | The property the event was sent to, read from the key it was sent with. | :: ## Metrics The Feature usage explore has 16 metrics. ### Who is active ::field-table | Metric | Calculation | Description | | --- | --- | --- | | Active visitors | Count distinct | Visitors with a visit on an allowed origin on the days in the rows, each once. | :: ### Adoption ::field-table | Metric | Calculation | Description | | --- | --- | --- | | Visitors who used it | Count distinct | Active visitors who used the feature on the days in the rows, each once. Over several features, those who used any of them. | | Adoption | Ratio (%) | The share of active visitors who used the feature on the days in the rows. Empty over more than one feature. | | Features per visitor | Ratio | How many different features the average active visitor used on the days in the rows: the breadth of use. | :: ### How often ::field-table | Metric | Calculation | Description | | --- | --- | --- | | Weeks used | Count distinct | Each ISO week each visitor used the feature in, once. | | Days a week | Ratio | On how many days of a week the visitors who used the feature in it used it, on average: Amplitude's frequency, 1 to 7. Weeks cut by the date range count the days in it. Empty over more than one feature. | | Weeks used on 3+ days | Ratio (%) | Of the weeks a visitor used the feature in, the share they used it on 3 days or more: how much of its use is a habit. Empty over more than one feature. | | Uses | Sum | Page views of the feature's page type, or clicks of its click type, on the days in the rows. | | Uses per visitor who used it | Ratio | How many times the visitors who used the feature used it on the days in the rows, on average. Empty over more than one feature. | :: ### First use ::field-table | Metric | Calculation | Description | | --- | --- | --- | | First-time users | Calculated | Visitors who used the feature for the first time ever on the days in the rows. Empty over more than one feature. | | Median days to first use | Calculated | How many days after their first visit the visitors who first used the feature on the days in the rows typically first used it. Empty over more than one feature. | :: ### Adoption by who the visitor is ::field-table | Metric | Calculation | Description | | --- | --- | --- | | Adoption, new visitors | Ratio (%) | The share of visitors who used the feature on the day of their first visit, over the visitors whose first visit fell in the rows. Empty over more than one feature. | | Adoption, returning visitors | Ratio (%) | The share of returning visitors who used the feature on their returning days in the rows. Empty over more than one feature. | | Adoption on mobile | Ratio (%) | The share of active visitors on a phone who used the feature. A visitor is a device, so its type is its first visit's. Empty over more than one feature. | | Adoption on desktop | Ratio (%) | The share of active visitors on a desktop who used the feature. Empty over more than one feature. | | Adoption on tablet | Ratio (%) | The share of active visitors on a tablet who used the feature. Empty over more than one feature. | ::