# VisitActionsByFilter: Matomo Matomo Live Visit Actions by Filter ## Documentation One row per action (page view, download, outlink, search, event or order) across the visits Live.VisitsByFilter's own filter_limit/filter_offset select. Requires the data of Matomo's own Actions plugin. - Catalog: `Matomo` - Schema: `Live` - Label: Matomo Live Visit Actions by Filter 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 `VisitActionsByFilter`. 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'. | | `filter_limit` | `number` | ☑ | | Maximum number of visits to read actions from, most recent first. This table always reads a bounded number of visits. | | `filter_offset` | `number` | ☑ | | Number of most-recent visits to skip before the page of filter_limit starts. | | `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 `VisitActionsByFilter` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `idsite` | `int32` | | ☑ | The Matomo site ID the enclosing visit belongs to - inherited from the parent visit, not a field of the action itself. | | `idvisit` | `int32` | | ☑ | The enclosing visit's own ID - the foreign key into Live.VisitsByFilter.idvisit, inherited from the parent visit. | | `page_title` | `varchar2` | | ☐ | Page title, where this action is a page view - null for every other action type. | | `server_time_pretty_site_local` | `varchar2` | | ☐ | When this action happened, in the site's own local time zone, as Matomo formats it. | | `subtitle` | `varchar2` | | ☐ | Matomo's own human-readable detail line for this action. | | `timestamp_utc` | `int64` | | ☐ | Seconds since the Unix epoch, UTC, of this action. | | `title` | `varchar2` | | ☐ | Matomo's own human-readable one-line title for this action, for instance 'Download' or 'Ordered (order-9001)'. | | `type` | `varchar2` | | ☐ | Action type, for instance 'action' (a page view), 'download', 'outlink', 'search', 'event' or 'ecommerceOrder'. | | `url` | `varchar2` | | ☐ | The page, download or outlink URL this action carries - null for an event or an order, which carry no URL of their own. |