Platform X
Search…
⌃K

Matomo

Matomo, formerly Piwik, is an open source web analytics application to track online visits to one or more websites and display reports on these visits for analysis. Using this destination you can implement server-side tracking using Matomo Tracking HTTP API.

Key features

The Matomo destination provides the following key features:
  • Events structure: our Events reference covers Matomo's request structure, meaning that your data is properly bridged to the expected fields in an optimized way.
  • Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.
  • Custom events and properties: you can freely push custom events and properties based on your specific needs.
  • Support for multi-item data: information included in the item array is bridged to Matomo.

Destination setup

Matomo recommends using custom parameters instead of custom variables as the latter are deprecated. The data for some Matomo optional fields will not be available in your app / technical layer which is expected, but you should provide as much information as you can.

Configuration

Settings
Description
Server Domain
Required
Your server domain as provided by Matomo. (https://your-matomo-domain.example/matomo.php)
Site Id
Required
Your site identifier as provided by Matomo. More details are available following this LINK.
Visitor Id Cookie Name
Cookie name holding a few details about the user such as the unique visitor ID. It normally starts with the string _pk_id. More details are available following this LINK. (E.g. value "4e4eb04b31f37eac.1653656637.")
User Identifier
You can bridge your selected user identifier for logged users. More details are available following this LINK.
Matomo Custom Variables
Map your Matomo custom variables by setting their field names in Custom Variable Name and adding the field name holding the value in Commanders Act event property or static value. E.g. if you inputsizein Custom Variable Name and properties.items.0.product.size in Commanders Act event property or static value, you'll have a custom variable in Matomo calledsizewith a value based on the content of the field properties.items.0.product.size [1]. You also have the option to set a static string/numeric value in Commanders Act event property or static value. More details on custom variables are available following this LINK.
Matomo Custom Parameters
Map your Matomo custom parameters by setting their field names in Custom Parameter Name and adding the field name holding the value in Commanders Act event property or static value. E.g. if you inputsizein Custom Parameter Name and properties.items.0.product.size in Commanders Act event property or static value, you'll have a custom parameter in Matomo calledsizewith a value based on the content of the field properties.items.0.product.size [1]. You also have the option to set a static string/numeric value in Commanders Act event property or static value. More details on custom parameters/dimensions are available following this LINK.
Matomo Goals
Map your Matomo goals by setting the Commanders Act Event Name in the related field and the Matomo Goal Id associated with it. More details on goals are available following this LINK.
Authorization Token
An authorization token is required to send additional parameters. More details on these parameters are available following this LINK.
[1] Using "dots" (".") you can navigate deeper to the specific field you want to get the value of. See Events reference for more details on the standard field names by event. You can also freely set custom fields: there are no boundaries.

Field Mappings

Matomo propertye_cis statically set withca_event. Ecommerce parameters are passed for incoming purchase events.
Commanders Act Properties
Matomo Properties
Site Id
idsite
event_name
action_name
e_a
e_n
properties.value
e_v
revenue
page.location
url
device.user_agent
ua
Visitor Id Cookie Name
_id [1]
page.referrer
urlref
Matomo Custom Variables
_cvars
properties.user.id
properties.user.email
properties.user.email_md5
properties.user.email_sha256
[custom_property]
uid [2]
properties.search_term
search
Matomo Goals
idgoal [3]
properties.id
ec_id
[[properties.items.0.id,properties.items.0.product.name,properties.items.0.product.category_1,properties.items.0.product.price,properties.items.0.quantity],...,[properties.items.N.id,properties.items.N.product.name,properties.items.N.product.category_1,properties.items.N.product.price,properties.items.N.quantity]]
ec_items [4]
properties.revenue
ec_st
properties.tax_amount
ec_tx
properties.shipping_amount
ec_sh
Authorization Token
token_auth
device.ip
cip
event_timestamp
cdt
[1] If a cookie is not provided, this destination searches for a cookie name containing the string_pk_idto retrieve the visitor identifier from it. [2] Depending on the drop-down selection (SeeUser IdentifierinConfiguration), a specific Commanders Act property is used. [3] Based on your configuration (SeeMatomo Goalsin theConfiguration), a specific identifier is set in this field. Withpurchaseevents,0is bridged as identifier. [4] The resulting array is encoded.
Last modified 2mo ago