What happened to the New Relic Tag?

andrew_gatlabay
New Member
andrew_gatlabay
I remember seeing new Relic in the Tag Marketplace. Is New Relic no longer supported?
4 REPLIES 4

What happened to the New Relic Tag?

Tealium Employee
Hi Andrew, New Relic team had a strong preference for their JS to be inline in the HTML source and politely requested to be removed from our marketplace. From a technical standpoint, a fully functional New Relic code snippet can be inserted into the utag.sync.js container and run synchronously in the HEAD. However, the New Relic team has let us know that running their code from within an external container is not officially supported. (Our previous async tag did only support a subset of their features.) For more detailed information, please open a ticket at support.newrelic.com.
Highlighted

What happened to the New Relic Tag?

ginny_cobbett
New Member
ginny_cobbett

Hi @ty_gavin - Do you know if the New Relic team will consider support from within a sync container in the future?

What happened to the New Relic Tag?

Tealium Employee

@andrew_gatlabay @ginny_cobbett

 

While New Relic may not be supported as of now within Tealium iQ, we do have an API integration built out leveraging our new EventStream service. There are more details to come in the near future, such as pricing considerations, but it would an option for sending browser or mobile app data to New Relic.

What happened to the New Relic Tag?

Tealium Employee

@ginny_cobbett

 

You may be able to "unofficially" run their JS code inside the Tealium utag.sync.js (synchronous) container if you like by pasting in their code block into utag.sync.js template.  The New Relic team simply has a strong preference to be inline in the page as they have a code block that prefers to execute before all other code.  Also, they have a good argument that any 3rd-party-hosted script that is set to run synchronously will add some delay to your page and impact page performance.  

 

If you *only* plan to run New Relic (and have no plans to run other synchronous 3rd party code), then it does make sense to add their code directly inline in your HTML.  As a best practice, executing 3rd-party-hosted JavaScript code should always run asynchronously.  The Tealium utag.js is an asynchronous solution, but we also offer the utag.sync.js as a convenience.

 

On a related topic, Tealium Collect tag now supports data collection for window.performance.timing metrics.  These metrics can be leveraged in AudienceStream for real-time understanding of how your visitor is currently experiencing your site's pages.  That might mean taking action in an AudienceStream Connector to send a targeted email to someone who has had a few consecutively slow page loads in your checkout process.  "We're sorry our site was slow during your recent checkout process.  Please remind your family members to stop streaming multiple videos on multiple devices while you're shopping online.  And take advantage of this 10% off coupon code." :-)