All Traffic Sources variables should be turned into out of the box eVar
type variables and they should allow you to adjust their expiration
beyond the visit, but don't allow things like keywords to be overwritten
by direct load on subsequent visits.
This would make the complex eVar vs. prop issue disappear. You ever try
explaining this to someone new to Omniture....I want to poke my eyeballs
out!! props=eVar instancesprops also have-visits-daily, weekly, monthly,
etc. visitors-pathing-participation These items should just be a feature
to enable on an eVar if needed. Also eVar visits/visitors does not equal
prop visits/visitors. If an eVar value persists past the visit it is
counted as a visit the next time that same visitor comes to the sit...
@BretGundersen I think not only having a landing page report by traffic
source but also, every other page of the visit by traffic source - many
people want to do analysis on the path users take after coming from a
certain traffic source, or the path users take by keyword searched etc.
The report would be pageName broken down by visit marketing channel
source and marekting channel source detail. This would let people know
which source or source detail drives the most people to a page - and