# Resolution: Matomo Matomo Resolution ## Documentation Visits over one period broken down by screen resolution - one row per resolution, 'unknown' where Matomo could not determine one. - Catalog: `Matomo` - Schema: `Resolution` - Label: Matomo Resolution This is a read-only table function. The Matomo API may not support changing the data or the Invantive UniversalSQL driver for Matomo does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Matomo API. ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `Resolution`. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values. Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three. Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third. | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `date` | `varchar2` | ☑ | | The date the period is anchored on, or a range such as '2026-08-01,2026-08-31'. | | `id_site` | `number` | ☑ | | The Matomo site ID to report on. | | `period` | `varchar2` | ☑ | | The reporting period: day, week, month, year or range. | ## Columns of Table Function The columns of the table function `Resolution` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `bounce_count` | `varchar2` | | ☐ | Number of visits at this resolution with exactly one action. Numeric, though Matomo does not report it with a consistent type. | | `label` | `varchar2` | | ☐ | Screen resolution, for instance '1920x1080', or 'unknown'. | | `max_actions` | `int32` | | ☐ | Maximum number of actions in a single visit at this resolution. | | `nb_actions` | `varchar2` | | ☐ | Number of actions across visits at this resolution. Numeric, though Matomo does not report it with a consistent type - see UserCountry.Country's own equivalent column. | | `nb_visits_converted` | `varchar2` | | ☐ | Number of visits at this resolution during which at least one goal was converted. Numeric, though Matomo does not report it with a consistent type. | | `nb_visits` | `int32` | | ☐ | Number of visits at this resolution. | | `segment` | `varchar2` | | ☐ | Matomo's own segment expression selecting exactly this resolution, usable as the segment argument of another reporting table. | | `sum_daily_nb_uniq_visitors` | `int32` | | ☐ | Sum, over every day in the period, of the number of unique visitors at this resolution that day - not the same as a period-wide unique count, which Matomo does not sum this way across days. | | `sum_daily_nb_users` | `int32` | | ☐ | Sum, over every day in the period, of the number of visits with a User ID set at this resolution that day. | | `sum_visit_length` | `varchar2` | | ☐ | Sum of the length of visits at this resolution, in seconds. Numeric, though Matomo does not report it with a consistent type. |