# ContainerTagsByContainerVersion: Matomo Matomo Tag Manager Container Tags ## Documentation What fires, when its triggers say to: the unit which fire_trigger_ids and block_trigger_ids attach to ContainerTriggersByContainerVersion. Read and insert; update/delete deferred as representative-sibling scope, the same reasoning ContainerVariablesByContainerVersion's own build already closed. - Catalog: `Matomo` - Schema: `TagManager` - Primary Keys: `idtag` - Label: Matomo Tag Manager Container Tags - Retrieve: True - Insert: True - Update: False - Delete: False ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `ContainerTagsByContainerVersion`. 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 | |---|:---:|:---:|:---:|---| | `id_container_version` | `number` | ☑ | | The version to list tags of - Matomo.TagManager.ContainerVersionsByContainer.idcontainerversion. | | `id_container` | `varchar2` | ☑ | | The container to list tags of - Matomo.TagManager.Containers.idcontainer. | | `id_site` | `number` | ☑ | | The Matomo site ID the container belongs to. | ## Columns of Table Function The columns of the table function `ContainerTagsByContainerVersion` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `block_trigger_ids` | `varchar2` | | ☐ | ContainerTriggersByContainerVersion.idtrigger values that block this tag from firing even when a firing trigger matches, as JSON text (a JSON array of integers). | | `created_date` | `varchar2` | | ☐ | Date and time the tag was created, as returned by Matomo. Matomo does not document which time zone this is expressed in. | | `description` | `varchar2` | | ☐ | Tag description. | | `end_date` | `varchar2` | | ☐ | Date the tag stops firing, or empty for no end restriction. Matomo does not document which time zone this is expressed in. | | `fire_delay` | `int32` | | ☐ | Delay before firing, in milliseconds. | | `fire_limit` | `varchar2` | | ☐ | How often the tag may fire per page, for instance 'unlimited' or 'once'. | | `fire_trigger_ids` | `varchar2` | | ☐ | ContainerTriggersByContainerVersion.idtrigger values that fire this tag, as JSON text (a JSON array of integers) - a required insert argument, measured live 2026-08-30 ("Fire Trigger: A value needs to be provided." without it), decomposed into indexed bracket-array form fields (fireTriggerIds[0]=..., not the bare repeated fireTriggerIds[]=...) by the same ParametersToFormBody mechanism, confirmed live to answer identically to Matomo's own repeated-key form. | | `idcontainer` | `varchar2` | | ☐ | The container this tag belongs to - addContainerTag's own required insert argument. Nullable because getContainerTags' own response carries no idContainer property at all, the same absence ContainerVariablesByContainerVersion's own idcontainer already documents. | | `idcontainerversion` | `int32` | | ☑ | The version this tag belongs to. addContainerTag's own PHP parameter is 'idContainerVersion' - case-sensitive, same reason as ContainerVariablesByContainerVersion's own idcontainerversion. | | `idsite` | `int32` | | ☑ | Site ID the container belongs to. | | `idtag` | `int32` | | ☑ | Tag ID - assigned by Matomo on insert, never written. | | `name` | `varchar2` | | ☑ | Tag name. | | `parameters` | `varchar2` | | ☐ | Type-specific configuration, as JSON text, in the same shape as the parameters column of ContainerTriggersByContainerVersion - decomposed into PHP's own bracket-array form fields on insert, see ParametersToFormBody. | | `priority` | `int32` | | ☐ | Fire order relative to other tags on the same trigger - lower fires first. | | `start_date` | `varchar2` | | ☐ | Date the tag starts firing, or empty for no start restriction. Matomo does not document which time zone this is expressed in. | | `status` | `varchar2` | | ☐ | Tag status, for instance 'active'. Pausing or resuming a tag is an update of this column. | | `type` | `varchar2` | | ☑ | Tag type, as defined by Matomo: for instance 'Matomo', its own tracking tag, or 'ThemeColor'. The types available per context are in TagManager.AvailableTagTypesByContext. | | `updated_date` | `varchar2` | | ☐ | Date and time the tag was last changed, as returned by Matomo. Matomo does not document which time zone this is expressed in. |