Pathing: Internal Search Analysis. (not just for page views)
When I was at the Omniture training class a few weeks back, the instructor mentioned that an advantage of storing the internal search terms in a s.prop was that you could get pathing enabled on the s.prop and you would then be able to see not only what your visitors were searching on, but how they refined their search.
Note: After you choose which s.prop you are going to use to store/capture the data in, you will need to contact Omniture Client Care to get pathing enabled for that s.prop

Where does your path take you?
Bing! You have inflated traffic numbers!
The past couple of months we noticed a very odd trend the the geo-location / city data that was being saved in Omniture. The great metropolis of Redmond, Washington was now the number 1 city of origin of our web visitors. And this was not a small lead, they were the number 1 city by more than double the traffic from the number 2 spot.
Trying to find an explanation for all this, I checked the twitter-verse and did a little digging online, but did not have a chance to really dive into the issue until yesterday. Read the rest of this entry »
Omniture / SalesForce Integration: Part 2 – s_code & more.
If you missed Part 1, read it first.
The past few weeks have brought some significant progress in the Omniture & SalesForce integration efforts. Thanks to the folks at Omniture we were able to figure out what was causing the data between the two systems not to flow.
Within the SalesForce Campaign Module, the following new Omniture data fields must be populated: Allocation & Origin

Once this was set, the data exchange began to work right away. Well..... it began to work the next day, as the data exchange happens once a day.
Now to back up a step. Part of the integration is making some changes to the s_code.js file. Using the setCookieParam function you need to set additional values:
s_code Changes
var external_campaign_param ='campid'; var internal_campaign_param ='iCampid'; var retouch_campaign_param ='rtCampid';
Page Code Changes
s.eVar20 = s.setCookieParam(external_campaign_param,s.getQueryParam(external_campaign_param),1,365); s.eVar22 = s.setCookieParam(internal_campaign_param,s.getQueryParam(internal_campaign_param),1,365); <pre id="line531">s.eVar23 = s.setCookieParam(retouch_campaign_param,s.getQueryParam(retouch_campaign_param),1,365);
Note: The eVar's used above should be the same that you set up in Part 1 as defined in the implementation guide.
These values will give you the ability to pass these values along whenever you submit data to SalesForce using Web2Lead or RingLead or however you submit data into SalesForce.
<cfhttpparam type="Formfield" value="#arguments.omtr_clm__campaign_external__c#" name="omtr_clm__campaign_external__c"> <cfhttpparam type="Formfield" value="#arguments.omtr_clm__campaign_internal__c#" name="omtr_clm__campaign_internal__c"> <cfhttpparam type="Formfield" value="#arguments.omtr_clm__campaign_retouch__c#" name="omtr_clm__campaign_retouch__c">
As of the writing of this, data has been flowing between SalesForce & Omniture for one week. It's too early in the process to get a full understanding of how we will best be able to leverage the data exchange between the systems, but I am looking forward to exploring this further.
Code snippets above are based on a ColdFusion environment and are meant to serve as psuedo code
-Rudi
“If wishes were horses beggars would ride”
Thanks to the magic of the internet & twitter I read a request this morning for a wish list of integration ideas for Adobe + Omniture, from @BrettError. I knew that I would not be able to fit my list in the 140 characters allowed by twitter, so I will list them out here.
Of all the Adobe products out there I use ColdFusion almost exclusively (not counting reading PDF's with Acrobat), so my list will be very slanted towards items I would love to see from an Omniture + ColdFusion perspective, that would make my job of implementing and optimizing the Omniture code & tags easier. That being said, this list below could easily be ported over to whatever development platform the site to be tracked is built on.
1) Tag library integration / validation within the soon to be released ColdFusion IDE - CF Builder. Much like the integrated JS libraries that can be added to other Eclipse based IDE's
2) Dedicated AJAX support - ok, so maybe this one has nothing to do with ColdFusion specifically but it would be great to have a defined/dedicated AJAX tag like s.trackAJAX() instead of having to use the custom link tracking s.tl() to track AJAX events. More and more of what I do is on RIA, AJAX heavy elements where a user/web visitor can spend a long time and make many clicks on AJAX elements without ever triggering a page reload.
3) Native integration with the ColdFusion session variables to by default populate many of the page specific variables to send to Omniture. (pageName, server, channel, etc.)
4) Built in tags to use the Data Insertion API to push data into Omniture as an alternative to the JS Beacon. Having this as a CF tag, might make it easier to accomplish #2 above.
5) Community. The Adobe ColdFusion is a loyal and active community and serves as a great example of the effectiveness of having a great active and supported developer community.
6) Enhance documentation by creating Adobe AIR versions such as this. I use this version of the Adobe Live Doc's all the time. Very handy!
So, there it is. My 2/5's of a nickel on what I would love to see as a results of the Adobe(ColdFusion) + Omniture integration.
-Rudi
PS. The original tweet request for the wish list made me instantly think of a quote my mom often repeated to me when I would say "I Wish...."
“If wishes were horses beggars would ride”
Omniture & ColdFusion: Why you should care.
So you use ColdFusion and by now you have heard the news that Omniture is going to be purchased by Adobe. So what? Why should you care?





