SiteCatalyst users, I am curious to know which plugins you found useful to pull over into a javascript extension vs. which ones got dropped and are no longer needed?

[joseph_brown]

e.g. the getQueryParam plugin Omniture would give you in the s_code is not needed when you use Tealium.

[jared_hislop]

Hey Joseph, Usually when I set up a client's s_code I will leave all the plugins intact. This creates a more seamless integration when going from the legacy code into Tealium. However, you are correct some plugins can be replaced by the ever impressive Tealium technology, like getQueryParam, getPageName, channelManager and getPreviousValue. Some that I would keep in place would be: CrossVisitParticipation DaysSinceLastVisit getNewRepeat getValOnce getVisitNumber Hope this helps.

[Clint]

Love this Q Joe!

[sam_tsai]

I like the idea of cleanup as well/reducing redundant code. Any tips on how to refactor plugins like getQueryParam within the s_code, since I'm assuming the code depends on it? I just know that coming from the outside (not originating the s_code) makes me feel a little uneasy making changes. Thoughts?

[jared_hislop]

Sam, Can you clarify what you mean by "refactor plugins"? Are you asking how to replace getQueryParam using Tealium's functionality instead of the s_code? Thanks

[sam_tsai]

Sorry, that might've been a poor word choice. I'm not looking to refactor plugins or rewrite them but really remove the ones that can be considered duplicates of Tealium's built in extensions. I was thinking just do global searches within s_code and any related extensions (since I've broken SiteCatalyst code plugins into extensions) to see where the dependencies were, but wanted to know if anyone saw any dangers with this.