Omniture Clickmap problems
Recently, I decided to dig into some of the problems that exist with the Omniture Clickmap technology.
First thing on my ToDo list was a brush up on the Clickmap documentation, updates could have been made since the last time I read it.
Well, there was one big change, the Clickmap userguide has disappeared from the:
“Help Home -> Supporting Docs -> Manuals” area, where all other manuals and implementation guides are located, it’s now only accessible through a Knowledge base article. Do a search for “Clickmap user guide” and it’ll show up in the results. (I’m still wondering why Omniture is hiding this file)
After a lot of reading & testing, here is my personal list of peculiar Omniture Clickmap behaviour:
- Buttons only work under certain circumstances, an old school <input type=”submit”> works fine. But if You use a <button type=”submit”>Buttontext</button> Clickmaps won’t work, and it doesn’t help to add a s_objectID.
- <input type=”text”> appears only to be working if you add a s_objectID
- In general, for elements without a href, without a s_objectID, but with an onclick handler, the content of the onclick handler will be used for identification of the link, but the Clickmap plugin will almost never be able to figure out where to place the clickmap overlays using these data.
- Clickmaps seems to have some serious issues with non-ASCII data in onclick handlers.
The Clickmap documentation itself is somewhat confusing as it contains the usual mix of G and H code specific examples, I really think Omniture has to realize that it’s too difficult to “patch update” documentation while at the same time maintaining high quality. They have quite a few manuals in the need of a major rewrite.
