3rd party integrations
...
Purple Tracking
Tracking Services

Matomo

22min

Summary

Official websites

Site

URL

Website

Documentation

Developer integrations

(*) Available since PXP 3.8

Tracking service

Event support matrix

Overview of the supported events and their configuration.



Templates

Parameter

Actions

category action name value

not supported

Views

path title

not supported

Purchases* **

category action name value product_name product_category

not supported

Attributes

id

not supported

(*) 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 are supported for native apps only

General structure in tracking_config.json

Tracking service key name in "tracking_config.json" is: "matomo"

General structure


Event configuration

Actions

Matomo supports action events.

Action event
Example


Templates

Templatey key

Required

Template value

category

yes

The category of the event.

action

yes

The action of the event.

name

no

The name of the event.

value

no

Must be value that can be parsed as floating point number.

Views

Matomo supports view events.

View event
Example 1
Example 2


Templates

Templatey key

Required

Template value

path

yes

Must be a path like in a website.

title

yes

The title of the path.

Purchases

Matomo supports purchase events.

Purchase event
Example


Templates

Matomo offers a specific API to track purchases. Tracking purchase events takes place in two steps:

  1. An event is sent with the value of the price
  2. An additional order item is tracked

(1) Templates used for the event:

Templatey key

Required

Template value

category

yes

The category of the event.

action

yes

The action of the event.

name

no

The name of the event.

(2) Templates used for the order item:

Templatey key

Required

Template value

product_name

no

The name of the product.

product_category

no

The category of the product.

The order item is sent with some additional values:

API

Value

productId

The product id of the purchase.

price

The price of the product.

transactionId

The transaction id of the purchase if available.

quantity

1

Attributes

Matomo supports attributes.

Attribute
Example


Templates

Templatey key

Required

Template value

id

yes

The id of the attribute.

Must be value that can be parsed as integer number.

Additional supported functionality

Custom User ID

Purples generated device id is used for the custom user id (a custom user id is set for native apps only).

How to configure

Native Purple App

Any native Tracking Service is configured in the Purple Manager.

Enable SDK

Settings location

"Your app" => "Consent/Push/Analytics" => "Analytics (General/iOS/Android/Web)"

Setting

Description

Enable Matomo

To enable the Matomo SDK in your app, activate this checkbox.

Matomo URL

The Matomo URL provided by Matomo.

Matomo Site ID

The Matomo Site id provided by Matomo.

Apple privacy / ATT

Settings location

"Your app" => "Consent/Push/Analytics" => "Privacy"

Consent management

Settings location:

"Your app" => "Consent/Push/Analytics" => "Consent Management"

Setting

Description

Vendor-ID for Matomo

The Vendor-ID is provided by the consent management platform.

Web integration

Enable SDK

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.

Structure in experience.config.json

Plugin configuration


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.

Updated 21 Oct 2024
Did this page help you?