Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
154 commits
Select commit Hold shift + click to select a range
547df94
Rework Experience Monitoring ToC
cg-tw May 7, 2026
437a905
Rename plugin in workflow file
cg-tw May 7, 2026
4812a93
Remove hyphen
cg-tw May 7, 2026
cd02bd3
Change case again
cg-tw May 7, 2026
2343caa
Fix path
cg-tw May 7, 2026
9a25680
Fix case
cg-tw May 7, 2026
3dbde01
Use underscores for consistency
cg-tw May 7, 2026
c8863d3
Fix case
cg-tw May 7, 2026
8239329
Fix case
cg-tw May 7, 2026
b5afa7c
Revert changes to documentation.yaml (must be done in separate PR)
cg-tw May 7, 2026
bb03225
Merge branch 'staging' into MON-195903-experience-monitoring-toc-new
cg-tw May 7, 2026
03d0886
cxm rework
emgcentreon May 15, 2026
a1656d8
created missing topics - EMG
emgcentreon May 19, 2026
d652afb
fix sidebar
emgcentreon May 19, 2026
c59e304
fix sidebar
emgcentreon May 19, 2026
dec8a86
fix sidebar
emgcentreon May 19, 2026
2ddc662
Update "Getting to know EM" part
smau-centreon May 19, 2026
d05e15e
Update ToC
cg-tw May 29, 2026
cf23648
Merge branch 'staging' into MON-195903-experience-monitoring-toc-new
cg-tw May 29, 2026
5cae79a
readd network views
emgcentreon May 29, 2026
600d0c7
Updates
cg-tw Jun 1, 2026
e1877d3
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 1, 2026
b73e6db
ToC changes
emgcentreon Jun 1, 2026
57f766a
fix ToC
emgcentreon Jun 1, 2026
6ac623d
fix sidebar file
emgcentreon Jun 1, 2026
ca9c52f
Update (navigating XM)
cg-tw Jun 1, 2026
2c7ec30
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 1, 2026
4f412c8
fix spelling mistakes
emgcentreon Jun 1, 2026
3b2db12
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 1, 2026
f79e107
Troubleshooting
cg-tw Jun 1, 2026
3c19bec
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 1, 2026
ee370be
Small update
cg-tw Jun 2, 2026
25294d2
Changes following review
cg-tw Jun 2, 2026
364a14f
Rewrite understanding system tab indicators
cg-tw Jun 2, 2026
32ebc20
Updates following review
cg-tw Jun 2, 2026
72171a7
Update TOC (Using analysis data)
smau-centreon Jun 2, 2026
f667a89
Improve navigating in CXM page
cg-tw Jun 2, 2026
0803e37
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 2, 2026
f97d68d
reworked user journey sections
emgcentreon Jun 3, 2026
3d8e734
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 3, 2026
37e6503
fix broken links
emgcentreon Jun 3, 2026
def9868
corrections to user journey pages
emgcentreon Jun 3, 2026
ffc890a
Update
cg-tw Jun 4, 2026
a9063d0
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 4, 2026
9c5bb44
Merge branch 'staging' into MON-195903-experience-monitoring-toc-new
cg-tw Jun 4, 2026
2c10941
Remove old file that shouldn't be there
cg-tw Jun 4, 2026
4885f27
Remove leftover quantas
cg-tw Jun 4, 2026
f98904d
user journey corrections
emgcentreon Jun 4, 2026
1a87b5a
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 4, 2026
028ffc8
Changes following review
cg-tw Jun 5, 2026
37c80fd
Update
cg-tw Jun 5, 2026
d2ae103
Update
cg-tw Jun 5, 2026
3abc1f9
Update
cg-tw Jun 5, 2026
625c40d
imrpovements to DSS and user journeys
emgcentreon Jun 5, 2026
6de9182
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 5, 2026
57decff
unbreak build
emgcentreon Jun 5, 2026
fc204f7
improvements
emgcentreon Jun 5, 2026
6395809
corrections to digital sobriety and user journeys
emgcentreon Jun 5, 2026
f08e13e
add screenshots and other improvements
emgcentreon Jun 8, 2026
b578155
Changes following review
cg-tw Jun 8, 2026
f8afbc2
glossary entries
emgcentreon Jun 8, 2026
a6d71dd
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 8, 2026
80c12cb
new screenshots + getting started sections
emgcentreon Jun 9, 2026
6ac4f24
Update
cg-tw Jun 12, 2026
efd8222
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 12, 2026
7df139d
Apply suggestions from code review
emgcentreon Jun 12, 2026
f295fea
new screenshots + readd load test procedure
emgcentreon Jun 12, 2026
c383f8b
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 12, 2026
d317ff7
Update
cg-tw Jun 12, 2026
94bf26f
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 12, 2026
82d07f4
Fix build
cg-tw Jun 12, 2026
a590403
implementing feedback
emgcentreon Jun 16, 2026
8ff561b
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 16, 2026
0fb4fcb
implement feedbacks
emgcentreon Jun 16, 2026
824c19c
implement feedback
emgcentreon Jun 17, 2026
92e11c7
Add link
cg-tw Jun 18, 2026
bfd7b6c
Clean up level-1 titles
cg-tw Jun 18, 2026
ce4670b
using graphs topic
emgcentreon Jun 18, 2026
aa5d425
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 18, 2026
ae92b26
unbreak build
emgcentreon Jun 19, 2026
db93fa4
correct links
emgcentreon Jun 19, 2026
0fedd35
fix link
emgcentreon Jun 19, 2026
6aebb06
Merge branch 'staging' into MON-195903-experience-monitoring-toc-new
emgcentreon Jun 19, 2026
bf3cc6b
fix broken anchors
emgcentreon Jun 19, 2026
4aaf281
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 19, 2026
9434e09
fix broken anchor
emgcentreon Jun 19, 2026
1fb7081
FR Translation (RUM)
cg-tw Jun 22, 2026
4960e2f
FR translation (system data)
cg-tw Jun 22, 2026
895969b
Restore Monitor production events in EN + FR translation
cg-tw Jun 22, 2026
a4fd223
FR business data
cg-tw Jun 22, 2026
1e2afd6
FR business data (2)
cg-tw Jun 22, 2026
594d3e8
fix broken links
emgcentreon Jun 22, 2026
97110b4
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 22, 2026
a491885
Restore section about global view
cg-tw Jun 22, 2026
705b1b2
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 22, 2026
97118c4
fix broken links
emgcentreon Jun 22, 2026
44350a2
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 22, 2026
1c58bb6
Installation checklist FR
cg-tw Jun 22, 2026
c0595fe
Add dashboards topic in FR (to be translated)
cg-tw Jun 22, 2026
23c7f43
Add digital sobriety concepts topic in FR (to be translated)
cg-tw Jun 22, 2026
caaeee4
Try to unbreak build
cg-tw Jun 22, 2026
ba19f8f
Add Troubleshooting file in FR
cg-tw Jun 22, 2026
aa8b2ac
missing files
emgcentreon Jun 22, 2026
e666b47
Add missing files (FR)
smau-centreon Jun 22, 2026
95b4456
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
smau-centreon Jun 22, 2026
82758e3
resolve conflict
emgcentreon Jun 22, 2026
e1798a7
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 22, 2026
4877d45
Fix conflict
cg-tw Jun 22, 2026
020b9cc
Delete unused files
smau-centreon Jun 22, 2026
e5a1adf
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
smau-centreon Jun 22, 2026
631bc7b
Clean up frontmatter for welcome topic
cg-tw Jun 22, 2026
b9f755f
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 22, 2026
0a8dd17
Restore STM zones in ToC
smau-centreon Jun 22, 2026
bf5c622
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
smau-centreon Jun 22, 2026
446999a
Clean up level 1 topics
cg-tw Jun 22, 2026
a17f324
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 22, 2026
2bb3b4f
Merge branch 'staging' into MON-195903-experience-monitoring-toc-new
cg-tw Jun 22, 2026
9c434fc
Restore "Network data"
smau-centreon Jun 22, 2026
b7596f8
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
smau-centreon Jun 22, 2026
6f73f2d
resolved conflict
emgcentreon Jun 22, 2026
deaf4ab
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 22, 2026
f6b93c2
Add missing file
cg-tw Jun 22, 2026
5a52891
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 22, 2026
90e1ee6
Fix broken link
smau-centreon Jun 22, 2026
15637d5
images cleanup + digital sobriety translation
emgcentreon Jun 22, 2026
d0f3e55
Merge branch 'MON-195903-experience-monitoring-toc-new' of https://gi…
emgcentreon Jun 22, 2026
b489fc9
Unbreak build
cg-tw Jun 22, 2026
3c7a0f7
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 22, 2026
5e5c188
Unbreak build
cg-tw Jun 22, 2026
1c93f02
Fix anchor in CXM connector doc
cg-tw Jun 22, 2026
193a993
FR translations for headers
cg-tw Jun 22, 2026
3ef58b1
Update
cg-tw Jun 23, 2026
c3a6c24
FR network data
cg-tw Jun 23, 2026
5c5de8d
FR load tests
cg-tw Jun 23, 2026
60c811d
FR dashboards
cg-tw Jun 23, 2026
461c86c
FR users and rights + changes in ToC
cg-tw Jun 23, 2026
689d6d2
FR glossary
cg-tw Jun 23, 2026
45ea342
Translate STM section
smau-centreon Jun 23, 2026
b171294
Fix title
cg-tw Jun 23, 2026
477df4c
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 23, 2026
3e96b44
Fix broken links
smau-centreon Jun 23, 2026
9bd0da9
Update title
cg-tw Jun 23, 2026
19305be
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 23, 2026
4874e82
FR using graphs
cg-tw Jun 23, 2026
08d558e
Event markers cleanup
cg-tw Jun 23, 2026
a96e639
FR intro getting started
cg-tw Jun 23, 2026
d86bc95
Merge branch 'staging' into MON-195903-experience-monitoring-toc-new
cg-tw Jun 23, 2026
1145304
Fix anchors
cg-tw Jun 23, 2026
9f1b595
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 23, 2026
4433c86
Workaround for incorrect dead link
cg-tw Jun 23, 2026
6d8918f
translate digital sobriety + getting started
emgcentreon Jun 23, 2026
7cec080
fix conflicts
emgcentreon Jun 23, 2026
0257ecf
Workaround for incorrect dead link
cg-tw Jun 23, 2026
b80ff66
Merge branch 'MON-195903-experience-monitoring-toc-new' of github.com…
cg-tw Jun 23, 2026
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 experience-monitoring/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.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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 experience-monitoring/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.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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 experience-monitoring/assets/rum-comparison.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 experience-monitoring/assets/rum_more_details.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 experience-monitoring/assets/settings.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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 experience-monitoring/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](../configuration/manage-users-and-rights.md) (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.
63 changes: 63 additions & 0 deletions experience-monitoring/business-data/business-data-results.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
id: business-data-results
title: Understanding business data results
---

The Business Data module displays traffic and conversion metrics sourced from your analytics tool (Google Analytics or Matomo). Correlate the technical performance of your site and your sales. A key thing to do is to [plot events onto your graphs](../installation/monitor-production-events.md) so as to explain changes.

## Business data or RUM?

Business Data traffic refers to the traffic that customers typically view in their analytics. It is a filtered "business-specific" view, unlike [RUM](../rum/rum.md), which captures all raw traffic.

| Criterion | RUM in Experience Monitoring | Business data (Google Analytics) |
| --- | --- | --- |
| Traffic coverage | 100% of traffic (before GDPR pop-in) | Only visitors who have accepted GDPR consent |
| Bots | Included (US bots, crawlers, etc.) | Excluded (filtered in the GA view configured by the client) |
| GDPR consent | Independent of consent | Dependent on consent acceptance |
| Estimated difference | Full raw traffic | Approximately 1/3 of traffic missing (GDPR refusals + filtered bots) |
| Configuration | Managed in Experience Monitoring | Experience Monitoring retrieves the view as configured in GA (no additional processing) |

## Use cases

### Traffic + Performance Dashboard

Create a [dashboard](../performance-analysis/dashboards.md) that combines website traffic (from GA) with the execution speed of user journey scenarios. This allows you to monitor the overall health of the site at a glance: traffic and performance side by side.

### Impact of a deployment on sales

After a deployment, check whether a slowdown in the site has a negative impact on the conversion rate or revenue. Use in conjunction with [event tags](../installation/monitor-production-events.md) to date the deployment.

### Impact of a deployment on the bounce rate

Check whether a deployment (successful or failed) caused an increase or decrease in the bounce rate. Example: sudden spike in the bounce rate on a certain date, to be correlated with a possible slowdown.

## Metrics

The Business Data module displays the following metrics, all sourced from Google Analytics:

* Website traffic: number of sessions/visitors over the selected period. For non-monetized websites, only this metric is truly relevant.
* E-commerce conversion rate: for e-commerce sites, tracks conversion trends.
* Revenue per minute: revenue generated minute by minute.
* Number of transactions per minute: transaction volume over time.
* Revenue per session per minute: average revenue per session, minute by minute.
* Bounce rate: percentage of visitors leaving the site after viewing only one page.

> Google Analytics Delay: There is a delay of 4 to 24 hours between the data reported by GA and actual results. For example, a bounce rate of 90% may be adjusted within the next 48 hours. This delay is inherent to GA and not to Experience Monitoring.




<!--Centreon Experience Monitoring links with Analytics so you can:

Have your business KPIs correlating the technical performance and your sales.
See the impact of peak traffic on your page load time.
Measure the capacity and impact of your site's modifications on your architecture load (Infrastructure Cost Per Clic evolution)

In the **Business data** page, you can:

* **Overview** tab - Analytics summary over the period
* **Opportunities** tab

* Correlate Google Analytics data with Synthetic Monitoring data in the **Journey and revenues** tab (you need to have configured a user journey). You can see an estimation of losses due to downtime or slow loading pages.

* Correlate Google Analytics data with system data in the **Infrastructure cost/click** (you need to have configured an agent collecting [system data](../installation/servers/install-system-agents.md)).-->
Original file line number Diff line number Diff line change
@@ -1,10 +1,8 @@
---
id: enable-disable-scenario-or-alert-via-api
title: Automate enabling/disabling a scenario or an alert via API
title: Automate enabling/disabling a journey or an alert via API
---

## Preamble

In some situations it can be useful to modify Experience Monitoring's configuration automatically. Use cases are many, but the most common are:

- disabling or re-enabling a journey (for example disabling it during a site maintenance window so the maintenance period is excluded from downtime statistics)
Expand All @@ -14,7 +12,7 @@ In some situations it can be useful to modify Experience Monitoring's configurat

In Experience Monitoring, all features are accessible through the API, so you can send requests to Experience Monitoring using tools such as curl or wget by specifying the site ID, the User Journey ID and the authentication parameters (**x-csrf-token** and **_qm3k_session**).

Example REST request to disable a journey where the Experience Monitoring UI edit panel URL is https://app.quanta.io/app/settings/sites/29274/user-journey?ids=2913:
Example: a REST request to disable a journey for which the Experience Monitoring UI edit panel URL is https://app.quanta.io/app/settings/sites/29274/user-journey?ids=2913:

```bash
curl "https://app.quanta.io/api/sites/29274/uj/journeys/2913" -X 'PUT' \
Expand All @@ -24,7 +22,7 @@ curl "https://app.quanta.io/api/sites/29274/uj/journeys/2913" -X 'PUT' \
-H "x-csrf-token: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=" \
-H "content-type: application/json;charset=UTF-8" \
-H "cookie: _qm3k_session=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
--data-raw '{"user_journey":{id:"**29274**","enabled":**false**}}'
--data-raw '{"user_journey":{id:"**2913**","enabled":**false**}}'
```

## Implementation as a shell script
Expand Down
48 changes: 0 additions & 48 deletions experience-monitoring/configuration/configuration-checklist.md

This file was deleted.

15 changes: 0 additions & 15 deletions experience-monitoring/configuration/configure-digital-sobriety.md

This file was deleted.

44 changes: 17 additions & 27 deletions experience-monitoring/configuration/configure-google-analytics.md
Original file line number Diff line number Diff line change
@@ -1,46 +1,36 @@
---
---
id: configure-google-analytics
title: Configure Google Analytics with Experience Monitoring
---

## Frequently asked questions

### Why integrate Google Analytics into Experience Monitoring?
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.

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

**No**, Experience Monitoring is invisible to Google Analytics — we don't call the Google Analytics tag that runs on your site's pages.
> To connect/disconnect Experience Monitoring to/from Google Analytics, you must have [**Administrator** or **Owner** permissions](../configuration/manage-users-and-rights.md) on your Organization in Experience Monitoring.

Therefore your GA statistics are not affected by our probes.
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.

### Why don't I see Analytics data in Experience Monitoring?
To link Experience Monitoring with your Google Analytics 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.
1. Select the site for which you want to link the Google Analytics account (click its name).

### Why don't I have real-time Analytics data?
2. Click **Settings** (the gear icon at the top right of the screen), then click 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.
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.

### I accidentally disabled the Google Analytics module in Experience Monitoring. Can I recover history?
5. Once authenticated, you are redirected back to Experience Monitoring. Select the Google Analytics property 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 support via the "Help" button at the bottom-right of the app.

## Link Google Analytics to Experience Monitoring

With Experience Monitoring 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.
## Frequently asked questions

> To add/remove a link you must have "Administrator" or "Owner" permissions on your Organization in Experience Monitoring.
### Are Experience Monitoring probes counted in GA?

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.
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 link Experience Monitoring 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 see real-time Analytics data in Experience Monitoring?

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 Experience Monitoring, 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 [Centreon support](http://support.centreon.com/).
Loading
Loading