# Reduction of tracking anomalies through monitoring

### 1. Business value: Continuous auditing at a controlled cost

Sampling monitoring allows you to detect technical regressions on your website in real time, without using up your entire event quota.

* **Proactive detection**: Identify DataLayer breaks as soon as they occur.
* **Cost optimisation**: 1% sampling is sufficient to obtain an accurate picture of the technical health of the site.
* **Marking plan reliability**: Certify that your data is compliant before it is used by your analytics (GA4, Mixpanel) or advertising (Meta, Google Ads) tools.

### 2. Implementation methodology

#### Step A: OneTag configuration and sampling

OneTag captures browser data and relays it to the server side.

* **Action**: Configure OneTag in your TMS container.
* **Sampling**: Add a trigger condition (e.g. 1 hit out of 100) to limit data sending while maintaining a relevant statistical basis.
* **Documentation**: [Tutoriel OneTag](https://doc.commandersact.com/getting-started/integrating-your-data/onetag-tutorial).

#### Step B: Defining the Event Specification

This is your data contract that defines the validation rules.

* **Action**: Create your event schemas (e.g., purchase, view\_item). Define the required fields and expected formats (e.g., price must be a ‘number’).
* **Documentation**: [Event Specification](https://doc.commandersact.com/features/data-quality/event-specification).

#### **Step C: Analysis via the Data Quality Report**

The system compares the sampled hits to your specifications.

* **Analysis**: The dashboard displays a quality score. You can immediately see which events are invalid.
* **Documentation**: [Data Quality Monitoring](https://doc.commandersact.com/features/data-quality/data-quality).

#### **Step D: Proactive Alerting**

Don't put up with errors any longer; receive a notification as soon as quality deteriorates.

* **Configuration**: In Platform X, create an alert based on your Data Quality score.
* **Alert threshold:** For example, be notified if the compliance rate for the purchase event falls below 95% over a 15-minute period.
* **Channels**: Receive the alert instantly by email or via a Slack/Microsoft Teams integration for your technical teams.

### 3. Typical use cases

1. **Production Alert**: After deploying a new version of the site, if the price format accidentally changes in the DataLayer, your technical team receives a Slack alert within minutes.
2. **Partner Monitoring**: Detect if a partner tag starts sending non-compliant or poorly structured data via OneTag.
3. **Consent Control**: Be alerted if sampled events are reported when the user has not given their consent (opt-out), ensuring your GDPR compliance.

### Is your monitoring in place?

Setting up proactive alerting is the best way to sleep soundly after a release. Our experts will help you configure your tolerance thresholds and notification channels. **Contact our support team:** <support@commandersact.com>