When using the token for [404] it would take precedence over a default value. Added a random panel page with no CASAA mappings. Was greeted by the 404 mapping Omniture value. When 404 mapping was removed page was still recorded but with default values. 404 should only return on the 404 error page. I guess in the end does there even need to be support for the [404] token?

Comments

cntlscrut’s picture

cntlscrut commented

That is a good question. We should take a look at the pros and cons of the token and decide whether or not we want to keep it.