New Keystone Blog Post- Omniture Campaign Best Practices
Head on over to the Keystone Community Blog for my latest post, with Tips and Tricks for Campaign Tracking in Omniture:
The standard Omniture Campaign reporting offering, based solely on a query string/tracking code pair, is pretty solid: campaign reports and all the possible classifications, paid/natural search detection and reporting, and marketing channel reporting, managed from right there in the SiteCatalyst admin console. But over time we’ve found some tips and tricks that can maximize the value of your campaign tracking efforts.
- Custom Campaign Click-throughs
- Granular, Classified Tracking Codes with a Marketing Channel prefix
- Campaign Landing Page Pathing
- Campaign Cross-Visit Participation
Head over and take a look!
Internal Search- short and sweet
If you aren't tracking internal search, it better be because you simply don't have a business need for internal search, which should be super rare. In *95% of internal search engines, tracking internal search requires nothing more than grabbing a query parameter. For instance, do a search on my little site here on "wugs".
You'll note on the landing page, the URL shows a query string that includes my search term (in this case, "s", though many websites use "q").
![]()
It's pretty rare to find one that doesn't have the search term in some parameter or another. Go to your own internal search, see what (if any) query string is catching the keyword.
Now that I know the parameter (again, "s" in this case), I can add this line of code to my s_code's s_doPlugins section (assuming propX and eVarX has been enabled and set aside for Internal Search Terms):
ADDITION: After I posted this I realized there was one more bit I usually like to do. If you want to set internal search as a custom event, you can then add this code:
And voila! Short and sweet Internal Keywords reports.
Note: why use both a prop AND an eVar? This recent Omniture post explains it nicely.
*I'll admit that number is completely anecdotal


