Omniture/SalesForce Integration Part 1: Configuration

1Sep/091

Omniture/SalesForce Integration Part 1: Configuration

As I set out on my latest adventure with Omniture, I decided to begin this project by actually reading the manual first. So, I downloaded and read the SalesForce: Genesis Integration Guide from Omniture. Ok..fine..maybe I skimmed some pages, but I read most of it. What I took away from it, was I was going to need to really plan this project out.

For starters, I was a bit stunned to discover that the default integration would take 9 eVars and 22 Custom Events, with an additional 33 custom events. (Holy smokes! 50 plus custom events!)

So based on the information from the manual, which is about the only information online I could find about the process, this was my initial task list:

1. Confirm SalesForce requirements with resident SalesForce expert.
2. Determine list of integration Custom Events needed. (which iof the 53)
3. Activate SalesForce Genesis plugin
4. Make changes to primary s_code files
5. Initial testing
6. roll out s_code changes to other report suites.

1 & 2 were easy.

#3. This was a whole other beast. I quickly realized that I needed to have the help of our resident SalesForce Expert to help with the configuration. There is simply too much about SalesForce data fields that I do not know. Not to mention the little bits of information that the Integration Guide leaves out.

Here are the items that were more of a challenge in the process, due to either missing information in the guide or lack of SalesForce knowledge.

eVar Classifications:

You must set up classifications for each eVar.
The select box provided to select SalesForce data fields is way way too narrow to be able to read the data field names.

Configure the SalesForce.com Dashboard:

You must add classifications for all elements on this page.
The options provided to add classifications on this page are directly pulled from the classifications selected on the eVar Classifications.
If you have to go back to edit your eVar Classifications any options selected here will not be saved.

Map SiteCatalyst Events

Even though the Integration Guide says that the Marketing Sourced/Touched: Opportunitiy: New is optional...it's not. I had to add a mapping for this.

#1 thing I learned in the configuration: make darn sure you have a great SalesForce person to assist you with this. I am sure I would never have selected the right objects to classify without their help.

It is also apparent that I need a new task list, one that contains a lot more details and steps than I first planned. I will be working on fleshing this out as I progress through the rest on the integration.

This ends the configuration portion of my adventure, off to make changes to the s_code.

-Rudi

Part 2: s_code & more

Share/Save

Tagged as: Genesis, Measure, Metrics, Omniture, SalesForce, SiteCatalyst, Web Analytics 1 Comment

26Aug/090

Capture Search Terms From Your Google Mini into Omniture

Yesterday, saw a twitter from @omtrdeveloper about tracking Google Site Search in Omniture. This reminded me that I needed to do that for our site, except we do not use the Google Site Search, we use the Google Mini Search Appliance.

Google Mini

Here are the steps I took to integrate/capture the search terms into Site Catalyst.

Step 1. Locate and backup your searchtemplate.xslt file.

Step 2. In the section of the code that has the sections labeled "(can be customized)" add this code block.

<!-- **********************************************************************
 Omniture SiteCatalyst code (can be customized)
 ********************************************************************** -->

<xsl:template name="sitecatalyst">
 <xsl:param name="query"/>
 <xsl:param name="matches"/>
 <xsl:comment>
 SiteCatalyst : Google Mini Search Integration
 </xsl:comment>
 <script language="JavaScript" type="text/javascript" src="INSERT-DOMAIN-AND-PATH-TO-CODE/s_code.js"></script>
 <script language="JavaScript" type="text/javascript">
 <xsl:comment>
 s.eVar1="<xsl:value-of select='$query'/>"
 var s_code=s.t();if(s_code)document.write(s_code)
 </xsl:comment>
 </script>
 <script language="JavaScript" type="text/javascript">
 <xsl:comment>
 if(navigator.appVersion.indexOf('MSIE')>=0)
 document.write("unescape('%3C')+'!-'+'-'")
 </xsl:comment>
 </script>
 <xsl:comment>
 End SiteCatalyst : Google Mini Search Integration
 </xsl:comment>
</xsl:template>

NOTES:
1. Replace the"INSERT-DOMAIN-AND-PATH-TO-CODE" with the location where you uploadedthe s_code.js file:
2. Be sure to use an absolute path. http://www.rudishumpert.com/subfolder/s_code.js
3. Code above assumes you are using s.prop1. Change value as needed.

Step 3. Next, locate the XSL template named, search_results.

<!-- **********************************************************************
Search results (do not customize)
 ********************************************************************** -->
<xsl:template name="search_results">
...
...
<body onLoad="resetForms()" dir="ltr">

and place the following code opening <body> tag:

 <!-- *** Add Omniture SiteCatalyst code *** -->
 <xsl:choose>
 <xsl:when test="RES">
 <xsl:call-template name="sitecatalyst">
 <xsl:with-param name="query" select="Q"/>
 </xsl:call-template>
 </xsl:when>
 <xsl:otherwise>
 <xsl:call-template name="sitecatalyst">
 <xsl:with-param name="query" select="Q"/>
 </xsl:call-template>
 </xsl:otherwise>
 </xsl:choose>

Step 4. Deploy code to test/production making sure to backup a copy of your existing XSLT template (just in case).

You should now be able to see the search terms being passed to Omniture using your debugging tool of choice.

-Rudi

EDIT: changed the Omniture variable used from prop1 to evar1 so we could add sub relations to the element.

Share/Save

Tagged as: Google Mini, Omniture, Site Catalyst, Web Analystics No Comments

19Aug/096

One Player to Rule Them All…

Last week I read a great post by Vaugn Denny about the JW Video Player. And being of the curious sort I had to investigate further. So I visited the JW Player web site. And I was greeted with a page that claimed that they had a video player that would not only play flv files, but wmv files as well. And with further reading the player claims to have an open API with access to the player events. Could it be true?

One Player to rule them all, One Player to track them,
One Player to bring them all and in the darkness correlate them
In the Land of Analytics where the Shadows lie.

theringvx6
Read the rest of this entry »

Share/Save

Tagged as: ColdFusion, JW Player, Omniture, Video Tracking, Web Analytics Continue reading

17Aug/094

Track Your FLV Video Files With Omniture & FlowPlayer

EDIT: After I wrote this I found a new video player that will play flv, wnv, and youtube videos.

I've been working on our Omniture integration for a while now and recently I started working on the task of tracking our videos. I know that Omniture has some very nice features you can use with Action Source code, but what if all you have access to is the end result of the flv file? With no tools to edit a player, or the ability to embed the code in the files/players? It's a bit of a challenge to say the least.

I needed a way to track flv files with the same amount of details that the Action Source would provide in a reliable, easy to duplicate fashion. My search for this led me to an FLV player called FlowPlayer. It is a nice easy to implement player with easy access to the API and the events.
Read the rest of this entry »

Share/Save

Tagged as: Flowplayer, Omniture, Video Tracking, Web Analytics Continue reading

6Aug/098

Adventures with Omniture WordPress Plug-in

Update: I have been working on my own version of an Omniture WordPress Plugin! Find it here: http://www.rudishumpert.com/projects/wp-omniture/

It's rare to find a plug-in these days that work exactly as advertised. Hell, it is rare to find one that is only somewhat painful to implement. So when I began the day with the task to implement the WordPress plug-in for Omniture I was skeptical. But it was much easier that I thought. Below are the steps I went through to install the plug-in, perhaps this will be helpful to someone!

My company is running a a blog using the 2.7.1 version of WordPress hosted on our own server. I set up a brand new report suite in SiteCatalyst just for the blog, exported the new s_code.js file and moved it to the linux server. Once on the server it was just a matter of moving the plugin files into the wp-content/plugins/ folder.

Then move the new s_code.js file into the wp-content/plugins/OmnitureSiteCatalyst/js/ folder. Once all the files are on the server, login to the admin section of your blog, and under Plug-ins, find and activate the Omniture plugin.

omnisettings

You're almost there. Next you go to Settings > Omniture Settings.

On this page you provide the plugin with the pathing information to the s_code file. The last item on the page needs the noscript Image url like this : http:/yournamespacehere.112.2o7.net/b/ss/reportsuite-name-here/1/H.20.3--NS/0

All that is left is to turn on the tracking and you're done.

Note: We were using the "Bookmarkify" plugin to add those handy links to the share the blog posts with others, but adding the Omniture plug-in caused some formatting issues with text wrapping all over the place. I switched to a different extension called: Add to Any, and it works fine.

Within 20 minutes I was seeing the data flowing into my reports in Site Catalyst. Start to finish this project took about 1 hour, not counting the time waiting for the data to show up in SC.

-Rudi

NOTE: If you see the error below when trying to activate the plugin, it is most likely due to an issue with PHP versions. The plugin works on PHP 5.x but not 4.X version.

Parse error: parse error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /home/content/r/s/h/code/html/codedir/wp-content/plugins/OmnitureSiteCatalyst/inc/omnitureControlClass.php on line 9

Share/Save

Tagged as: Omniture, SiteCatalyst, Web Analytics, Wordpress 8 Comments

« Newer Entries Older Entries »