#omniture

[wengland]

Adobe Enterprise and Adobe Analytics do NOT play nice with uBlock Origin.  If you need to use Adobe Analytics, you will need to shut off and whitelist Adobe.  Part of that is Omniture:

no-strict-blocking: omniture.com true

You’ll also need to shut off DuckDuckGo Privacy protection too.  Guess that makes sense in that Adobe Analytics / Omniture is specifically designed to track you across the web for data gathering purposes.  It’s like, their job. 

[lets-payal-stuff]

How to add Omniture to Google Tag Manager

The problem with Google Tag Manager is that it currently doesn’t support document.write in their Custom HTML tags, so adding the Omniture code unmodified won’t work. So in order to get everything to work properly we need to make a small modification to the Ominture code and make sure we load everything in the proper order. I Have outlined a step by step process to get Omniture working in Google…

View On WordPress

[wang656]

Cole Haan Site Optimizations

Cole haan was a brand held under the Nike umbrella and was forced to use an outdated version of the Nike global CMS. Unfortunately, that made it very difficult to implement changes to their templates and enhance the functionality of their site. One thing that we did have access to was Omniture Test and Target which was used as both a workaround and as an A/B testing tool. Optimizations made during the urban explorer campaign ensured incremental lift to their holiday sales.

[elisp-solves-problems]

I've been curious for a while how other companies are testing their analytics, if they're testing them at all (?!). Viget is doing it by spying on the .push() function that Google Analytics uses to send their beacon calls.

At work, we were doing it that way previously, except spying on the analogous function for Omniture requests as we were using Omniture for the majority of our analytics. While it looks super clean in the Viget article, we found it to be a little messy for our purposes. As best I can tell, Omniture uses different function calls for normal page events vs click events, so we had two different functions to spy on. 1 Plus, we're in the middle of migrating between different analytics providers, so at the moment we've actually got Omniture, ComScore, and Google Analytics on any given page. The pure javascript spy method does wrap up nicely with PhantomJS and the reporters already built, but it doesn't scale very well to multiple trackers.2

What we've switched over to now is the proxy method - in particular, setting up our Webdriver browsers with the Browsermob Proxy in the middle, watching all network traffic that the browser generates. Luckily, we didn't run into any issues with HTTP vs HTTPS traffic, as I wouldn't really know the first place to start with that. But, using a proxy has its own issues - there are a few tricky issues about cleverly determining which request you actually want to look at 3. However, we prefer it because it's guaranteed 100% the actual data that's going to the analytics service, so we can be confident in our test results. Additionally, given our current set up, we need a method that easily applies to multiple analytics groups, and using the proxy that's just filtering against different URL addresses 4 instead of setting up a whole new spy, which would require some intimate knowledge of the tracker code.

Actually, I think we were spying on an in-house wrapper function instead of the actual omniture call, so things weren't nearly as clean as in the linked article. ↩︎

The answer to whether or not we should be using multiple trackers is definitely not!... maybe outside the scope of this blog post... ↩︎

Do we only look at the most recent request? the most recent few? Do we throw away all old requests every time we click or navigate to a new page? What constitutes a new page? ↩︎

Omniture's pattern is /b\/ss/, google's pattern is google-analytics, etc, etc ↩︎

[ukomnimann]

Adobe Site Catalyst Product Names

Adobe Marketing Cloud: Product Names

Black : the new name for white.

Seriously though I think the time has now come for us all to switch over to new names and sunset the old ones – for good.

Since the 2009 Adobe purchase of Omniture Business Unit and the July 2013 UI Update (which formally sunset the “old” names ,but not completely!) we’ve been parallel running with old/new names.

Twitter

#Omnit…

View On WordPress

[andi77]

Another reason why I prefer to attend web analytics conferences instead of social media events;-)

[mdillr]

Measuring Community

Building a community site is just the beginning. Once it's up and running, how do you measure your success? You could take the easy way out and just go by a simple measure like number of registered members, but that's the wrong way to go. What you really need to know are things like: How engaged are my members? Are they getting more involved with the site over time, or less? Are they attracted to the web features that I spent the most time (money) on, or are they instead lining up to use the features that come standard in my CMS? In short, you need a strategy for measuring your community, and that measurement needs to have historical dimensions so you can track trends. My manner of approaching this task has changed over time; this is where I currently stand. 1) Bounce rate. This is the measure of visitors who come to your site, take one look at it, go, "Bleah!" and leave. Ideally this should be the number of visitors that leave within 10 seconds of hitting your site. Depending on your analytics package, this figure may or may not be available. On my current post we're using Omniture, where the best I can do is measure the number of visits that take less than one minute. Given that the sites I work with are pretty content-intensive, a visit of less than a minute is a pretty definitive bounce. A variant bounce-rate measure would be single-page visits, though you should look a little deeper here and see which page they're visiting. It may be that you have a single page on your site that meets the needs of a number of your returning visitors, in which case it's not a classic bounce. On the other hand, if this single page is your home page, it's a good bet that you're failing to engage with your content, design, or information architecture. 2) Forum posts. Not a sexy number, since this is your members doing the community thing on their own, without engaging with any of your fabulous (and possibly expensive) original content. But it's real community juice, and you want to know if posts and threads are going up or going down over time. 3) Time spent per visit / Pages per visit. These are two sides of the same coin (so it should be perplexing if one is trending up while the other is trending down). Of the two, I tend to prefer the latter, because while pages per visit is skewed by search engine spiders that crawl every page on your site, my personal bias is that time per visit is skewed more by visitors who load your site then walk away, leaving the browser open without exiting the site. I have no data to prove that, mind you, it's just my lurking suspicion. Either way, you want these measures to rise over time. More time and more pages per visit mean that what you're building is keeping people around. 4) Visit number. I'm fond of this metric. It shows you how many of your visitors are new to the site vs. returning. Community sites should draw in more and more repeat visitors over time. Of course, this is easily skewed as well; anyone who clears their cookies will be registered as a first-time visitor the next time they visit. That's why you shouldn't look at absolute numbers, rather look on whether the numbers are trending up or down. Down is bad. 5) Success events. This metric isn't special to community sites; pretty much every serious site should come complete with an idea of what you want your visitors to do when they visit. When they do those things, it's a success event. Define them, measure them, graph them over time. Trending up is good. And last, and somewhat least, you've got: 60 Competitive stats. Odds are that you have competitors: sites that make you grind your teeth, those evil bastards who are stealing your visitors and buying Google adwords that rightfully belong to you. Compete.com and a few other sites will graph traffic to any URL you enter, though their data certainly isn't of uniform quality. So come up with your two or three top competitors and see how they measure up against your site! You'll never know how trustworthy the data is, but it certainly makes for interesting reading. Site analytics is where, in my experience, most community sites fall flat. All the energy goes into features; after they're live, no one really wants to follow through and see what is performing well. Maybe we're all just afraid that we're secretly failing, and pulling down those numbers will expose us for the frauds that we are. But if you don't have those numbers you never have the chance to learn from your successes and failures. Gather the numbers, report them monthly, and get better at what you do.