---
title: How to enable the whitelist feature in Matomo
slug: experience/how-to-enable-the-whitelist-feature-in-matomo
docTags: 
createdAt: 2025-03-06T15:56:25.178Z
---

# How to enable the whitelist feature in Matomo

The motivation for the whitelist feature is that only data from known sources is accepted in Matomo and can be done in the Matomo site configuration.

## Get the package name from your app



![](https://api.archbee.com/api/optimize/ygR6KtT9QI_R0u3uKTJsm/0zpeneaEPAV3uHa34EuVl_matomo-wl-packagename.png)

The resulting package name is:

"<font color="#2166ae">**com.purplepublish.purpledocumentationapp**</font>"

:::hint{type="warning"}
Please note that Android and iOS can have different package names, due to structures that have grown over time. In this case, URLs with both package names must be stored in the Matomo site configuration.
:::

## Understanding the structure of sent URLs by native apps

Since within native apps are not URLs, existing PXP defines some structures on how to create&#x20;

### Action events

The structure of the sent URL for action events is:

<font color="#2166ae">**https://{package_name_of_the_app}/{event_name}**</font>

:::hint{type="info"}
**Example**

The triggered action event is "<font color="#2166ae">app_bookmark_added"</font> and this results in the URL as follows being sent:

<font color="#2166ae">**https://com.purplepublish.purpledocumentationapp/app_bookmark_added**</font>
:::

### View events

For view events, the path-template can be configured as a "path" or a "full URL".

:::CodeblockTabs
path

```json
"APP_MENU": {
  "templates": {
    "path": "/app_menu",
    "title": "App/Menu"
  }
}
```

full URL

```json
"APP_MENU": {
  "templates": {
    "path": "https://com.purplepublish.custom/app/any_path",
    "title": "App/Menu"
  }
}
```
:::

**a) When configured as path**

The template structure of the sent URL for view events is:

<font color="#2166ae">**https://{package_name_of_the_app}/{path}**</font>

:::hint{type="info"}
**Example**

The triggered view event is "<font color="#2166ae">**/app/appmenu"**</font> and this results in the URL as follows being sent:

<font color="#2166ae">**https://**</font><font color="#2166ae">**com.purplepublish.purpledocumentationapp**</font><font color="#2166ae">**/app/appmenu**</font>
:::

**b) When configured as URL**

The template structure of the sent URL for view events is:&#x20;

<font color="#2166ae">**{path}**</font>

:::hint{type="info"}
**Example**&#x20;

The triggered view event is "<font color="#2166ae">**https://com.**</font><font color="#2166ae">**purplepublish**</font><font color="#2166ae">**.custom/app/any_path"**</font> and this results in the URL as follows being sent:

<font color="#2166ae">**https://com.**</font><font color="#2166ae">**purplepublish**</font><font color="#2166ae">**.custom/app/any_path**</font>
:::

## Enable and setup Whitelist-Feature in Matomo&#x20;

### Matomo-Site created for the Website

A new or existing Matomo site configuration regarding the whitelist feature could look like this. In this example, it was previously created for a website.

![](https://api.archbee.com/api/optimize/ygR6KtT9QI_R0u3uKTJsm/F6zrjHKFME1gfxkqKXwNa_matomo-wl-setting-start.png)

### Add URLs sent by native apps and enable whitelist.

Now the URLs for the native apps must be added, and the whitelist feature activated via a checkbox.

![](https://api.archbee.com/api/optimize/ygR6KtT9QI_R0u3uKTJsm/cONCab8msCAy4d1LvDukZ_matomo-wl-setting-enabled.png)

