# Users: Matomo Matomo User ID Users ## Documentation Visits over one period broken down by Matomo's own persistent User ID - one row per User ID, empty where no visit on the site has ever carried one. idvisitor links a row to Live.VisitsByFilter's own visitor_id column for the same visitor. - Catalog: `Matomo` - Schema: `UserId` - Label: Matomo User ID Users 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 `Users`. 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 `Users` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `bounce_count` | `int32` | | ☐ | Number of visits carrying this User ID with exactly one action. | | `idvisitor` | `varchar2` | | ☐ | Matomo's own opaque visitor identifier for this User ID - the same value Live.VisitsByFilter's own visitor_id column carries for a matching visit. | | `label` | `varchar2` | | ☐ | The User ID, as the site's own tracker sent it. | | `max_actions` | `int32` | | ☐ | Maximum number of actions in a single visit carrying this User ID. | | `nb_actions` | `int32` | | ☐ | Number of actions across visits carrying this User ID. | | `nb_visits_converted` | `int32` | | ☐ | Number of visits carrying this User ID during which at least one goal was converted. | | `nb_visits` | `int32` | | ☐ | Number of visits carrying this User ID. | | `segment` | `varchar2` | | ☐ | Matomo's own segment expression selecting exactly this User ID, 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 carrying this User ID that day. | | `sum_daily_nb_users` | `int32` | | ☐ | Sum, over every day in the period, of the number of visits with a User ID set carrying this User ID that day. | | `sum_visit_length` | `int32` | | ☐ | Sum of the length of visits carrying this User ID, in seconds. |