New Relic

New Relic is a leading observability platform that lets you monitor, debug, and enhance your tech stack.

RudderStack supports New Relic as a destination to which you can seamlessly send your event data.

Find the open source code for this destination in the GitHub repository.

Connection compatibility

Destination info
Status: Generally Available Supported sources: Android, iOS , Web, Unity, AMP , Cloud, React Native , Flutter, Cordova, Warehouse, Shopify Refer to it as NEW_RELIC in the Integrations object.

Connection modes
Source	Cloud mode	Device mode	Hybrid mode
AMP
Android
Cloud
Cordova
Flutter
iOS
React Native
Shopify
Unity
Warehouse
Web

Supported message types
Source	Identify	Page	Track	Screen	Group	Alias
Cloud mode
Supported sources

Get started

Once you have confirmed that the source platform supports sending events to New Relic, follow these steps:

1. From your RudderStack dashboard, add a source. Then, from the list of destinations, select New Relic.
2. Assign a name to the destination and click Continue.

Connection settings

To successfully configure New Relic as a destination, you will need to configure the following settings:

• Account ID: Enter your New Relic account ID.

For more information on finding the account ID based on your New Relic user model, refer to the FAQ section below.

• Insert Key: Enter your New Relic insert key.

For more information on getting your New Relic insert key, refer to the FAQ section below.

• Data Center: Choose the data center associated with your New Relic account. By default, it is set to US.
• Custom Default Event Type: Use this field to define any custom eventType for any unmapped track calls. By default, RudderStack sets the eventType as rudderstack.
• Send Device Context: If this setting is enabled, RudderStack flattens all contextual fields delimited by a period (.) before sending them to New Relic.

Enabling this setting is recommended as getting rich device context is very useful in New Relic.

• Send User ID and Anonymous ID: Enable this option to send userId and anonymousId in your events to New Relic.

Track

The track method lets you capture user events along with the properties associated with them.

RudderStack uses the track calls to send custom events to New Relic via the Event API.

A sample track call is shown below:

rudderanalytics.track(
  "Email Opened", {
    subject: "Resume validation",
    sendtime: "2022-01-01",
    sendlocation: "alex@example.com"
  }, {
    context: {
      traits: {
        email: "alex@example.com"
      }
    }
  }
);

RudderStack applies the following rules to the event properties before sending them to New Relic:

• Booleans are transformed into strings.
• NRQL words are wrapped with backticks.
• Reserved words are removed.

FAQ

Where can I find the New Relic account ID?

To find the New Relic account ID, log into your New Relic dashboard.

Depending on your user model, the steps are listed below:

• New Relic One user model: In the top right section of the dashboard, go to your account settings and navigate to Administration > Organization and access > Accounts. You can find your account ID here.
• Original user model: In the top right section of your New Relic dashboard, go to your account settings and click API keys. Your account ID will be displayed here.

Where can I find the New Relic insert key?

To find your New Relic insert key, follow these steps:

1. Log into your New Relic dashboard.
2. Go to API Keys.
3. Find the key of type INGEST-LICENSE (used as insert key):

Questions? Contact us by email or on Slack