Reply
Visitor
Posts: 7
Registered: ‎12-26-2017

S_Code File for Omniure Configuration Through Tealium

Hi,

I have been trying to configure the Omniture tracking through Tealium and  I have following concern. Could you please anyone help me with this:

I assume without S_code.js file and the metrics and methods involved in this, I can configure the Adobe tracking through Tealium. I just need the following info. from this file such as Server, Server name, Report suite, and Namespace.

Reply
0 Kudos
Tealium Employee
Posts: 740
Registered: ‎09-01-2015

Re: S_Code File for Omniure Configuration Through Tealium

Hi @shat2057

This series of articles should help with all things Adobe Analytics, specifically check out the Setup Guide which tells you what in the s_code to look for. For example, the value of  s.account is what you'd enter into the Report Suite input.

I hope you find this helpful!

Cheers,
-Dan

Highlighted
VIP
Posts: 195
Registered: ‎01-04-2016

Re: S_Code File for Omniure Configuration Through Tealium

Hello @shat2057 - is it a new implementation altogether or a migration to Tealium from hard-coded or another tag mgt. provider?  

 

You get a choice in the TiQ Marketplace to implement Adobe Analytics (SiteCatalyst) with the "s code" version or the newer AppMeasurement protocol tag.  Either way, Tealium takes care of injecting the underlying code.  If you're migrating from an existing implementation, you'll need to adapt any special DoPlugins setup into your new Tealium-based implementation.  The link Dan provided will give you some info to go on.

 

Looking forward to your updates - 

Visitor
Posts: 7
Registered: ‎12-26-2017

Re: S_Code File for Omniure Configuration Through Tealium

[ Edited ]

Hi @dan_george

Thanks for sharing this. I have created an Adobe tag in Tealium using the s_code.js file configurations. Since we migrated all props, evars, and Events through the extensions, I believe this s_cdoe.js file will not be needed anymore.

Reply
0 Kudos
Visitor
Posts: 7
Registered: ‎12-26-2017

Re: S_Code File for Omniure Configuration Through Tealium

Hi @mitchellt

Thanks for the Insights.

I have migrated the page level tracking to Tealium tracking. So configured Adobe tag using S_code metrics available in the website. We also created Tealium extensions for Variables tracking which we had this in s_code.js file previously. Due to this, we don't use DoPlugins extensions. 

Correct me if I am wrong.

Reply
0 Kudos
Tealium Employee
Posts: 740
Registered: ‎09-01-2015

Re: S_Code File for Omniure Configuration Through Tealium

@shat2057

You are correct that the s_code file is no longer needed. Technically speaking, adding the tag via Tealium iQ adds it back in but it's managed via Tealium instead of hard-coded on the page. 

Regarding doPlugins, it varies which can be removed and which need to stay. It sounds like you were able to leverage Tealium extensions to take place of doPlugins which is great, especially since that data is now available for all vendors instead of only Adobe.

So it looks like you're on the right track!

Cheers,
-Dan

Visitor
Posts: 7
Registered: ‎12-26-2017

Re: S_Code File for Omniure Configuration Through Tealium

Thanks @dan_george.

 

Reply
0 Kudos