Omniture – SiteCatalyst WordPress Plugin « Rudi Shumpert : Code By Numbers

Omniture – SiteCatalyst WordPress Plugin

Project Page

Description:

This plugin will add Omniture SiteCatalyst tracking features to your wordpress blog without having to know any PHP, edit code, or cut and paste tracking code to footers. Also, if you change or update themes, you will not have to remember to update tracking code.

As of version 0.1.0 there is an optional reporting feature using the Omniture SiteCatalyst Widgets. You have two options to see data from your Omniture SiteCatalyst account within the Wordpress Admin.

The first option is to enable a single widget on the WordPress Dashboard itself.

Embed Reportlet in WordPress Dashboard

The second option is to add a new page to the Dashboard menu which can hold multiple widgets and the number is set from the admin settings.

You can have both reporting options enabled at the same time. The data displayed in the widgets is defined within the SiteCatalyst GUI. Once you create a reportlet and save it to a dashboard you should be able to select the reportlet from within the widget. You will have to login to the widget using your Omniture login at least once. Then refresh the page and the other widgets should then be logged in as well.

NOTE: This is an alpha version.

Requirements:

Omniture SiteCatalyst Account
Ability to load the omniture s_code.js file to your server with the report suite id filled in.

Optional:

s.props to capture internal search data
s.props to capture logged in status
SiteCatalyst Widget path

How to install the plugin:

Manual: Download the latest plugin from the Wordpress site. http://wordpress.org/extend/plugins/omniture-sitecatalyst/

Automated:

1. Log into your blog. Under Plugins -> Add New search for Omniture SiteCatalyst You should see it in the list:

2. Select Install. Once it is completed, you will see "Omniture" in the Settings Menu.

Version 0.1.0 Menu

Enter in the fields, select update and you are done. The tracking is live!

Version History

0.0.1.2 Alpha
Initial Release: January 2010
Tracks basic traffic & logged in status of users
Added basic tracking of internal searches & ability to set domain information
404 page tracking with page recorded
Ability to track/not track blog administrators

0.0.2
Ability to set eventN when comment is added
Ability to define which eventN in the admin settings

0.1.0
Added reporting widgets.

If you have any suggestions or comments, please let me know! Thank you for using the plugin.

Share/Save

Comments (27) Trackbacks (4) ( subscribe to comments on this post )

Dan Cross
January 14th, 2010 - 10:13

I’d love to see the ability to fire an event when a user leaves a comment. I’d also love the ability to add author name to an s.prop for blogs with multiple authors. But, a nice easy looking tool!
Rudi
January 14th, 2010 - 15:51

Updated Version 0.0.2 – You can set an event number in the admin screen and it will capture that when a comment is added.

-Rudi
Ian Andersen
January 14th, 2010 - 21:47

Hi Rudi,

Looks like a great plugin that will be useful. One question before I install though: What is the URL Campaign Variable used for? Does the plugin create campaigns at all? Or is this just a way to catch campaigns that I may be running? I just want to be sure campaign data won’t be added to my existing Omniture data. Thanks.

ian
- Rudi
  January 14th, 2010 - 21:52
  
  Ian,
  
  If you fill in the “Url Campaign” variable it will pass any tracking code it finds in that url variable to the s.campaign variable. So if you are going to use the same report suite with this plugin you will need to be careful with that.
  
  Thanks for trying the plugin.
  
  -Rudi
Rudi
January 16th, 2010 - 21:35

Question from the contact form:
From: Ottley Holmes

Message body:
I installed your plugin on my Wordpress site. When I went to take a look it shows a dialog box asking for username and password. Is this a free plugin? And if so what username/password do I use?

I’m stumped. Thanks for your anticipated help.
—————————————
Ottley! Thanks for trying out the plugin.

Which screen do you see the login on? The Omniture Widgets require that you login with your existing SiteCatalyst credentials. The plugin itself requires that you have an existing Omniture account.

-Rudi
Ian Andersen
January 18th, 2010 - 20:10

Thanks Rudy. Looks like it’s working well. Great plugin. Everything’s working so far!

Ian
Ian Andersen
February 3rd, 2010 - 13:33

Hi Rudi,

I have the my WP Omniture data going into my master report suite in that I use to track my public website which is completely unrelated to wordpress. I activated WP Omniture under the assumption that I would easily be able to segment out blog traffic from my report suite. I’m finding that it is actually very tricky.

With WP Omniture you pass in the post title as the pageName; the category as the Category; and some prop variables for user behavior. But I don’t see any common element attached to pageName or category. Therefore, to segment out all blog pages I’d have to use an advanced filter to enter in all the post titles that have come into the system so far.

It would be great if there was an option to add a prefix to pageName or category. That would fix the problem right up for me. That way all the pageNames that came from my blog could have “The Awesome Blog -” attached to the beginning.

Am I missing something here? I really need an easy way to segment the data coming from the blog.

Thanks,
Ian
Ian Andersen
February 3rd, 2010 - 13:49

I already have a solution after only a few minutes in the code. To add a prefix to s.pageName, s.channel, and s.pageType you can just find these three lines in omniture.php:

s.pageName = “‘.$pageName.’”
s.channel = “‘.$channel.’”
s.pageType = “‘.$pageType.’”

And hard code the prefix like so:

s.pageName = “My Blog – ‘.$pageName.’”
s.channel = “My Blog – ‘.$channel.’”
s.pageType = “My Blog – ‘.$pageType.’”

This should make the plugin work perfectly for me. Thanks!
Kyle
February 8th, 2010 - 12:53

When I install this plugin I get a blank screen, no error even when I set error_reporting to E_ALL, and have to delete it to load any part of the blog again. I’m using wordpress 2.9 – Has this plugin been tested with 2.9 yet?
- Rudi
  February 8th, 2010 - 12:56
  
  Kyle,
  
  I have this plugin running on 3 sites all with wordpress 2.9.
  Can you tell me more about the environment you are on?
  
  -Rudi
Mike WebGuy
February 16th, 2010 - 18:42

Any idea why I’m not seeing image requests being fired off ? I’m pretty sure I have configured it correctly and I’m providing it with the correct path to my .js file: http://www.mikewebguy.com/s_code.js
- Rudi
  February 16th, 2010 - 18:52
  
  Mike,
  
  When I went to your site I could see the code firing via WASP. In the admin settings for the plugin what is the “Track Admins” setting?
  
  -Rudi
Riju
March 25th, 2010 - 06:21

I have a question. Will this plugin work both in WordPress and WordPress MU ? I have a MU blog with 3 blogs in it.
- Rudi
  March 25th, 2010 - 06:30
  
  Riju,
  
  I have not tested it on WordPressMU. But I know it works on regular WordPress sites.
  
  -Rudi
dude
April 30th, 2010 - 10:38

Hi Guys,

Anyone got this working on an wordpress MU Version ? or do i need to put the omniture code on the footer.php of the different themes ?
- Rudi
  April 30th, 2010 - 12:19
  
  I’ve have not personally tested this on a MU install, but I have been told that it works.
  
  -Rudi
Sarah
May 11th, 2010 - 13:34

How do I get an Omniture account? Is it free? I couldn’t find anything on the website.
- Rudi
  May 11th, 2010 - 13:59
  
  Sarah,
  
  No, Omniture is not free. http://www.omniture.com/en/contact/sales
  
  -Rudi
Josh O
June 8th, 2010 - 17:18

Are you sharing your dev plan?

The plugin currently uses the page title as the s.pagename. It would be nice to be able to override this on a by-page or by-post basis since many themes use posts and pages as alternate content types, and set it for special page types (archive, tag, etc) from within the UI.

An interface for how whether categories and tags are mapped as the channel, and setting other specific eVars and props either by hand or programmatically by post/page would also be handy and (ultimately) extensible.
- Rudi
  June 8th, 2010 - 18:48
  
  I have no firm dev plan, but I like all of your suggestions. Perhaps we could talk more about your ideas.
Chase
July 8th, 2010 - 16:58

Hi Rudi,

I’ve installed this, and have set it up per your specs, but the debugger is not showing any tracking. I have the tracker installed on a few static pages on my site, and it works like a charm there…

I am running WordPress 2.9.2 with a custom theme. I double checked and is in there.

Any ideas what might be keeping the tracker from being enabled?

Thanks,
Chase
- Rudi
  July 8th, 2010 - 17:11
  
  Chase,
  
  Check to see if you have the “don’t track admins” enabled.
  
  -Rudi
Chase
July 9th, 2010 - 08:04

Thanks for the response, Rudi. Admins are being tracked, and just to be sure, I tested on another browser. I have “cid” in the field for URL campaign variable… is this correct?

Thanks,
Chase
Chase
July 9th, 2010 - 08:20

Figured it out! My custom theme was missing the wp_footer tag in the footer.php file. I have remedied the situation.

Thanks for your help and for an awesome plugin.
Rudi
July 9th, 2010 - 08:52

Chase,

Glad you figured it out!

-Rudi
Chase
July 12th, 2010 - 08:06

Hi Rudi,

Sorry just have one more question- is it possible to make the s.channel and s.pageName different? Right now they’re just pulling whatever the URL is…

Thanks,
Chase
- Rudi
  July 14th, 2010 - 18:40
  
  I’ll take a look and see what is possible