A full-cohort source-check range is not summarized on this page. The dated package retains row-level source checks and historical publication limits. The package-check date records offline acceptance, not a source refresh.
41 reviewed New Relic company accounts. Evidence covers new relic browser initialization or agent code; first-party monitoring declarations. Claims apply only to the recorded property, product or workload.
New Relic source composition | Source class | Count | Scope |
|---|
| New Relic browser initialization or agent code | 39 | Code is served by an official website or portal. Scripts were inspected without execution; backend agents and telemetry transmission are unverified. |
|---|
| First-party monitoring declarations | 2 | Company-published documentation or policy describes New Relic use; statement age and workload limits remain recorded. |
|---|
Contexts in the New Relic research: Recorded monitored surface types; no assertion of actual telemetry delivery. WhosBuilt review of the saved accepted report and approved examples; no source refresh.
Accepted report describes the retained list. Qualitative roles show presence, not prevalence. Counts refer only to the named recorded classifications; no source-by-context intersections are released. The displayed date is the package date. Source dates remain as recorded in the package; no source was refreshed for this analysis.
- Public sources do not verify paid subscriptions, organization-wide deployment or purchasing intent.
- Source retrieval dates record access; they do not make an older statement or historical deployment current.
- Published contact channels do not establish outreach permission, mailbox deliverability or purchasing authority.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.