New Relic Destination

Destination Info

• Accepts Track calls.
• Refer to it as New Relic in the Integrations object

Components

• Server

Connection Modes

Device-mode	Cloud-mode
Web	Web
Mobile	Mobile
Server	Server

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

Getting Started

1. From the Segment web app, click Catalog.
2. Search for “New Relic” in the Catalog, select it, and choose which of your sources to connect the destination to.
3. In the destination settings, enter your Insights Account ID and your Insert Key.
4. Once destination enabled we’ll start forwarding your calls to New Relic.

Track

If you’re not familiar with the Segment Specs, 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 using 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 using 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.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.