Matomo / Matomo Tag Manager

summary official websites true 162 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type developer integrations true 160 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type ( ) ( ) available since pxp 3 8 0 ( ( ) ) available since pxp 3 8 2 tracking service event support matrix overview of the supported events and their configuration true 163,262left unhandled content type unhandled content type unhandled content type left unhandled content type unhandled content type unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type unhandled content type left unhandled content type left unhandled content type left unhandled content type ( ) ( ) purchases purchases contains special handling regarding tracking behavior more detailed information can be found below in the description of the event configuration for actions and views ( ( ) ) purchases purchases are supported for native apps only ( ( ) ) the name name template is used by matomo tag manager only general structure in tracking config json tracking service key name in " tracking config json " is " matomo matomo " general structure { "matomo" { "eventsenabledbydefault" true, "viewsenabledbydefault" true, "purchasesenabledbydefault" true, "attributesenabledbydefault" true, "events" { // your configured list of events }, "views" { // your configured list of events }, "purchases" { // your configured list of events }, "attributes" { // your configured list of attributes } } } event configuration custom dimensions matomo supports custom dimensions custom dimensions are distinguished into two different types "visit dimensions" used for purple attributes and "action dimensions" used by action and view events actions matomo supports action events action event "action event key" { "templates" { "trigger" "the name of the trigger in matomo tag manager", "category" "value of template", "action" "value of template", "name" "value of template", "value" "value of template" }, "parameters" { "parameter key 1" "value of parameter", // your configured list of parameters (supported via web only) } } example "issue downloaded" { "templates" { "category" "app", "action" "issue downloaded", "name" "{{issue name}}", "value" "1" } } example with parameters "issue downloaded" { "templates" { "action" "issue downloaded {{issue name}}", "category" "epaper", "label" "issue downloaded" }, "parameters" { "1" "{{issue id}}" // assuming that a custom visit dimension is configured as "issue id" at matomo and has this id of "1" } } templates true 138,96 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type parameters matomo supports parameters for action events in web only parameters must be configured as custom action dimension at matomo true 230,96 unhandled content type unhandled content type unhandled content type unhandled content type views matomo supports view events depending on the platform used, the configuration differs as follows native purple app view event "view event key" { "templates" { "path" "value of template", "title" "value of template" } } example 1 "storefront feed" { "templates" { "path" "/storefront/feed", "title" "app/feed" } } example 2 "app menu" { "templates" { "path" "/app menu", "title" "app/menu" } } templates true 161,96 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type web integration for web integration, the path template is omitted because matomo sets this value automatically view event "view event key" { "templates" { "trigger" "the name of the trigger in matomo tag manager", "name" "value of template", "title" "value of template" }, "parameters" { "parameter key 1" "value of parameter", // your configured list of parameters (supported via web only) } } example javascript tracking client "storefront feed" { "templates" { "title" "app/feed" } } example matomo tag manager "app menu" { "templates" { "name" "app menu", "title" "app/menu" } } templates true 161,96 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type parameters matomo supports parameters for view events in web only parameters must be configured as custom action dimension at matomo true 258 unhandled content type unhandled content type unhandled content type unhandled content type purchases matomo supports purchase events in native apps only purchase event "purchase event key" { "templates" { "category" "value of template", "action" "value of template", "name" "value of template", "product name" "value of template", "product category" "value of template" } } example "storefront issue purchased" { "templates" { "category" "storefront", "action" "issue purchased", "name" "{{issue name}}", "product name" "{{product id}}", "product category" "single purchase" } } templates matomo offers a specific api to track purchases tracking purchase events takes place in two steps an event is sent with the value of the price an additional order item is tracked (1) templates used for the event true 161,96 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type (2) templates used for the order item true 161,96 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type the order item is sent with some additional values true 202 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type attributes matomo supports attributes via custom dimensions custom dimensions are distinguished into two different types "visit dimensions" and "action dimensions" purple attributes correspond to the "visit dimensions" for more information please read the matomo documentation attribute "attribute key" { "templates" { "id" "value of template" } } example "has active subscription" { "templates" { "id" "1" } } templates true 161,96 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type additional supported functionality custom user id https //matomo org/faq/reports/set up user id tracking in matomo/ this feature is not not fully enabled as provided by matomo purple sets the user id in native apps only the generated purple device id is used for this url whitelisting https //matomo org/faq/how to/faq 21077/ matomo offers the possibility to create a whitelist of urls this ensures that only events whose url matches one of the whitelist urls are recorded if you want to send data from both your native apps and your website to the same matomo site and also want to enable the whitelist feature, please read on here docid\ u qv254gvcz zax1ukxav how to configure native purple app any native tracking service is configured in the purple manager purple manager enable sdk settings location " your app your app " => " consent/push/analytics consent/push/analytics " => " analytics (general/ios/android/web) analytics (general/ios/android/web) " true 166,307 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type apple privacy / att settings location " your app your app " => " consent/push/analytics consent/push/analytics " => " privacy privacy " consent management settings location " your app your app " => " consent/push/analytics consent/push/analytics " => " consent management consent management " true 166,307 unhandled content type unhandled content type unhandled content type unhandled content type web integration enable sdk you can use the docid\ kmuf0oag3of3a46iup5q4 to edit the " experience config json " matomo is not explicitly enabled if a valid configuration of matomo is present in the " experience config json ", the sdk is integrated into the html document this can be either done as matomo javascript tracking client or as matomo tag manager the corresponding configurations differ as follows structure in experience config json matomo javascript tracking client { "purple" { "analytics" { "matomo" { "configuration" { "siteid" "provided by matomo", "endpointurl" "provided by matomo", "scriptsourceurl" "provided by matomo" } } } } } matomo tag manager { "purple" { "analytics" { "matomo" { "configuration" { "usetagmanager" "provided by matomo", "containersourceurl" "provided by matomo" } } } } } matomo javascript client true 176 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type matomo tag manager true 173 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type when using the matomo tag manager a further setup at matomo tag manager dashboard is needed please read on more here docid\ rbdqewiczw3sxfpdaadqp consent management if you use one of the cmps supported by purple, you must specify the cmp specific vendor id for matomo, which you can get from your cmp frontend additionally, the iab vendor id for matomo can also be added structure in experience config json javascript tracking client with consent { "purple" { "analytics" { "matomo" { "configuration" { "siteid" "provided by matomo", "endpointurl" "provided by matomo", "scriptsourceurl" "provided by matomo" }, "consent" { "vendorid" "provided by your cmp", "iabvendorid" "" } } } } } tag manager with consent { "purple" { "analytics" { "matomo" { "configuration" { "usetagmanager" "provided by matomo", "containersourceurl" "provided by matomo" } "consent" { "vendorid" "provided by your cmp", "iabvendorid" "" } } } } } consent true 186 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type