5. 🕵️ Data Processing, Filtering & Privacy

This section controls how the raw data collected by the JaJuMa Real User Monitoring (RUM) extension for Magento 2 is cleaned, enriched, filtered, and prepared for analysis in the RUM Dashboard.
These settings are crucial for ensuring data quality and meeting privacy requirements like GDPR.

5.1 🔐 Privacy & GDPR Compliance

• Anonymize IP
  This setting anonymizes visitor IP addresses to comply with local privacy laws and guidelines.

  Why this matters:
  This is a core feature for GDPR compliance. When set to Yes, the extension will not store the fully qualified IP address of your visitors, providing essential user privacy.
  This allows you to gather valuable performance metrics without collecting personally identifiable information (PII), greatly simplifying your privacy compliance obligations.

🔐 Use Case: Effortless GDPR Compliance
To comply with strict privacy regulations like GDPR, you need to avoid storing personally identifiable information without explicit consent. By enabling "Anonymize IP," you can continue to gather vital country-level performance data and user metrics while automatically ensuring that the full IP address, which can be considered PII, is never stored in your database.

5.2 🔑 Ensuring Data Quality: Filtering & Blacklists

Accurate reporting depends on filtering out irrelevant traffic from bots, crawlers, and internal testing.

• Use Default User-Agent Filter
  When enabled, a predefined, internal blacklist of common bot and scanner user-agents is applied to filter out spam and non-human traffic.

  Why this matters: This feature ensures your performance metrics reflect genuine customer interactions, not automated traffic. It is highly recommended to keep this enabled to avoid skewed data.

• User Agents Blacklist
  Exclude specific user-agents from data processing using a comma-separated list of Regular Expressions (RegEx).

• IPs Blacklist
  Exclude specific IP addresses from data processing using a comma-separated list of IPs.

🔑 Use Case: Ensuring Clean Data
Your marketing agency and internal developers visit your site daily.
To prevent their sessions from skewing your real customer data, add your office and agency IP addresses to the blacklist.
This ensures your performance metrics purely reflect the genuine customer experience.

5.3 🌎 Geolocation & Data Enrichment

• Geocode IP to Country
  When enabled, this feature attempts to geocode visitor IP addresses to the country of origin. Note that this feature is currently for manual data analysis and is not yet used in the RUM Dashboard reports.

  To use this feature, you must first install the required library via composer:

  composer require maxmind-db/reader

  You must also upload an IP-to-Country geocode database file. We recommend one of the following:

  • DB-IP (Free): Download the latest database (the .mmdb file).
  • MaxMind (Requires Signup): Offers databases that promise more accurate data.

5.4 📊 Configuring Report Segmentation

These settings define the dimensions by which your RUM data is aggregated. Enabling more segments provides more powerful drill-down capabilities in the dashboard but requires more server resources for processing.

• Process Reports for Stores:
  Select the specific Store Views for which reports should be generated.
  It's recommended to only select the levels you actively monitor to conserve server resources.
• Process Reports for Custom Layouts:
  By default, reports are segmented by standard Magento layouts (e.g., cms_index_index, catalog_product_view).
  You can add custom layouts here for more granular reporting on specific page types.
• Segmentation by Devices, Browsers, Navigation Types, and First Visits:
  These toggles allow you to enable or disable report processing for different segments. While it's recommended to keep all enabled for the most detailed insights, you can disable segments that are not of interest to save server resources.

5.5 🚀 Performance Tuning for Data Processing

• Number of Threads
  This setting defines the number of CPU cores that will be used for data processing.

  Why this matters:
  If your server has multiple CPU cores available, you can significantly speed up the data processing cron job by setting this value higher than 1.
  This allows the extension to process data in parallel, reducing the time it takes for new data to appear in your dashboard.

📞 Need Help?

Still have questions or need help with your configuration? Our expert team is here to assist. Please don't hesitate to contact our support team for personalized assistance.