New Relic
New Relic is a monitoring platform. Its browser agent runs in a visitor's page to time how long things took, catch JavaScript errors and report both back to the engineering team that operates the site. It is classified here as monitoring rather than tracking, and it is the kind of third party a site's own developers add deliberately rather than one that arrives through a marketing tag. It was detected on 159 of the 5,294 sites measured here, 3% of them, which puts it 26th on the site-count list of the 88 companies in this index.
More than half its sites carry a banner the crawl can name
89 of the 159 sites ran a consent product the crawl could put a name to, a little over half of them. Alongside New Relic it saw OneTrust on 53 sites, an IAB TCF consent tool on 28, then Osano on 2, Usercentrics on 2, Cookiebot on 1 and CookieYes on 1. Read those as separate sightings rather than a split of the 89, since one page can hold two banners. The pattern reflects who buys application monitoring: organisations with engineering teams large enough to also have a compliance function.
OneTrust alongside on 50 of 159 sites
Setting Google aside, which was present on 118 of the 159 sites, the company most often found next to New Relic is OneTrust, on 50 sites or 31.4%. Adobe Fonts followed on 20 (12.6%) and adobedtm.com on 19 (11.9%), then Cloudflare, Cloudflare Analytics and demdex.net on 15 each, jsDelivr and Amazon Ads on 14, and go-mpulse.net on 13. That makes OneTrust the tightest pairing on this hostname's co-presence list once Google is set aside, and it is a consent platform rather than an advertising one.
142 of 159 sites had a company arrive inside the window
142 sites, 89.3% of them, had a company arrive inside the consent window, which ranks 69th of the 88 companies here and so sits toward the lower end. The median site contacted 5 companies inside that window and 1 after it closed, which is the more interesting half of the pair: something on a typical New Relic page is still arriving once the window has passed.
News, research and retail, in the same list
The example sites run across categories that rarely share a page profile. weather.com contacted 13 companies with all 13 inside the consent window, at 393 ms, behind an IAB TCF consent tool. wsj.com contacted 16 with 15 inside it. At the other end, sciencedirect.com contacted 4 with all 4 inside it, cambridge.org 7 with all 7, and nist.gov 5 with 4. nike.com contacted 4 with only 1 inside the window and a first contact at 1,346 ms, and aol.com contacted 10 with 2 inside it at 1,724 ms. Also present: criteo.com, adsrvr.org, ea.com, docker.com and behance.net.
Eight companies on the median site
The median New Relic site contacted 8 companies, which is 49th of 88, carried 1 tracker, which is 69th of 88, and issued 43 requests, 46th of 88. That combination, a middling number of companies with a low tracker median, is the shape of a page with real engineering infrastructure and a modest advertising footprint. First contact on the median site landed at 745 ms, 32nd of 88 counting down from the slowest; the earliest on any of its sites was 170 ms.
| Site | Companies | Before consent | First contact |
|---|---|---|---|
| criteo.com | 12 | 8 | 495 ms |
| sciencedirect.com | 4 | 4 | 1097 ms |
| nist.gov | 5 | 4 | 611 ms |
| adsrvr.org | 3 | 3 | 639 ms |
| weather.com | 13 | 13 | 393 ms |
| ea.com | 8 | 7 | 368 ms |
| wsj.com | 16 | 15 | 382 ms |
| aol.com | 10 | 2 | 1724 ms |
| docker.com | 6 | 5 | 329 ms |
| behance.net | 8 | 5 | 433 ms |
| nike.com | 4 | 1 | 1346 ms |
| cambridge.org | 7 | 7 | 560 ms |
| Tool | Sites |
|---|---|
| OneTrust | 53 |
| IAB TCF consent tool | 28 |
| Osano | 2 |
| Usercentrics | 2 |
| Cookiebot | 1 |
| CookieYes | 1 |
The six most common are listed. The remaining 2 of 89 sites with a banner carry something outside that six. One tool is recorded per site, so these counts never overlap.
Seen on the same pages
Companies most often contacted by the same sites. Co-presence only — the crawl records what arrived, not who called whom.
- GoogleTogether on 118 of these sites
- OneTrustTogether on 50 of these sites
- Adobe FontsTogether on 20 of these sites
- adobedtm.comTogether on 19 of these sites
- CloudflareTogether on 15 of these sites
- Cloudflare AnalyticsTogether on 15 of these sites
- demdex.netTogether on 15 of these sites
- jsDelivrTogether on 14 of these sites
Questions
How many sites in this index use New Relic?
159 of the 5,294 sites measured here, or 3%, ranking 26th among the index's 88 companies.
Is New Relic counted as tracking in this index?
No, it is classified as monitoring. Its browser agent reports timings and errors to the team running the site. It is still a third party the page contacts, which is why it is measured here.
How many New Relic sites carried a consent tool?
89 of 159, a little over half. OneTrust was the product seen alongside it most often, on 53 sites, then an IAB TCF consent tool on 28.
How many companies arrived before the banner could be answered?
The median site contacted 5 inside that window and 1 after it closed, and 142 of the 159 sites had at least one arrive inside it.
Why does a monitoring tool appear next to advertising vendors?
Because it is installed by the same organisations that run advertising. The co-presence figures on this page count what else was on the same sites, which says nothing about what any of those parties do with the data they receive.