Browser subscription usage

Original pricing plan

This doc is for accounts on our original Product-based pricing. If you're on the newer pricing plan, see New Relic One pricing plan. Not sure which you're on? See Overview of pricing plans.

For accounts on our original pricing plan, this document explains how we calculate billable usage for Browser subscription usage. This document also provides available subscription usage attributes and example NRQL queries to use in the New Relic UI or with API calls.

For details about single-page app (SPA) monitoring usage, see SPA usage.

Data generation

Once per hour, for every monitored application, a New Relic Browser account will generate a NrUsage event. Each event will summarize the usage for the last hour.

When querying Browser usage data, use a productLine attribute value of Browser. For more information, see the Browser query examples.

Usage calculations

Monthly subscription usage equals the total number of page views that month across all end-user browsers. AJAX traffic does not count against your daily usage. If your page views are fairly steady over time, you can estimate usage for the current month.

Only the account Owner and Admins can view the usage UI. However, anyone in your account can query usage data using the NrUsage event.

To view usage information in the UI:

  1. Go to: account dropdown > View your usage.
  2. On the Browser usage page, set the time picker to Last 30 days.
  3. Multiply the Avg daily page views by the number of days in the current month.

For more information about the usage UI, see Introduction to New Relic subscription usage data.

Table definitions

Here are definitions of the column headers displayed in the UI table and CSV files. The columns visible depend on the Group by option selected at the top of the page.

Header Definition
Account name The name of the account. This can be a standalone account, a master account, or a customer partnership.
Account ID New Relic account ID.
Average daily page views The average daily page views for that account or application.
% of total usage The percentage of the total usage used.

General attributes

The following are general (not Browser-specific) account-related attributes. These attributes can help you understand how your accounts and sub-accounts are using New Relic products.

Attribute Description
consumingAccountId

ID of the New Relic account that is directly responsible for the stored events, as determined from the license key used.
consumingAccountName Name of the New Relic account that is directly responsible for the stored events, as determined from the license key used.
masterAccountId

The ID of the master account that is either responsible for stored events or that is the parent of the consuming account. When a master account is the consuming account, masterAccountId is the consumingAccountId.

This attribute is present even for accounts that do not have a master account. This is to ensure continued reporting if the account is later made a master account.
masterAccountName

Name of the master account that is either responsible for stored events, or that is the parent of the consuming account. When a master account is the consuming account, masterAccountName is the consumingAccountName.

This attribute is present even for accounts that do not have a master account. This is to ensure continued reporting if the account is later made a master account.
partnershipId

Partner ID of the New Relic customer partnership associated with the account responsible for the stored events.

This attribute is only present if the consuming account is associated with a New Relic customer partnership.
partnershipName

Name of the New Relic customer partnership associated with the account responsible for the stored events.

This attribute is only present if the consuming account is associated with a customer partnership.
subAccountId

ID of the sub-account that is responsible for the stored event. When this attribute is present, subAccountId is the consumingAccountId.

This attribute is only present if the consuming account is a sub-account (not a master account).
subAccountName

Name of the sub-account responsible for stored events. When present, this attribute is the same as the consumingAccountName.

This attribute is only present if the consuming account is a sub-account (not a master account).
timestamp UNIX timestamp (seconds since epoch) of the day and time when event generation was initiated.

Browser attributes

The following are usage-related attributes generated by New Relic Browser. To query Browser data, use a productLine attribute value of Browser.

Attribute Description
browserPageViewCount Number of page views for an application for that 24-hour period. For more on how events are generated, see Data generation.Page views for both Pro and Lite Browser agents are counted.
productLine The New Relic product the usage data is from. For Browser data, this value is Browser.
usageType

The type of entity this event records values for. For Browser, this value is Application.
browserAppId

ID uniquely identifying the application reporting this usage, as it appears in the Browser product.
isPrimaryApp

Deprecated April 2, 2020.

Boolean. true means the application is the primary app. false means the app is one of several apps that an agent reports data for. For more on multiple app names in APM and Browser, see Use multiple app names.

The sum of events where this attribute is true will give an accurate total of page views when you are using the multiple app names feature. Counting events where this attribute is false will result in over-counting of usage.

Query examples

Here are some examples of NRQL queries you can use with your subscription usage data. You can run NRQL queries and use the resulting charts in dashboards.

Page views for the last complete month

This query shows a count of page views from the last complete month:

SELECT sum(usage) 
FROM NrUsage 
WHERE productLine='Browser' 
SINCE last month 
UNTIL this month
Page views for the last week by account

This query shows a count of page views from the last week by account:

SELECT sum(usage) 
FROM NrUsage 
WHERE productLine='Browser' 
SINCE 7 days ago 
FACET consumingAccountName
Page views for the past month, by application:

This query shows a count of page views from the past month by application

SELECT sum(usage) 
FROM NrUsage 
WHERE productLine='Browser' 
SINCE 30 days ago 
FACET browserAppID
Account hierarchy

This query is useful for seeing the account hierarchy (partnership, master, sub-accounts):

SELECT count(*) 
FROM NrUsage 
FACET partnershipName,masterAccountName,masterAccountId,consumingAccountName,consumingAccountId 
LIMIT 1000 
SINCE 1 day ago

SPA usage

Page views are used by New Relic Browser to determine customer data usage and product pricing. This document defines a page view in the context of New Relic Browser's SPA monitoring and explains why:

  • SPA monitoring does not affect Browser data usage
  • SPA monitoring will increase Insights data usage

In New Relic Browser, a page view is defined as a complete load or reload of a page, signaled by the firing of the window.onload event.

New Relic's SPA monitoring tracks traditional page views, but it also tracks changes in the browser that do not require a page load, such as:

  • Route and hash changes
  • Synchronous and asynchronous JavaScript
  • Dynamic server-side updates to a page

Route changes are tracked automatically, and by setting up custom instrumentation you can capture almost any type of browser interaction.

With New Relic Browser Pro, pricing is based on an account's number of page views per month. If SPA monitoring is enabled, browser interactions that do not require a page load are not counted as page views for billing purposes. With SPA monitoring, you can track an unlimited number of route changes and other custom browser interactions that don't involve page loads.

Notes on Insights subscription

If you switch from standard Browser monitoring to SPA monitoring, and you also pay for Insights (and don't use only your complementary Insights subscription), your Insights data usage will increase. Because SPA monitoring is a more advanced way to monitor your application, it creates more Insights events than standard monitoring for the following reasons:

  • Page views create not only PageView events, but also BrowserInteraction, AjaxRequest, and BrowserTiming events.
  • For the typical SPA-architecture app, there are more route changes than there are standard page loads.

If you pay for Insights and your current Insights license is not sufficient for the amount of events generated with SPA monitoring, we will notify you when you have exceeded your data usage plan. To remedy this, the following options are available:

For more help

If you need more help, check out these support and learning resources: