Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added cxm/assets/audit.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added cxm/assets/percentiles.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
38 changes: 38 additions & 0 deletions cxm/business-data/business-alerts.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
---
id: business-alerts
title: Business alerts
---

> Available by default on Business and Full licenses; optional on other plans.

Business alerting monitors the impact of site issues (for example drops in traffic or conversion) rather than a predefined list of causes.
They detect abnormal drops in traffic or conversion and let you analyze precisely when those drops occurred.

Because this data comes from Google Analytics, it is processed with a default 4-hour delay (GA data is refined over time).

## Prerequisites

* Users must have filled in their personal data (email, SMS, Slack) and defined the time periods during which they want to be notified or not.

## Creating business alerts

1. Go to **Settings > Alerting**.
2. In the **Business alerts** section, click **Add a business alert**, then select the alert type you want ([**Alert on conversion rate**](#conversion-rate-alerts) or [**Alerts on pageviews/mn**](#page-view-alerts)).
3. Name your alert and define which users should receive it. Select email, SMS or Slack.
4. If you want to define another notification channel than email, SMS or Slack, define the webhook to be used. This type of notifications are not linked to a user.
5. Hover over the alert's tile. 2 buttons appear:

* **Configure this alert's planning**: define the time periods during which alerts should be sent.
* **Configure this alert's thresholds**: define criteria for triggering an alert and a recovery notification.

### Conversion rate alerts

This checks whether your conversion rate average over a given period (2 hours by default) is lower compared to the same period historically (daily, weekly, or monthly baselines).

By default this alert triggers when the conversion rate drops by 30% compared to the usual value. A resolution notification is sent when the metric returns to 75% of the usual conversion rate.

You can also set a fixed conversion-rate threshold below which you want to be alerted.

### Page view alerts

This works the same way as conversion-rate alerts but is applied to page views per minute.
4 changes: 4 additions & 0 deletions cxm/business-data/business-data-results.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
---
id: business-data-results
title: Understanding business data results
---
44 changes: 20 additions & 24 deletions cxm/configuration/configure-google-analytics.md
Original file line number Diff line number Diff line change
@@ -1,46 +1,42 @@
---
id: configure-google-analytics
title: Configure Google Analytics with CXM
title: Configure Google Analytics with Experience Monitoring
---

## Frequently asked questions

### Why integrate Google Analytics into CXM?
By integrating Google Analytics data into Experience Monitoring, you can correlate web scenario execution times and technical metrics such as response time and server load with business data like traffic and conversions. This helps you analyze how traffic impacts page load times and draw meaningful conclusions.

Integrating this data allows you to correlate technical metrics (response time, server load, etc.) with your business data (traffic, conversion, etc.). These correlations help you draw meaningful conclusions.
## Link Google Analytics to Experience Monitoring

### Are CXM probes counted in GA?
> To connect/disconnect Experience Monitoring to/from Google Anaytics, you must have **Administrator** or **Owner** permissions on your Organization in Experience Monitoring.

**No**, CXM is invisible to Google Analytics — we don't call the Google Analytics tag that runs on your site's pages.
Here is a [video tutorial](https://www.youtube.com/watch?v=qmeXwypUmL4&list=PLgmedpAAxo-40d8PaBsaQS7Hkrm6mdxjs&index=3) that shows how to link Experience Monitoring to your Google account. You can also follow the procedure below.

Therefore your GA statistics are not affected by our probes.
To link Experience Monitoring with your Google Analytics account:

### Why don't I see Analytics data in CXM?
1. Click **Settings** (the gear icon at the top right of the screen).

Google Analytics data can take several hours to appear. Because we retrieve data via their API, we can only import data that is visible in GA.

### Why don't I have real-time Analytics data?
2. Select the site for which you want to link the Google Analytics account (click its name).

Google Analytics data can take several hours to appear. Because we retrieve data via their API, we can only import data that is visible in GA.
3. Go to the **Integrations** tab.

### I accidentally disabled the Google Analytics module in CXM. Can I recover history?
4. At the bottom of the **Business & Analytics** section, click **Connect**. You'll be redirected to Google's sign-in page — enter the credentials of the account you want to link.

No problem — we always import the last 24 hours of data. Wait a little and the data should appear.
5. Once authenticated, you are redirected back to Experience Monitoring. Select the Google Analytics property you want to use.

If you need to recover more than 24 hours of historical data, contact support via the "Help" button at the bottom-right of the app.
## Frequently asked questions

## Link Google Analytics to CXM
### Are Experience Monitoring probes counted in GA?

With CXM you can correlate your web scenario execution times with traffic measured by Google Analytics over the same period and analyze the effect of traffic on page load times.
No, Experience Monitoring is invisible to Google Analytics — we don't call the Google Analytics tag that runs on your site's pages. Therefore your GA statistics are not affected by our probes.

> To add/remove a link you must have "Administrator" or "Owner" permissions on your Organization in CXM.
### Why don't I see Analytics data in Experience Monitoring?

We have a [tutorial video](https://www.youtube.com/watch?v=qmeXwypUmL4&list=PLgmedpAAxo-40d8PaBsaQS7Hkrm6mdxjs&index=3) that shows how to link your quanta to your google account.
Google Analytics data can take several hours to appear. Because we retrieve data via their API, we can only import data that is visible in GA.

To link CXM with your Google Analytics account, go to the "Configuration" tab (gear icon at the top right), then select the site (click its name) for which you want to link the Google Analytics account.
### Why don't I have real-time Analytics data?

Go to the "Integrations" tab.
Google Analytics data can take several hours to appear. Because we retrieve data via their API, we can only import data that is visible in GA.

To create the link, click "Connect". You'll be redirected to Google's sign-in page — enter the account credentials you want to link.
### I accidentally disabled the Google Analytics module in Experience Monitoring. Can I recover history?

Once authenticated you are redirected back to CXM, your Analytics profiles are imported into the UI and you just need to choose the profile you want to use.
No problem — we always import the last 24 hours of data. Wait a little and the data should appear. If you need to recover more than 24 hours of historical data, contact our support team.
12 changes: 7 additions & 5 deletions cxm/how-to-articles/rum-blocked-by-csp.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,13 @@
---
id: rum-blocked-by-csp
title: A strict Content Security Policy (CSP) blocks the RUM data collection
title: Troubleshooting RUM
---

## A strict Content Security Policy (CSP) blocks the RUM data collection

In certain web environments with an enforced security policy ([Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP)), the Centreon Real User Monitoring (RUM) tag may require additional configuration. The issue is rare, but can prevent RUM data from being transmitted until the Quanta domains are correctly authorized.

## Symptom - RUM data is not being transmitted
### Symptom - RUM data is not being transmitted

If you have installed the Quanta RUM tag via GTM or Axeptio and you observe that:
- the Quanta script loads correctly,
Expand All @@ -14,7 +16,7 @@ If you have installed the Quanta RUM tag via GTM or Axeptio and you observe that

Your site uses a CSP that requires an update. This behavior is completely normal in environments where the security policy is strict (banking, advanced retail, sites under WAF/CDN, etc.).

## Issue - The RUM tag is blocked by a CSP
### Issue - The RUM tag is blocked by a CSP

CXM uses a script loaded from ``https://appstatic.quanta.io``, and then sends its performance metrics to ``https://rum-metrics.quanta.io``.
On the large majority of sites, this works automatically, including when the tag is installed via GTM, Axeptio or another manager. However, some sites implement an advanced Content Security Policy (CSP).
Expand All @@ -28,7 +30,7 @@ This is a security mechanism that precisely defines:

> In Chrome DevTools, this appears as ``blocked:csp`` on the ``beacon.gif`` type request.

## Solution - Add authorizations
### Solution - Add authorizations

To allow the RUM module to work while strictly respecting your security rules, simply add the two Quanta domains to the appropriate directives.

Expand All @@ -49,7 +51,7 @@ Even if the current beacon passes through ``img-src``, this addition ensures com
- future optimizations of the RUM API,
- enforced security environments.

## CSP adjustment example
### CSP adjustment example

Here is a schematic example (to be adapted to your existing configuration):

Expand Down
53 changes: 26 additions & 27 deletions cxm/installation/installation-checklist.md
Original file line number Diff line number Diff line change
@@ -1,49 +1,48 @@
---
id: installation-checklist
title: CXM Installation checklist
title: Experience Monitoring installation checklist
---

This list covers the requirements to ensure proper operation of CXM's different modules for a given site.
This list shows the requirements needed for Centreon Experience Monitoring's features to run properly on a given site. (Bear in mind that some features may not be included in your license.)

## User journeys
## User journeys/Synthetic monitoring (STM)

There is **nothing to install** because CXM connects to your application just like any regular user.
There is nothing to install because CXM connects to your application just like any regular user.

However, depending on the security level on your site, you may need to allow our IP addresses so that your anti-bot system does not block our probes. If that's the case, you'll find the procedure here:
However, depending on the security level on your site, you may need to allow our IP addresses so that your anti-bot system does not block our probes. If that's the case, you'll [find the procedure here](./cxm-ip-addresses.md).

[CXM IP addresses](./cxm-ip-addresses.md)
## Real User Monitoring (RUM)

## Real User Monitoring
Real User Monitoring installs like any marketing tag: by inserting a JavaScript tag into your site's HEAD element. For the full procedure and installation instructions, see: [Install Real User Monitoring](./real-user-monitoring-installation.md).

Real User Monitoring installs like any marketing tag: by inserting a JavaScript tag. For the full procedure and installation instructions, see:
## Digital sobriety

[Install Real User Monitoring](./real-user-monitoring-installation.md)
Digital sobriety scores are calculated from STM and RUM data. If STM and RUM are properly installed and configured, no additional installation is required.

## System agent
## Analyze a site's business data (Google Analytics/Matomo)

CXM's system functionality requires at minimum the installation of system agents, then adding modules depending on the level of detail required or allowed by your license.
To correlate your business data with other Experience Monitoring data, you need to [link your Google Analytics or Matomo account to Experience Monitoring](../configuration/configure-google-analytics.md).

### Minimal installation
## System data: monitor the health of your host server

To install the system agents, follow the detailed procedure here:
To monitor the health of your host server, you need to install a system agent on it. Additional modules can be added depending on the level of detail you need or your license allows.

[Install system agents](./servers/install-system-agents.md)
* [Install the system agent](./servers/install-system-agents.md) to retrieve basic information about your server.
* After the agent is installed, you can install additional modules:

### Installation for advanced metrics
* If your application runs on Apache, MySQL, Varnish (...), [install a dedicated agent](./servers/add-advanced-metrics.md) to collect data from those services.
* If you are using a PHP application (e.g. Magento or OroCommerce), [install the PHP profiler](./servers/install-php-magento-orocommerce-profiler.md).

After the agent is installed, you can install additional modules:
## Check a site's network performance

- Application agents for Apache, MySQL, Varnish, … to obtain information specific to those services:

[Add advanced metrics](./servers/add-advanced-metrics.md)

- The profiler, compatible with any PHP application such as Magento or OroCommerce:

[Install the PHP / Magento / OroCommerce profiler](./servers/install-php-magento-orocommerce-profiler.md)

You don't need to do anything - data appears automatically on the **Network data** page.

## Automatic events
## Run a load test

You can add events manually in the UI, or automatically via the API. **This is especially useful when you deploy a new version of your site.** We recommend setting this up so changes are recorded in CXM.
You don't need to install anything to be able to run load tests. You just need to configure a user journey.

[Automatically track production deployment events](./monitor-production-events.md)
<!--
## Adding events markers to your graphs

To help you analyze Experience Monitoring data and explain changes in behavior, you can [add event markers to graphs manually (or automatically via the API)](./monitor-production-events.md). The typical use case is deploying a new version of your site.
-->
60 changes: 28 additions & 32 deletions cxm/installation/real-user-monitoring-installation.md
Original file line number Diff line number Diff line change
@@ -1,56 +1,52 @@
---
id: real-user-monitoring-installation
title: Install Real User Monitoring
title: Installing RUM
---

## GDPR considerations

Although CXM uses a cookie, **no consent is required.**
Real User Monitoring (RUM) requires inserting a JavaScript tag into your site's pages.

The CNIL (French data protection authority) exempts certain cookies from requiring consent under these conditions:
## Procedure

- they have a limited purpose such as measuring performance, detecting navigation issues, optimizing technical performance or usability...
- they produce only anonymous statistics
- they are not cross-referenced with other datasets
- they are not transmitted to third parties
- they do not enable tracking a user's browsing across other websites.

**CXM meets these conditions.**
1. To retrieve your application's RUM tag, go to **Configuration > Integrations**:

You can find CNIL's recommendations on [this page](https://www.cnil.fr/fr/cookies-et-autres-traceurs/regles/cookies-solutions-pour-les-outils-de-mesure-daudience).
![image](../assets/installation/install-rum-1.png)

## Find the tag to insert on my site
The tag is displayed on the screen with a copy button.

Real User Monitoring (RUM) requires installing a JavaScript tag. The tag is available in the application. To retrieve it, go to **Configuration > Integrations**:
![image](../assets/installation/install-rum-2.png)

![image](../assets/installation/install-rum-1.png)
2. Insert the tag into your site's HEAD section. The operation can be done manually by a developer, or alternatively it can be added to a tag manager such as GTM by following the procedure below.

You will then find the tag on that screen with a button to copy it easily:
3. Go to **Real User Monitoring**. You should see data appear in a matter of minutes.

![image](../assets/installation/install-rum-2.png)
### Using GTM to add a Centreon RUM tag to your pages

This tag should be inserted into the site's HEAD section. The operation can be done manually by a developer, or alternatively **it can be added to a tag manager such as GTM by following the procedure below**.
1. Create a new tag: sign in to your GTM account and select the container for your website. Click "Add a new tag."

### Using GTM to add a CXM tag to your pages
2. Configure the tag:

**1 — Create a new tag**
1. Select "Custom HTML Tag" as the tag type.
2. Paste the script provided into the HTML field.
3. Ensure the script type is correctly set to "JavaScript" if required. GTM usually handles this automatically, but it's good to check.

Sign in to your GTM account and select the container for your website. Click "Add a new tag."
3. Set triggers: choose when you want the script to execute. You can apply it to all pages or to specific pages depending on your needs. Triggers allow precise control over when the script runs.

**2 — Configure the tag**
4. Save and test the tag: after configuring the tag and its triggers, save it and use GTM's preview feature to test whether the script works as expected on your site. This lets you see changes in real time without affecting real visitors.

Select "Custom HTML Tag" as the tag type.
Paste the script provided into the HTML field.
Ensure the script type is correctly set to "JavaScript" if required. GTM usually handles this automatically, but it's good to check.
5. Publish the changes: once you've checked everything works correctly, remember to publish the changes in GTM so the script is active on your live site.

**3 — Set triggers**
## GDPR considerations

Choose when you want the script to execute. You can apply it to all pages or to specific pages depending on your needs. Triggers allow precise control over when the script runs.
Although CXM uses a cookie, **no consent is required.**

**4 — Save and test the tag**
The CNIL (French data protection authority) exempts certain cookies from requiring consent under these conditions:

After configuring the tag and its triggers, save it and use GTM's preview feature to test whether the script works as expected on your site. This lets you see changes in real time without affecting real visitors.
- they have a limited purpose such as measuring performance, detecting navigation issues, optimizing technical performance or usability...
- they produce only anonymous statistics
- they are not cross-referenced with other datasets
- they are not transmitted to third parties
- they do not enable tracking a user's browsing across other websites.

**5 — Publish the changes**
**CXM meets these conditions.**

Once you've checked everything works correctly, remember to publish the changes in GTM so the script is active on your live site.
You can find CNIL's recommendations on [this page](https://www.cnil.fr/fr/cookies-et-autres-traceurs/regles/cookies-solutions-pour-les-outils-de-mesure-daudience).
22 changes: 0 additions & 22 deletions cxm/performance-analysis/basic-actions/how-alerts-work.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,25 +52,3 @@ Examples:
You can also trigger an alert when a scenario exceeds a fixed duration you set.

By default, these alerts are sent when the deviation occurs at least 15 times within a 25-minute window. They are marked as resolved once the deviation stops for at least 20 out of those 25 minutes.

## Business data alerts

> Available by default on Business and Full licenses; optional on other plans.

Scenarios help detect many site issues, but it's difficult to cover every possible anomaly with a scenario. Business alerting monitors the impact (for example drops in traffic or conversion) rather than a predefined list of causes.

Business alerts detect abnormal drops in traffic or conversion and let you analyze precisely when those drops occurred.

Because this data comes from Google Analytics, it is processed with a default 4-hour delay (GA data is refined over time).

### Conversion rate alerts

This checks whether your conversion rate average over a given period (2 hours by default) is lower compared to the same period historically (daily, weekly, or monthly baselines).

By default this alert triggers when the conversion rate drops by 30% compared to the usual value. A resolution notification is sent when the metric returns to 75% of the usual conversion rate.

You can also set a fixed conversion-rate threshold below which you want to be alerted.

### Page view alerts

This works the same way as conversion-rate alerts but is applied to page views per minute.
Loading
Loading