nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Omniture Component

cagatayk

Hi,
I am very new with Teamsite and LiveSite.
I need integeration with Omniture but out-of-box component doesn't meet most of our requirements. Did anyone deal with these case before or develop any complex component for integration with Omniture?
Thanks

Find more posts tagged with

Comments

Stokes

Hi,
I am very new with Teamsite and LiveSite.
I need integeration with Omniture but out-of-box component doesn't meet most of our requirements. Did anyone deal with these case before or develop any complex component for integration with Omniture?
Thanks

What do you need that the OOTB component doesn't do?

Stokes.

cagatayk

We have lots of eVar and sProp variables that should be set manually and page by page by business team, but with OOTB component we can not do this.

Stokes

Well, if the OOTB component gives you a starting point that mostly works, you can copy that component into your own folder and customize it to do what you need.

If all you need to do is gather some string values in the component that's dropped on each page (or in a template) and then include those as variables in the script on the page, then that shouldn't be too hard.

You can just add <Datum>s to the component to gather the values (for each page) and typically change the Appearance XSL to put those values into the component output. In this case though, I don't think analytics components use the XSL... instead they use a Java external to set the content that will be rendered in the page. So you would have to extend or replace the Java class with one that added the additional information gathered in your new <Datum>s.

Stokes.