Latest Posts

Archives [+]

The Clickstream Cloud

Customer Experience Management (CEM) aims to empower and delight customers by (among other means) giving web visitors exactly the information they need, in the right form, at the right time. Doing this reliably, in real time, can be a challenge. It requires Web Content Management software that can aggregate relevant user information from a variety of sources so as to drive intelligent provisioning of content on a page according to predetermined strategies.

Adobe's Web Experience Management offering (part of the new Adobe Digital Enterprise Platform) rises to this challenge with a patent-pending technology called the Clickstream Cloud.  

The Clickstream Cloud represents a dynamically assembled collection of user data that can be used to determine exactly what content should be shown on a given web page, in a given situation.

To see the Clickstream Cloud in operation, simply type Ctrl-Alt-C from within any web page. The Cloud summary toggles into view.

file

A variety of types of information are shown for the given user:

  • Profile data typically shows the user's registration data (assuming the user has registered with the website): Name, e-mail address, occupation, age, mailing address, phone number, and any other information the user has previously submitted in a registration process. This could also include social network information, data pulled from a CRM system, etc.

  • Tag cloud data shows the tags that were of interest to this user. Mousing over any of the tag names causes a tooltip to appear, showing the number of times the user has accessed a particular tag.

  • Page data shows the number of times the page has been visited, the page's title, and the Random factor as used in the random strategy of a campaign.

  • Surfer info shows the IP address, keywords used for search engine referral, the browser being used, the OS (operating system) being used, the screen resolution of the device the visitor is using to view the web page, and the mouse X-Y position on the page.

  • Events shows activity-stream information from SiteCatalyst.

  • Resolved Segments shows which (if any) defined segments of a marketing campaign have been matched.

Several things make Adobe's implementation of the Clickstream Cloud unique:

  1. Much of the information (such as info about the user's viewing environment) is derived on-the-fly, in real time.
  2. Marketers can experiment with different user-data values to see changes to a page in real time (for purposes of trying different campagin strategies). The Edit button in the upper right portion of the panel allows for manual editing (overriding) of user-data values.
  3. The Clickstream Cloud is extensible. You can add a new (custom) session-store object whose contents can be displayed in the panel.
  4. Non-volatile information shown in the Clickstream Cloud viewer is persisted on the client side (in a cookie), relieving the server of having to maintain (and then transport back and forth) large amounts of user data.

Because user info is persisted on the client, concerns over privacy and control of potentially sensitive user data are easily allayed: The user has ultimate control over the data.

The Clickstream Cloud is a container for different data stores (also called session stores), which extend either CQ_Analytics.SessionStore (for values computed on page load) or CQ_Analytics.PersistedSessionStore (for values persisted from one page to another).

Each data store is built up of property pairs (names and corresponding values) and represents a logical collection of properties (for example, profile properties).

The default session stores available in Adobe WEM can be obtained from a call to CQ_Analytics.ClickstreamcloudMgr.get(), which returns an object with properties of:

profile (correponding to CQ_Analytics.ProfileDataMgr)

eventdata (correponding to CQ_Analytics.EventDataMgr)

tagcloud (correponding to CQ_Analytics.TagCloudMgr)

pagedata (correponding to CQ_Analytics.PageDataMgr)

surferinfo (correponding to CQ_Analytics.SurferInfoMgr)

mouseposition (correponding to CQ_Analytics.MousePositionMgr)

There's much more goodness tucked away in the Clickstream Cloud's APIs, which we'll visit in another (followup) blog post soon. But for now, if you want to get into the details yourself, there's no easier way to get started than to consult our documentation here and (for even more detail) here.

 

COMMENTS

  • By Luis - 5:11 PM on Sep 01, 2011   Reply
    I need help from the DAY Community! :)

    I'm currently representing a former Microsoft firm based in NYC, who is looking for a DAY CQ resource. We are also open to someone who has been mainly a Java engineer with some minor DAY experience. Great firm with an amazing reputation, good compensation and longterm work.

    In addition we have a great referral program if this is something that your not interested in but know someone who might be.
  • By Ronan - 2:54 PM on Sep 12, 2011   Reply
    Interesting stuff. I wonder how this would work with the dispatcher cache?
  • By John Dolce - 6:46 PM on Sep 26, 2011   Reply
    I have entered my sitecatalyst information is the page properties, but I can't seem to launch the clickstream cloud page with ctrl-alt-C
  • By chandra - 6:47 PM on Dec 13, 2011   Reply
    All Segment resolving is happening in client side java script code. and finally resolved content are being displayed in teaser container.

    For me, the client is some external portal not teaser component in CQ5. so in this case the resolving mechanism has to be written in server side CQ5 script and all resolved teaser news content will be exposed as JSON on http.

    Does CQ5 provides something similar any thoughts on this.

    Do i need to rewrite the server side code of teaser-client.js and segmentationMgr.js etc?