March might be my favorite month of the year. It usu­ally starts, as it did a few weeks ago, with Adobe Sum­mit, which is always a great time for learn­ing, net­work­ing, and shar­ing our vision of the future of dig­i­tal mar­ket­ing. Then March con­tin­ues with the NCAA Men’s Bas­ket­ball Tour­na­ment, my favorite sport­ing event of the year. And this year, March is excit­ing for an addi­tional rea­son: our lat­est release of Adobe Ana­lyt­ics, which hap­pened today.

In this post, I want to high­light a few of the changes you should expect to see imme­di­ately rel­a­tive to the Site­Cat­a­lyst por­tion of the Adobe Ana­lyt­ics toolset.

Cor­re­la­tions for All!

What do we want? Data cor­re­la­tions! Where do we want it? Everywhere! 

In my break­out ses­sion at Adobe Sum­mit ear­lier this month, I shared a tip which explained that newly enabled cor­re­la­tions in Site­Cat­a­lyst 15 auto­mat­i­cally pop­u­late with data going back to your SC 15 upgrade date.

That tip is already offi­cially out of date, as our engi­neer­ing team has now enabled all cor­re­la­tions out of the box in Site­Cat­a­lyst 15. This means no more enabling cor­re­la­tions in the Admin Con­sole, and no more call­ing Client­Care to get a five– or 20-item cor­re­la­tion turned on. All pos­si­ble data rela­tion­ships are avail­able auto­mat­i­cally, and those rela­tion­ships exist going back to your upgrade date.

Cor­re­la­tions are a key com­po­nent of Adobe Ana­lyt­ics which allow you to dis­cover the rela­tion­ship between data dimen­sions. As such, they are great for answer­ing ques­tions that span mul­ti­ple dimen­sions, such as “Which refer­ring domains drove traf­fic to my page?” and “What browsers are most pop­u­lar with my cus­tomers in Tokyo?” I’m very excited that users will now be able to answer more of these ques­tions, faster and more com­pletely than ever before.

Any­thing by Any­thing by Any­thing by Anything

An addi­tional ben­e­fit of this change is that all cor­re­la­tions are now n–dimen­sional. In the past, the most com­mon kind of cor­re­la­tion related two spe­cific items, such as Page Name and Search Key­word. You could break down one by the other (and vice versa), but that was it; you could go no deeper. Five– and 20-item cor­re­la­tions allowed you to drill more deeply into your data, but those were more rarely used. With this change, you can keep drilling into your data until you find that nugget of insight that you’re look­ing for, whether that means break­ing down Page Name by Search Key­word, or whether it means break­ing down Page Name by Search Engine by Browser by Geog­ra­phy by Video Name, or what­ever other dimen­sions you need.

As I hope you can see, this is a huge step for­ward for unlock­ing the value of your data within our web UI.

PTI (Push to Implement)

With this release, we are intro­duc­ing the most robust one-click mobile app imple­men­ta­tion avail­able any­where. With the Adobe Ana­lyt­ics mobile SDKs, one line of code now gets you rich user and con­tent data, includ­ing life­cy­cle met­rics such as installs, upgrades, launches, crashes, and more. All of this is avail­able with­out imple­ment­ing a sin­gle prop, eVar, or event.

I like to call it “Push to Imple­ment” (like “Push to Talk;” get it?) because it really is that easy. Once you’ve deployed the mobile SDKs accord­ing to the doc­u­men­ta­tion, you can now go to Admin > Report Suites, choose the right report suite, and then go to Edit Set­tings > Mobile Man­age­ment > Mobile Appli­ca­tion Report­ing. There, you will find a but­ton called “Enable Mobile App Life­cy­cle Track­ing.” Just press that but­ton, and all of the data I men­tioned above will become avail­able to you in out-of-the-box mobile app reports and dash­boards. Many users will now be able to do rich mobile app ana­lyt­ics and seg­men­ta­tion with­out using cus­tom vari­ables or a sin­gle line of addi­tional code.

My col­leagues will likely be blog­ging more about this soon, so I’ll link to their con­tent when it becomes available.

Login Improve­ments; Also, Ben Writes Some Code

It is true: I have code that went out with this release. Very excit­ing. I think we can say that it is a mile­stone in my life. With the care­ful over­sight of one of our most senior engi­neers who reviewed my code for me, I fixed a few annoy­ing issues rel­a­tive to the login process.

  • Many of you (led by Kevin Rogers, who orig­i­nally sub­mit­ted the fea­ture request in the Idea Exchange) have reported that it is a drain on your time to have reset your colleagues’ non-admin user accounts which have become locked due to too many failed attempts. We have added a link to the “Reset Your Pass­word” page in the mes­sage that users receive when they are noti­fied that their accounts have been locked. Hope­fully this will reduce calls/e-mails and free you up to do more analysis!
  • For new users, or those who have not vis­ited the login page since last clear­ing cook­ies, the default prod­uct ver­sion is now Site­Cat­a­lyst 15. You can still select Site­Cat­a­lyst 14 from the ver­sion drop-down on the login page, but this should hope­fully save time/confusion generally.

Meet s_fid: A Bet­ter Fall­back Vis­i­tor ID Methodology

In the past, when­ever a user did not accept the s_vi cookie, Site­Cat­a­lyst used a com­bi­na­tion of users’ IP address and their user-agent string to dif­fer­en­ti­ate one vis­i­tor from another. With the release of H.25.3 code and newer (, the JavaScript code now sets a first-party cookie called s_fid con­tain­ing a vis­i­tor iden­ti­fier gen­er­ated within the client code. This cookie is used to iden­tify vis­i­tors if the s_vi cookie can­not be set. (If nei­ther cookie can be set, the pre­vi­ous fall­back method is still available.)

This allows us to be more accu­rate in our fall­back vis­i­tor iden­ti­fi­ca­tion method. For exam­ple, if Bret Gun­der­sen and I are both brows­ing the same site from the new Adobe cam­pus in Lehi, Utah, we will appear to have the same IP address. We might even have the same user-agent string depend­ing on our browser and other fac­tors. This new method will ensure that we are mea­sured as dis­tinct visitors/customers.

Fur­ther­more, given that third-party cook­ies are likely to be blocked more fre­quently, this helps ensure that vis­i­tor mea­sure­ment con­tin­ues to func­tion accurately.

We rec­om­mend that you upgrade to code base H.25.4 to take advan­tage of this new fall­back vis­i­tor iden­ti­fi­ca­tion method­ol­ogy. If you’re inter­ested, you can read more about this in our online documentation.

Nam­ing Pro­cess­ing Rules

Pro­cess­ing Rules are a pow­er­ful capa­bil­ity in the Admin Con­sole which allows you to make minor imple­men­ta­tion changes on the fly with­out touch­ing any code. For exam­ple, you can cap­ture cam­paign track­ing codes, com­bine two vari­able val­ues, or label key­words as branded/non-branded. This is done by writ­ing some “guided logic” in a series of con­di­tional (if/then) statements.

In the past, you might have have five rules that all set a cer­tain variable—let’s say, the Track­ing Code variable—based on dif­fer­ent cri­te­ria. For exam­ple, some­times you want to set the Track­ing Code to the value of a query para­me­ter; other times you want to set it to the value of a dif­fer­ent vari­able. When you col­lapse all of those rules, they would all say “Set Track­ing Code con­di­tion­ally.” You would need to expand the rules to under­stand what they all do differently.

With this release, you can pro­vide a friendly name for each pro­cess­ing rule. The abil­ity to assign each pro­cess­ing rule its own name makes it eas­ier to set up and man­age them. Now you can know exactly what each rule does with­out inves­ti­gat­ing the logic or read­ing the notes inside of the rule. Thanks to Jason Paulsen for sub­mit­ting this idea in the Idea Exchange!

Not the End

FYI, we have now imple­mented nearly 200 of your fea­ture requests from the Idea Exchange!

There is even more to be excited about in this release, so please check out our Release Notes. As always, please let me know what you think by leav­ing a com­ment or hit­ting me up on Twit­ter at @benjamingaines. We’ll be back next month with more great addi­tions to Adobe Ana­lyt­ics. That’s right, more Adobe Ana­lyt­ics AND the start of the base­ball season.

Have I men­tioned that April might be my favorite month of the year?