
Hidden in Plain Sight: Why B2B Brands Need to Rethink How They Use New Relic’s RUM Data
In the B2B world, every second counts, but not always in the ways you expect. A procurement officer placing a repeat order before a site visit. A field sales rep building a quote on their phone between client meetings. A production manager logging into an account dashboard to check delivery schedules.
These aren’t hypothetical scenarios. They’re the everyday reality of how B2B buyers use your site, and in each of them, performance is silent currency. When your platform responds instantly, those moments disappear into the background and the order moves forward. When it doesn’t, the cost isn’t just in seconds lost - it’s in disrupted workflows, missed revenue, and weakened trust.
Which brings us to an uncomfortable truth: we see a lot of B2B brands flying blind when it comes to measuring performance where it matters most.
![]() | ![]() |
The Blind Spot You Didn’t Know You Had
If you’re running Adobe Commerce Cloud, there’s a good chance you’re already paying for Real User Monitoring (RUM) via New Relic. It’s bundled in, but in countless platform audits, we’ve found merchants who either:
Don’t realise they have access to it; or
Have it switched on, but are only scratching the surface of what it can do.
Out of the box, New Relic tracks Core Web Vitals like LCP, INP, and CLS - the very signals Google uses to measure real-world user experience. That’s useful. But it treats your site as a single, monolithic entity.
The problem? In B2B, your site is not one thing. It’s a collection of distinct, revenue-critical experiences:
Quick-order forms
Account dashboards
Quote request flows
Complex product detail pages with technical documentation and spec sheets
Checkout processes with purchase orders and split shipping
When performance is averaged across all of these, the signals flatten out. A lightning-fast homepage can hide a sluggish account area. A high-performing category page can mask a slow-loading checkout. The truth is lost in the noise.
Why This Matters Even More in B2B
B2B eCommerce isn’t just “B2C with bigger carts”. It’s a different animal entirely:
Your customers are professionals on a mission - they value efficiency over aesthetics.
Delays compound - slow performance in one stage of the buying process often means the customer has to break context and come back later, risking order abandonment.
The stakes are higher - a failed checkout isn’t just one missed sale; it could mean a lost annual account.
In this environment, not knowing where performance is breaking down is like running a factory without knowing which machines are stalling. You can’t fix what you can’t see.
![]() | ![]() |
The GENE Approach: Intelligent Innovation
We believe in solving problems elegantly, not expensively. That’s why we created something deceptively simple that changes the game: the gene/module-newrelic-rum-page-type
module.
Here’s what it does:
It adds a single attribute - pageType
- to every PageViewTiming event New Relic tracks, based on the Magento route. That’s it. But that single addition transforms how you can work with your RUM data.
With it, you can break down performance by:
cms_index_index
- Homepagecatalog_category_view
- Category pagescatalog_product_view
- Product detail pagescheckout_index_index
- CheckoutCustom B2B routes like quick-order, account dashboard, or quote request
And because it works with the New Relic Browser monitoring you already have in Adobe Commerce Cloud, there’s no extra licensing and no extra cost.
As our Head of Engineering, Luke Rodgers, puts it:
“It’s a misstep Adobe doesn’t include this by default. It won’t replace full tooling like RUMvision, but if you’re already paying for the tool, why not use it?”
What This Means for Your B2B Operation
Once installed, the shift in visibility is immediate:
You can see which specific workflows slow down under load.
You can compare desktop vs mobile performance for your most-used B2B features.
You can monitor how site updates affect specific buying journeys.
You can set precise, meaningful alerts (e.g., INP on Quick Order page > 200ms on mobile).
This goes far beyond technical curiosity. It’s about aligning performance work with commercial priorities, allowing you to see exactly which pages are underperforming. Once you have that information, you can prioritise fixes that protect revenue, safeguard key accounts, and improve the daily experience of your most valuable customers.
The Origin Story: Built for Real Needs, Shared Freely
Like many of our innovations, this wasn’t dreamt up in a product planning meeting. It came from our Unlimited Support team, working in the trenches with B2B merchants every day. We built it because we needed it, and because without it, our performance dashboards were telling an incomplete story.
And in keeping with our belief in Radical Collaboration, we made it public. No licensing fees, no “pro” tier, no hidden strings. Just a tool we knew would be as useful to the broader Adobe Commerce ecosystem as it was to us.
![]() | ![]() |
How to Get Started
Installation is refreshingly simple:
composer require gene/module-newrelic-rum-page-type
bin/magento setup:upgrade
Deploy it, wait 24 hours, and your RUM data in New Relic will start coming through with the new pageType
attribute. From there, you can use the included dashboard template to start exploring, or build your own NRQL queries to dig even deeper.
If you’re on GENE’s Unlimited Support, we’ll handle setup, integrate it with your monitoring, and even translate the data into actionable insights for your commercial teams.
Want to learn more?
We’re hosting a free webinar on Tuesday 9th September - Adobe Commerce: Smarter Monitoring, Greater Visibility. Luke Rodgers and Duncan Copeland will show:
How to get more from New Relic APM, Infrastructure and Logs
How to enhance your RUM data with this module
How to spot overlooked Fastly configurations that slow you down
How to set smarter, noise-free alerts
This is for the leaders who want their teams to act faster, and the teams who want to prove the value of their work in hard data.
Register here
Ready to See What You’ve Been Missing?
If you’re already running Adobe Commerce Cloud, you already own the infrastructure. This module simply lets you use it to its full potential.
That’s what Intelligent Innovation looks like: find the blind spot, solve it elegantly, share it freely.
Author
Luke Rodgers
Luke heads up engineering at GENE, where he spends most of his time solving hard problems for eCommerce teams trying to scale. He’s an Adobe Master Developer, long-time Magento contributor, and bug bounty hunter who cares deeply about performance, clean code and doing things properly.
He’s been instrumental in shaping GENE’s security tooling and performance frameworks, making sure the things we build are fast, stable, and easy to maintain. Whether it’s stabilising a flaky build, tuning infrastructure, or rethinking how checkout works, Luke’s focus is always the same: ship fast, run stable, add value.
Related Blog Posts
We surveyed and interviewed eCommerce decision-makers across retail, B2B, and DTC. The result? A brutally honest snapshot of what’s working, what’s not, and what’s coming next.