PHPackages gene/module-newrelic-rum-page-type - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Logging & Monitoring](/categories/logging) 4. / 5. gene/module-newrelic-rum-page-type ActiveMagento2-module[Logging & Monitoring](/categories/logging) gene/module-newrelic-rum-page-type ================================== Track pageType in New Relic Real User Monitoring 1.0.2(10mo ago)15413↓50%LGPL-3.0-onlyPHPPHP ~7.4.0||~8.1.0||~8.2.0||~8.3.0||~8.4.0CI passing Since Dec 3Pushed 9mo ago3 watchersCompare [ Source](https://github.com/genecommerce/module-newrelic-rum-page-type)[ Packagist](https://packagist.org/packages/gene/module-newrelic-rum-page-type)[ RSS](/packages/gene-module-newrelic-rum-page-type/feed)WikiDiscussions main Synced 1mo ago READMEChangelog (2)Dependencies (1)Versions (4)Used By (0) gene/module-newrelic-rum-page-type ================================== [](#genemodule-newrelic-rum-page-type) Install this module to easily monitor and improve customer experience by tracking [Core Web Vitals](https://web.dev/articles/vitals) in New Relic by page type and enhancing your [RUM](https://newrelic.com/blog/best-practices/what-is-real-user-monitoring) setup. 🎉 If you are hosted on Adobe Commerce Cloud you already have New Relic with browser monitoring available! 🎉 Why install it? --------------- [](#why-install-it) By default New Relic is already tracking LCP, INP, and CLS on page views. This is recorded and queryable within New Relic. However you can only filter by some default values like `domain` or `pageUrl`. This granularity is insufficient for tracking changes and making targeted improvements on your ecommerce site. To be able to make impactful changes we need to tbe able to answer questions like - What are customers experiencing on the whole domain? - What are customers experiencing on product pages? - What are customers experiencing in the checkout? By adding this module you will have this level of detail and be able to make more informed decisions and stay ahead of any regressions. Installation ------------ [](#installation) ``` composer require gene/module-newrelic-rum-page-type bin/magento setup:upgrade ``` How it works ------------ [](#how-it-works) This module adds a custom attribute to the New Relic PageViewTiming data to set the current request type as `pageType`. This allows you to query the tracked data in segments like - `cms_index_index` - the homepage - `catalog_product_view` - product pages - `catalog_category_view` - listings pages - `checkout_index_index` - the checkout How to use ---------- [](#how-to-use) ### 1. Prepare a New Relic dashboard [](#1-prepare-a-new-relic-dashboard) It is best to view this data within a New Relic dashboard. We have prepared a dashboard template for you to get started with 1. Copy the contents of `dev/new-relic-cwv-dashboard.json` into a text editor 2. Replace the dummy `1234567` account ID with your actual New Relic account ID 3. Replace `www.example.com` with your actual domain. 4. Log into New Relic 5. On the left panel click "Dashboards" 6. On the top right click "Import Dashboard" 7. Paste in the prepared JSON dashboard and import the "Core Web Vitals by PageType" dashboard. 8. You will now see a dashboard highlighting your Core Web Vitals. This LCP/INP/CLS charts have a horizontal target line, your web vitals for desktop and mobile should be below this target line. [![New Relic Dashboard showing core web vitals with pageType filter](dev/filter-by-pagetype.png "New Relic Dashboard showing core web vitals with pageType filter")](dev/filter-by-pagetype.png) ### 2. Deploy this module to production [](#2-deploy-this-module-to-production) 1. Install this module on production. PageViewTiming metrics within New Relic will now have their `pageType` value attached. 2. Give it at least 24 hours for data to start filtering through, depending on your site and setup you may find patterns that some periods are slower when imports/exports are being triggered. ### 3. Make improvements for specific pageTypes [](#3-make-improvements-for-specific-pagetypes) 1. When no filter is applied you can see the overall scores for your website, as well as other key pageTypes. 2. By filtering through `catalog_product_view`, `catalog_category_view`, etc you can identify areas for improvement and whether they are most significantly affecting desktop or mobile devices. 3. Use the [Chrome Performance Panel](https://developer.chrome.com/docs/devtools/performance/overview) 1. Compare your experience to the experience of real users 2. Configure your environment to better match that of the real users 3. Investigate the additional panels, in particular the "rendering panel" can be very useful in improving CLS 4. After you deploy a fix it may take some time for it to become fully visible in your dashboard graphs. ### 4. Set up automated alerting [](#4-set-up-automated-alerting) 1. After you have improved your web vitals you want to monitor them to prevent regression. 2. From the dashboard click `...` on the top right of CLS/INP/LCP 3. Create an alert condition 4. Follow instructions from Tips 1. Alerting on a 24-hour rolling window seems to be the most stable. 2. Have an alert for desktop, and one for mobile. 3. Have alerts for specific page types, so that you are quickly alerted when something goes awry. 4. Alerts can fire even when no deployments are made, changes in audience, third party tracking, or A/B testers may be the cause. Caveats ------- [](#caveats) New Relic RUM is not as complete as some other offerings, most notably it is missing [LoAF](https://support.newrelic.com/s/hubtopic/aAXPh0000007Zgz/browser-monitoring-interaction-to-next-paint-inp-loaf-support). However, if you already have New Relic and are not currently looking at your RUM data then this module may be enough to get you kick-started on that journey and making targeted improvements. ### Health Score 40 — FairBetter than 88% of packages Maintenance56 Moderate activity, may be stable Popularity24 Limited adoption so far Community11 Small or concentrated contributor base Maturity58 Maturing project, gaining track record Bus Factor1 Top contributor holds 88.9% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~109 days Total 3 Last Release 307d ago PHP version history (2 changes)1.0.0PHP ~7.4.0||~8.1.0||~8.2.0||~8.3.0 1.0.1PHP ~7.4.0||~8.1.0||~8.2.0||~8.3.0||~8.4.0 ### Community Maintainers ![](https://www.gravatar.com/avatar/aa904d0f61196b12bd6727175110ad7a58e19d888960279e7e4b9dbb636f34b9?d=identicon)[convenient](/maintainers/convenient) ![](https://www.gravatar.com/avatar/112fb744acca7c0c63cf0282b4f447d8f1c1703ea1330c115eb1a135435d17ff?d=identicon)[genecommerce](/maintainers/genecommerce) --- Top Contributors [![convenient](https://avatars.githubusercontent.com/u/600190?v=4)](https://github.com/convenient "convenient (16 commits)")[![cjnewbs](https://avatars.githubusercontent.com/u/1676494?v=4)](https://github.com/cjnewbs "cjnewbs (2 commits)") ### Embed Badge ![Health badge](/badges/gene-module-newrelic-rum-page-type/health.svg) ``` [![Health](https://phpackages.com/badges/gene-module-newrelic-rum-page-type/health.svg)](https://phpackages.com/packages/gene-module-newrelic-rum-page-type) ``` ### Alternatives [justbetter/magento2-sentry Magento 2 Logger for Sentry 1851.5M3](/packages/justbetter-magento2-sentry)[graycore/magento2-stdlogging A Magento 2 module that changes all logging handlers to stdout 2382.6k](/packages/graycore-magento2-stdlogging)[itonomy/module-admin-activity A continuation of The Admin Activity extension by KiwiCommerce. This extension makes it easy to track all admin activity and revert the modification. 1270.4k](/packages/itonomy-module-admin-activity)[ampersand/magento2-log-correlation-id Magento 2 correlation id for requests and logs 279.9k](/packages/ampersand-magento2-log-correlation-id)[mage-os/module-admin-activity-log The Admin Activity extension makes it easy to track all admin activity with comprehensive audit logging. 261.4k](/packages/mage-os-module-admin-activity-log)[graycore/magento2-graphql-logger 106.6k](/packages/graycore-magento2-graphql-logger) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)