• CQ 5.4
• CQ5 Mobile
• CQ5 Marketing Campaign Management
• CQ5 Social Collaboration
• Adobe’s Online Marketing Suite (Omniture)

Adobe's WEM. Source: http://www.cmswire.com

Looking at the above list, it could be one of the leaders in the area of WEM providing all the capabilities. I will cover details about each of the modules in my next post. But one important module which I wanted to highlight is CQ5 Mobile. Here is some description about CQ5 Mobile from Adobe’s site:

It is increasingly important that websites offer specific “views” for mobile devices, where these “views” typically are separate sites that share some content with the “normal” website. CQ assists you in creating mobile websites: when authoring a mobile page, the page is displayed in a way that emulates the mobile device, called an emulator. When authoring the page, you can switch between several emulators to get a real view of what the end-user will see when accessing the page.

In the out-of-the-box version, devices have been grouped into three categories – feature, smart and touch – according to the capabilities of the devices to render a page . CQ allows to create new device groups. When the end-user accesses a mobile page, CQ detects the device and sends the representation that corresponds to its device group.

CQ enables you to create a mobile site based on an existing standard site. It can be simply achieved by creating a livecopy of the standard site.

This defintely links back to my previous post :Content Delivery over Mobile: Mobile Apps Vs Mobile Web? this definitely a step towards mobile web over mobile applications for future trends.

From Google Blog:

“John Batelle once described search trends as “a massive database of desires, needs, wants and likes.” Looking at Insights for Search data, we were intrigued to find that this “database of intentions” shows consistent search patterns among Best Picture winners for the last three years. Each year, the winning film has shown an upward trend in search volume for at least four weeks, as well as highest regional interest from New York (The Hurt Locker, Slumdog Millionaire and No Country for Old Men).”

I can see such kind of apps getting more and more popular in the recent times to come. What the masses think?

There have been lots of posts around Fatwire and Google Analytics integration but none with much information. Here are some of the details which might help to provide some insight around integration:

There are four different types of tracking defined with the integration tag:

• Tracking the use of a particular asset; be a PAGE or any other type.  A PAGE asset will trigger a page viewed tracking event
• Tracking when a recommendation has been selected or clicked by the user
• Tracking when a list of recommendations is requested. The object type is set to RecAsked.
• Tracking when a recommendation is listed for display purposes. The object type is set to RecListed.

Based on above tracking system, two modes of operations are defined:

• Basic which tracks physical page views using the GoogleAnalytics (GA)  _trackPageview function and the request to display Assets using the GA Event facility function _trackEvent. This basically covers first tracking type.
  • Examples:
    • <Asset Name> [<Asset Type (c)>=<Asset ID (cid)>]
    • FSII Home page [Page=1223456789]
• Advanced is extension on top of the basic tracking system to record Engage Recommendation information. This mode makes extensive use of the GA Event Tracking facility to record asset related information for recommendations and segments. The three components of a GA Event (category, action, and label fields) are used to store FatWire information. This covers the last three tracking types.
  • Examples:
    • Recommendation Listed
      • <Recommendation name>  [recId = <recommendation Identifier>]
      • FavouriteBlogList [recId = 123456789]
  • Segment information with list of assets
    • FavouriteBlogList [segId = 123424325435], shishankinfo [Blog = 987654321], apoorvinfo [Blog = 1357924680], contentprise [Blog = 2468013579]

AddAnalyticsImgTag is the element that renders tracking request to an Analytics data collection server either FatWire Analytics product and/or a 3rd party product such as Google Analytics.

Example:

   <render:callelement elementname=”Analytics/AddAnalyticsImgTag”>

         <render:argument value=’<%=ics.GetVar(“c”)%>’/>

         <render:argument value=’<%=ics.GetVar(“cid”)%>’/>                                                           

         <render:argument value=’<%=ics.GetVar(“site”)%>’/>

         <render:argument  value=’<%=ics.GetVar(“childpagename”)%>’/>

         <render:argument value=’<%=ics.GetVar(“recid”)%>’/>

</render:callelement>

Reporting on Gathered Data

Once the data has been collected, it’s time to display them in different reports.  There are different options available:

• Directly login to Google Analytics and generate customize reports; this could be displayed within the Fatwire UI accessed through inline frame
• Custom reporting by accessing analytics data through the Google Data Export Protocol. The only caveat with this is that the web page producing the reports be accessible from the Internet.

Limitations of using Google Analytics

Google limits the amount of activity between a client and Google Analytics. Here are some facts:

• Maximum of 5 million page views per month for any Web property (unlimited if the site is a Google AdWords subscriber)
• No more than 500 tracking requests per session.
• No more than 10 requests in any given 1-second period.
• No more than 10,000 requests per 24 hours.
• Data query is limited to 10,000 entries per feed.