There are many excuses I could list, or hide in the shadows and hope that no one else would find out about this, but I won't.  I knew when I took on this project that I did not have the time right then to work on the project and I should have not signed up for the project, but I did.  Thankfully, Ridder, was totally committed to the project stepped in and did all of the work for the client.   I sent my apologizes on to the client, my mentor, and even to Eric Peterson.  All of which were extremely professional and really speak to the quality of the work and people contributing to the Exchange.  It is because of this quality that I wanted to write this post.  I truly do feel bad for the position that I put both my mentor and the Analysis Exchange in,  but the more I thought about it the more I felt it really echoed what happens on many, many projects out there in the real world.

Things happen, deadlines are missed, and projects fail.  That is a fact of life, not just in the confines of the measure community but in all aspects.   I can not change the things that have happened in the past, all I can do is to accept responsibility for my inability to contribute on the project and make damn sure that does not happen again.   Fail faster is a phrase you hear frequently in the measure community, now having earned that badge :/ it is time to try again.  And try again I will.  But this time I will be better prepared.  I will take more time to evaluate the project before putting my name in.  I will make sure I have the time to commit to the project.  I will strive to make a positive impact on the project.

If you have already contributed to the Analysis Exchange, thank you for all that you have done.  If you have not, don't be afraid to fail.  Try it!  If it does not go well, accept it, figure out what went wrong, fix it, and try again.

-Rudi

Share/Save

Not too long ago I added one of the "Share this page" scripts, AddToAny, to our web site.  This seemed like it was going to work fine but this approach had 3 major drawbacks.

1. Most of these services require you to link to their JavaScript file on their servers.  Sure this is fairly reliable but I am not a fan of this approach.
2. Limited tracking / analytic capabilities.
3. Cookies you can not control.

The first two issues are not huge issues, but while we were testing the site, we noticed that the scripts were adding a few of their own cookies to our users.  I understand why this is, but I did not like it and the feature was pulled.  So I tested out another one, Share This, and it did the same thing. Not only do they add cookies to your users, but they are also tracking usage of their tool on your site.  I don't blame them for this, after all they are providing this as a free service but I still do not like it.

After looking at the scripts for a while I decided that it could not be that difficult to write my own "Share this page" feature.

My goal was to create a widget to let users share the current web page without the limitations listed above.  With just a wee bit of research I found the methods needed to be able to share a page via email, Twitter, Facebook, and LinkedIn. And then track the usage of data in Omniture SiteCatalyst.

<ul>
  <li><A onClick="jsFunctionToRecordClick('Email');" HREF="mailto:?subject=#variables.emailSubject#&body=#variables.emailMessage#">Email </a></li>
  <li><a onClick="jsFunctionToRecordClick('Twitter');" href="http://twitter.com/home?status=#variables.twitterLink#" target="_blank">Twitter </a></li>
  <li><a onClick="jsFunctionToRecordClick('LinkedIn');" href="http://www.linkedin.com/shareArticle?mini=true&url=www.rudishumpert.com&title=AmazingArticle&summary=This is the best ever&source=Rudi"  target="_blank">LinkedIn </a></li>
  <li><a onClick="jsFunctionToRecordClick('Facebook');" href="http://www.facebook.com/share.php?src=bm&u=#variables.currentPage#&t=#variables.twitterLink#&v=3" target="_blank">Facebook </a></li>
</ul>

Sample links without the tracking added:

• Email
• Twitter
• LinkedIn
• Facebook

And then the JS Function: Note the JS function is specific to Omniture tracking but this could be leverage for any analytic solution with some minor tweaking.

			function jsFunctionToRecordClick(category){
				var s = s_gi(s_account);
				s.linkTrackVars="events,eVarN,propN,propN";
				s.linkTrackEvents="eventN";
				s.events="eventN";
				s.eVarN=''+category+'';
				s.propN=''+category+'';
				s.propN=''+category+' | '+s.pageName+'';
				s.tl();
				s.events="";
				s.linkTrackEvents="";
				s.linkTrackVars="";
				s.eVarN='';
				s.propN='';
				s.propN='';
			}

The feature is added to the page using a jQuery menu script that creates the same mouse-over drop down effect that the free scripts use, but you can use any sort of presentation approach that fits your web site's style.

And that is it.  You know have your own custom share this web page feature that your can style however you like and maintain complete control over what cookies are used on your site and what level of tracking you would like to get out of the widget.

Share/Save

One url. page.cfm?urlVariable=1 , page.cfm?urlVariable=2, page.cfm?urlVariable=3. They all showed up as page.cfm in the reports. And while Eloqua does have features that allow you to set up a query string in the admin console, you have to assign each value ahead of time and from what I have been told by folks both inside and outside of Eloqua, you are not able to use those values for certain types of behavioral tracking and filtering.

NOTE: I claim little knowledge of the inner workings of Eloqua and have had to take the word of the support folks and the documentation I could find. If you know this to be different, I would love to hear from you.

After much time spent scouring the web I found this article on an Eloqua blog.
http://eloqua.blogspot.com/2010/05/fun-with-eloqua-and-jquery-tracking-pdf.html

The author of this blog, used a secondary tracking script from Eloqua ( elqFCS.js) and leveraged this and jQuery to auto tag links to any pdf on the sample site. Seeing this approach I was pretty sure I could use this method to meet my goal.

Step 1: Add the link to the additional JS file. It should be part of the standard implementation scripts.

 <SCRIPT TYPE='text/javascript' SRC='/elqNow/elqFCS.js'></SCRIPT>
 

Step 2: Check for the dynamic page, and if found create a "static" url to send to Eloqua.

 <cfparam name="url.urlVariable" default="">
<cfif cgi.path_info EQ "/dynamicPageInQuestion.cfm" and LEN(url.urlVariable) GT 0>
	<script>
		$(document).ready(function(){
			var fullurl = '<cfoutput>http://www.yoursite.com/NameOfYourChoosing/#url.urlVariable#</cfoutput>';
			elqFCS(fullurl);
	 	});
	</script>
</cfif>

That's it! Now inside of Eloqua in addtion to seeing a visit to /dynamicPageInQuestion.cfm you will also see

http://www.yoursite.com/NameOfYourChoosing/1

http://www.yoursite.com/NameOfYourChoosing/2

http://www.yoursite.com/NameOfYourChoosing/3 etc or whatever value you need to be able to filter on.

As of now, this is working and meets the goal / need I had. I'm curious if others have dealt with this, and if so what solutions did they come up with.

Share/Save

There are many, many blogs and folks that spend a lot of time talking about how to do analysis of all the data that folks are collecting with various tools, but there are not that many that really go into the topic of tagging, or implementation, or just data collection.  Perhaps it us because it is more technical, geeky, and flat out just not as sexy as other topics.  But this white paper really stood out for me as my main focus in web analytics is data collection.

The white paper outlined the following issues with tagging as it exists today.

In Web Analytics Demystified’s opinion, the problem with tags is three-fold:

• Tags become a panacea, replacing sound business measurement practices
• Tags can slow down page loading and degrade the consumer experience
• Tags have the potential to erode data  confidence when poorly managed

I would add a fourth item to this this.   Lack of skilled staff to implement/manage tags.  Sure there are lots of companies and consulting shops that can do this for you, but most companies do not have this type of talent on staff, or they do not have full access to this type of IT resource .

Some of the causes listed in the white paper for the proliferation of tags were:
More Tags Does Not Mean “More Accuracy”
I agree in this statement, but what about the use of two tools for validation of trends, not the confirmation of numbers?  Although with the right tag monitoring tool in place the need for this would greatly diminish.

Data Confidence

Load time
I have seen this first hand, and yes the tags can slow down a web site, especially when you have have multiple tagging solutions in place. ( Which is why you should track load times ) The other thing to watch out for is as more and more site use Ajax and the likes to provide a rich experience for the end user, there is a risk of double tagging a page if the developers are not careful in how they load content on a page and that can result in all sorts of wonky data.

This may all sound a bit daunting, but fear not!  The white paper has a solution for this very need.  A "Chief Data Officer"!!  The white paper does a great job explaining the responsibilities that the CDO would have, but what it all boils down to is someone to own all aspects of data collection with regards to analytics.   As a developer who is also tasked with these responsibilities I am thrilled  about this.   As sites become more complex and the tagging solutions evolve with them, the need for a technical person who can fill this role is crucial.   My hope is that companies will read and adopt this quickly.

Share/Save

I was a little confused but went ahead and typed in the url and was taken to a clever micro site that had be created / customized for me.  I clicked around a bit and was impressed with the interaction of the site.   I did not think too much of this and went back to my code.  In less than 20 minutes I received a work email from a sales guy.

Rudi,

Good afternoon.  I sent that hotel keycard & napkin, and wanted to hear your thoughts of that personalized web experience.

May I request a discussion, maybe Wednesday afternoon?  Let me know what works best.

I’m also happy to send additional information at your request.
Cordially,

Sales Guy

Now, being more involved in the analytics space I was impressed.  Here was a very clever mail to web campaign and it had worked.  I went to the web site, they detected that and sent a timely email about the experience.   I was thinking about responding to find out more about the site/product/solutions.

But then my desk phone rang.  I still had the email from the sales guy up on my screen and the phone number on the caller id matched the email.  I chose not to answer, but did listen to the voice mail.  Sure enough....it was the sales  guy, letting me know that they had tracked me and like Will Smith in "Enemy of the State" they knew my every move.   Well maybe I paraphrased that last part.

This is where they lost me.  This clever campaign went to creepy in less than 20 minutes.   I thought about it for a little while and then emailed the sales guy.

Dear Sales Guy,

With the email then the voice mail it went from Clever to Creepy pretty quick.

A short time later, he responded.

Rudi,

We have no intention to creep you out. We just wanted to show you our capability of being able to put a message in front of a prospect and know in real time that they are looking at it. I want to share an actual VLG customer lead generation campaign.

This dialog marketing campaign has generated a 38% mail to web response. Just click the link below:

(link removed)

I'd like to answer your questions and provide more information regarding our capabilities at VLG. Please let me know a good time to have a brief discussion.

Cordially,
Sales Guy

I do not fault the intent behind this particular sales pitch, but something about it did not sit right.  I am fully aware of the effort and opportunities that such a solution could have, but the creepy factor has outweighed the clever factor for me.

What do you think?

Share/Save

The developer side of my brain refuses to believe that there is only one way to do things, so after spending a great deal of time and effort to integrate SalesForce data into Omniture using the standard Genesis integration I felt that there had to be another way.  If you have not read the recent posts by Adam Greco on getting CRM data into Omniture, stop reading this post and go read those first.  Then come back!

What I needed to do was find a way to get a few data points out of SalesForce and into Omniture SiteCatalyst.  The solution also needed to be automated so that it could run every 3-4 hours.  After thinking over the topics discussed is Adam's blog post I had a plan.

The Challenge:

State over time.  That is what this whole exercise comes down to.  How to get Omniture SiteCatalyst to store and measure the state of a data point over a set time.  These data points are up to you and your specific business needs.  Some examples are revenue, leads, etc..

The granular level of data you can/want to pull over is limited only by your your business objectives.  For the purpose of this post, I will only be talking about getting data at a campaign level.

The Setup:

Transaction ID's and a matching key in SalesForce.  If you can, I strongly recommend using the SalesForce campaign id's as your web analytics campaign ID's.  It give you a great 1:1 data point between the two systems.  It also makes it easy to use that campaign ID as your transaction ID.

Incrementor Events.  (2 for every data point in SalesForce that you want to integrate)  These are needed to accomplish the heavy lifting of the state over time.   If you want to track revenue attributed to a specific campaign for example, you create 2 events.  One revenue_positive event, and one revenue_negative event.   Later you will create a calculated metric to get the delta of these two events to get the actual number.

State Manager.  You have to have some mechanism to get the data out of SalesForce and then be able to determine the difference in the value of the data points you want to integrate into Omniture.  There are numerous ways that you could accomplish this, but I chose to write a custom ColdFusion / SQL solution.

The flow chart above shows at a high level all of the steps in the process.

1) Pull a list of transaction ids/ campaign ids from Omniture and store that list in a new db table.

2) Loop over that table and query SalesForce to get the data points you want to move, and store that in a second database table.

3) The very first time you run this process you are creating the state.  This copies the data into the third state database table.  Each time after that, you compare the values in the 3rd table with the data in the 2nd table.   This drives the values you pass into the incrementor events.   If the first time you pull data from SalesForce to find the revenue for a campaign is $100.00 that gets stored in the third table.  You pass 100 to the revenue_positive and 0 to the revenue_negative.  The next data pull the revenue is now 110.  After the comparison, you pass a 10 to the revenue_positive and 0 to the revenue_negative.  Now on a future data pull, you find the revenue is down to 50.  You now send a 0 in the revenue_positive and a 60 to the revenue_negative events.   When you create the calculated metric you will see the new value of 50 for that calculated metric.

<cfset variables.revenuewon_str="#variables.revenue_pos_event#=0|#variables.revenue_neg_event#=0">
<cfif variables.DIF_revenuewon EQ 0>
	<cfset variables.revenuewon_str="#variables.revenue_pos_event#=0|#variables.revenue_neg_event#=0">
<cfelseif variables.DIF_revenuewon GT 0>
	<cfset variables.revenuewon_str="#variables.revenue_pos_event#=#variables.DIF_revenuewon#|#variables.revenue_neg_event#=0">
<cfelse>
	<cfset variables.revenuewon_str="#variables.revenue_pos_event#=0|#variables.revenue_neg_event#=#ABS(variables.DIF_revenuewon)#">
</cfif>

The code sample above evaluates the difference in the data point between tables 2 and 3 and generates the string required to send the data to Omniture.

4) Push the data to Omniture.  After you create the txt file with the transaction id and the values for the events, set up an automatic ftp using the Omniture DataSources.

5) Automate.  Since the controlling code to power this process was ColdFusion, all that was required was to set up a scheduled task within the ColdFusion admin and done!

The Result:

My Photoshop-fu is weak.

Now, right inside of SiteCatalyst, you can see SalesForce data points that matter to you in your reports.  Of course, the data will look much cleaner that my mocked up image...hopefully.

Share/Save

What does Practical Analytics mean?  Here is my spin on it:

Practical Analytics is the process of using web analytic data to help guide infrastructure,  features, and  support of a web site or web based application.

Really it comes down to makes changes on your site that make it easier to manage and maintain, not necessarily changes that make it a better experience for the end user of the site itself.  The data used to make these changes is not hard to get to, nor does it require any deep analysis.  Most of the time it is data contained in the most basic, canned reports available in almost every tool.

So what?  Well as a career developer, I can not tell you the number of times I would have killed to have had the type of usage data I have now to not only help guide change, but to be able to use this data to help convince the HiPPOs out there that these changes needed to be made.

This is extremely important to me right now, as I am knee deep in a major redesign effort.   As part of the planning process for the redesign there have been countless decisions made based on analytic data we had, and over the next few blog posts I will be highlighting some of my favorites.

Practical Analytics: Use Case #1 - Kill the old, tired, busted, outdated pages.

I am sure this is hardly news to anyone, but as a company constantly adds content to their site to keep it fresh and current, there is often a multitude of old outdated pages that never quite seem to get deleted.  Perhaps the thought is that they need to be kept for SEO, or someone may have a bookmark to the page, or more than likely a new page version with a new name was published and the old file was never deleted.

So use your web analytics tool of choice and pull a list all the web pages with any traffic at all for the last six months.   The most basic of reports.  Then get a list of all the files currently on your server.  Apply a little excel magic and you will get a list of pages on your site with zero traffic in the last six months.  These are the first ones to go, no one will miss them at all.

The next step would be to look at the ones that are really lagging far behind.  This will take a bit more time to go through that list and see if these pages need to go, or need to be improved.  Either way, you have made the maintenance of your web site a bit easier by removing the pages with little or no traffic.

If you are truly concerned about users that might have a bookmark to one of those old pages, then you could easily modify your 404 process to send users to a search results page or some other custom 404 solution.

This is simply one of many practical applications of analytics data that will not only help you clear out old content, but should make the overall task of site maintenance easier.   This should please even the most obstinate of curmudgeon developers out there!

Share/Save

A few months back I was lucky enough to get a copy of "User Driven Change: Give Them What They Want" by Carlos del Rio & Jeff Noethen.  When it arrived I set it on a stack of other books in my ever growing pile of books to read.   To be honest I had forgotten about it until I received a nice "nudge" on twitter asking what I thought of the book.

Well, I finally got around to reading it.  I was blown away!  Not only was it a nice fast read, but the information was broken down in great examples.  The book starts off with how to make a site quick to use and engaging, and breaks that down into the following points:

1. Site Speed
2. Short Action Process
3. Intuitive Design
4. Clear Messaging
5. Compartmentalization
6. Third Party Integration

Impressively, the authors take their own advice and apply most of these points to the book, making it both quick and engaging!

1. Site Speed:  The book is only 130 pages and can easily be read in one sitting, although I am sure that I will be re-reading it with a highlighter and note pad in hand.  It does not get bogged down in useless information.

2. Short Action Process: With each section of the book, there are examples/suggestions to put the topic into action on your own site.

4. Clear Messaging: No fluff.  Straight to the points and to the real meat of the content.

5. Compartmentalization: Each section is broken down into small items that can be taken and used on small sections on your site or as part of a larger project.

While this book is not written for someone new to the measure space, there are great insights in this book than can be leveraged by people at all skill levels.  After reading through a few very technical books, it was nice to have a light, quick read that is still packed with useful information in an easily digestible format.  I would recommend this book to anyone looking for more insight on improving the site experience for your users, and I am looking forward to their next book!

Share/Save

Before we get into it, there is a key point I want to make about the data.  The data base that you get from Jive is not your typical clickstream data set.  It is an activity database.  You will not get pagenames, or visitor session information.  What you will get is an activity logged for everything a users does on the community site.  Views/creates/modifies  a thread, blog post, question, poll, etc..   If the user is logged in, you get their user id, name, etc..   If the user is not logged in, they all show up as a single user. Even with this limitation, there is still plenty of useful data to be found.

Configuration requirements/prerequisites: While the end solution is fully automated, there is a fair amount of configuration that most be completed.

ColdFusion Server: The main controlling files are cfm pages that are called via the CFAdmin / Scheduled tasks.  This process could be accomplished using your scripting/coding language of choice.

PostgreSQL: The .dmp file that Jive provides is in the PostgreSQL format.  This is a free/open source database solution.  I found that the built in admin works ok for setting up the database and user to be used for the scripts, and for creating any views to assist with the ETL process, but is severely lacking in terms of exporting capabilities.

• Create 2 views to pre-process the data for extract
  • Known Users
  • Unknown users / guests
  • Define headers of views to align to Omniture - Data Source file requirements.

SQL WorkBench :  A free / open source db admin tool with exceptional data export features which are all accessible via the command line interface.  Once you install the tool, you will need to create a connection profile to be used in all scripts.

• Create SQL queries to perform data extract
• Need 1 .sql file for each query
  • creates .txt file with data ready to ftp
  • creates matching .fin file to ftp

Command line / batch file access: While most of the controlling files are ColdFusion pages, the files that perform the restore and data extraction are batch files.  It is up to you to use the format of calling these batch files that you are most comfortable and confident with.

Omniture Report Suite: Before uploading any data, make sure you have planned out what data points you want to capture.  Walk through the tables in the .dmp file to see what elements are most important to your business needs.  Once you have this, work with Client Care to set up the report suite.  Below is a list of some of the items you will want to consider.

• Define props / evars / events
• Enable custom visitorID (uses userID from Jive)
• Enable timestamps
• Generic Data Source setup with full processing
• FTP information

Local Folders: Working directory to hold batch files, cfml pages, data extracts, and a sub folder to move completed files to.

Once all of the configuration steps have been completed, you can begin tackle the automation.

Work Flow - Steps

1. Download daily dmp file from Jive of the Analytic / Activity.
2. Restore dmp to local postgreSQL db
3. Extract data
4. FTP data extracts to Omniture

Only 4 steps!  That is not so bad.  So lets look at what is involved in each step.

Step 1: Jive provides an "Analytics" database in either a .sql.gz  or  a.dmp file.  I say "Analytics" because the data does not contain all of the traditional analytics information, page views, etc... What it does hold is activity.  Every time a user views a thread, blog post, poll etc... that is logged.  As is when users create content for the site.   All of this information is held within the myriad of tables in the .dmp file.  The database is a PostgreSQL format

The challenge is how to automate the download of this file.   I used a CFHTTP call as it allows me to provide a userid/password to authenticate into the Jive Cloud Admin site to retrieve the file.  It is also an easy way to customize the filename to include the date.  Each .dmp file is named in the following format:  accountname-yyyymmdd.dmp

		<cfhttp
				username="yourLogin"
				password="yourPassword"
				method="GET"
				url="#variables.URLLocation#"
				result="dmpGet"
				resolveURL="yes"
				getAsBinary="yes"		/>

Once you have written the script to pull the database you have to schedule the download around the processing that Jive performs.  Each day, they delete the previous day's file and begin the process to create the next day's file.  This can take anywhere from 2-6 hours and during that time the new .dmp file is not there.  Each file is a full dump, so don't worry if you miss a day, you will always be able to go back and retrieve past information.

If the call to download tries to get the .dmp file when the file is not yet ready I create a  db_download.fail file in the working directory.  This is mostly used for debugging purposes.  Once the file is successfully downloaded I create a db_download.done and a db_download-yyyymmdd.done file.   The db_download.done file serves as a flag to the next step that the dmp file is there an ready to be restored.  The db_download-yyymmdd.done lets the download process know to not attempt to download the dmp file again for that day.

Step 2: Restore .dmp to local postgreSQL

The controlling cfml page checks to see if the db_restore.done exists.  If it does, it executes a batch file that uses a command line command to restore the database and once the restore is finished it creates a db_restore.done file.  It also moves the db_download.done to the processed folder within the working directory and renames it to db_download-yyyymmdd.done.completed

"C:\Program Files\PostgreSQL\8.4\bin\pg_restore.exe" --clean --host %server% --port 5432 --username %username% --dbname %database% --verbose D:\WorkingDirectory\db.dmp

Step 3: Extract Data

The controlling file checks to see if the db_restore.done file exists.  Once it finds the db_restore.done file, it executes each predefined  .sql file.  These files create a daily-dataset.txt file that is properly formatted to be ftp'd to omniture.  It also creates a .fin file of the same name to be ftp'd as well.   Once all of the .sql files have been processed it moves the db_restore.done file to the processed folder within the working directory and renames it to db_restore-yyyymmdd.done.completed.  The controlling file also creates a db_extract.done file.

WbExport -type=text
         -file='d:/workingdirectory/dailyfile.txt'
         -header=True;
// pseudo code
SELECT  Your data
WHERE to_char(data.date,'mm/dd/yyyy') = to_char(current_date-1,'mm/dd/yyyy');
WbExport -type=text
         -file='d:/workingdirectory/dailyfile.fin'
         -header=false;
select * from jivedw_user where user_id = -99;

Step 4: FTP completed files to Omniture

The controlling file  checks to see if the db_extract.done file exists.  Once it find this, the I use  CFFTP to open a secure connection to the Omniture FTP server defined in the configuration.  Each file is ftp'd to Omniture along with the matching fin file.  Again these files are also moved to the processed folder in the local working directory and renamed with the time-stamp.

Click to see full size

Next steps? Or as Avinash likes to say... So What?

Now that you have a daily process that will pull, transform, and load the activity data from your Jive installation into Omniture, what else can you do/discover.

• Find out which areas of the community are generating the most content
• Create automated report publications to community administrators / moderators
• Easily identify the most active:
  • Users
  • Companies
  • Employees
  • Topics
  • etc.......

These are just a few things you can do with the activity data once you have it inside of Omniture.  What are some of the things you will use the data for?

Share/Save

Let me start with saying that I think true value of a membership in the WAA, or any user group like this,  is dependent on what you are willing to put into it.  Membership is not a passive experience.    My personal goals in joining the WAA were:

• Education
• Networking
• Collaboration

Education:

As I become more and more immersed in the world of analytics, I am constantly looking for way to expand my knowledge.   As part of this process I wanted to be able to participate in the WAA committees, forums, peer reviews, webcasts, etc..    Being able to join the committees and not only participate in the discussions, but to learn from the experiences of the other members of great value to me.

Networking:

I love being able to interact with others that are passionate about web analytics.  To share experiences, challenges, failures, and successes and to build relationships with others in the industry is great.  It is true that this can be done without the WAA, but for me,  it has opened up another set of people to interact with that I had not yet, or might not have the had the opportunities to.

Collaboration:

The developer in me loves standards. Love, love, love, love... Standards.  So the opportunity to be part of a group/committee that discusses and helps shape those standards is a very exciting offer.  I am still getting my feet wet in this area, but I look forward to becoming more active in this area.

Based on these goals alone, I do feel that I get a great value for my membership in the WAA!

There are other great groups and projects out there, like the Analyis Exchange where you could accomplish these goals, but I do not feel that participation in one group should preclude you from participating in the other.   I love talking about analytics with whomever will listen and through these conversations, this engagement, and healthy debate on ideas true innovation happens.    There is something great about taking an idea and throwing it out for the world to see, comment on, and mold into something new.

Share/Save