New Relic Destination

Segment makes it easy to send your data to New Relic (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to New Relic in the format they understand. Learn more about how to use New Relic with Segment.


We forward track calls to New Relic by hitting this endpoint.

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.

The events are given an eventType of Segment.

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

Supported Sources and Connection Modes

📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

Account ID

Your New Relic Insights account ID

Custom Default Event Type

By default the eventType for any unmapped track events will be sent as ‘Segment’. You can define another custom eventType name to be used instead of that here.

Map Track Events to Custom Tables

Enter your Segment .track() event names on the left and their respective eventType (table name) in New Relic.

Insert Key

Put your New Relic Insert Key

Send Device Context

If you enable this setting, we will flatten all your context fields delimited by a period and send it to New Relic. This is recommended as getting rich device context is useful inside New Relic.

Send UserId and AnonymousId

If you want to send your Segment userId and anonymousId, enabling this option will do so.

If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!