New Relic Destination

New Relic enables you to better understand, using their real-time analytics, the end-to-end business impact of your software performance.

This document was last updated on August 29, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, please let us know!

Getting Started

The first step is to make sure New Relic supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

WebMobileServer
📱 Device-based
☁️ Cloud-based
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “New Relic” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in your Insights Account ID and your Insert Key.
  4. Once destination enabled we’ll start forwarding your calls to New Relic.

Track

If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:

analytics.track('Article Completed', {
  title: 'How to Create a Tracking Plan',
  course: 'Intro to Analytics',
});

We forward track calls to New Relic in order to insert custom events via their Insights API.

Your event properties will be included with the event, conforming to the following rules:

  • booleans are transformed to strings
  • reserved nrql words are wrapped with backticks
  • reserved words are removed
  • dates are converted to ISO strings
  • arrays and objects are removed

By default the events are given an eventType of ‘Segment’. This can be changed via the optional ‘Custom Default Event Type’ setting in the Segment UI.

If you pass a revenue property, we’ll pass that through as the value of the conversion.


If you have any questions, or see anywhere we can improve our documentation, please let us know!