- Andrew Kos
- Bill Burlein
- Bryan Williams
- Christian Vozar
- Jeff Brown
- John Kraus
- Joseph Mak
- Josh Durbin
- Mark Daugherty
- Matt Van Bergen
- Melissa Geoffrion
- Michael Kang
- Michael Chan
- Michael Hodgdon
- Mike Motherway
- Molly McDaniel
- Nadia Maciulis
- Pat McLoughlin
- Paul Michelotti
- Puru Hemnani
- Rohit Srinath
- Ryan Lunka
- Tom Kelly
Adobe Omniture and CQ WCM
Tuesday, July 5, 2011
Analyze your authoring, author your analytics.
I’m excited about this integration we’re doing right now, bringing Omniture analytics into their world of content management with CQ. I realize this blog gets readers of many backgrounds, so let’s clarify:
Omniture provides a rich suite of reports and analytics based on a wide spectrum of data, ranging from a simple anonymous page view to an authenticated user’s actions and page events.
CQ WCM provides a highly configurable and flexible web authoring experience for the non-tech savvy.
When wired together, web site administrators bring CQ’s level of flexibility and control into their analytics game. With Omniture in your CQ installation, you’re not only editing your analytics implementation on your site without seeing code, but you’re re-authoring content based on effective, custom tailored metrics about that content.
We’re also building Omniture into existing components to capture events related to them. For example, we’ve got a “video” component that authors drag onto a screen, allowing users to view a video there. By wiring Omniture in, we’re now capturing data each time the user watches the video. This same concept can be built anywhere, capturing events. How many anonymous users are filling out the mailing list form each month? How many authenticated users are searching the FAQ database? What percentage are new users? It’s fun stuff to know, but also carries great utility when the Omniture integration is planned for and designed well.
One of the many beauties of a Web Content Management system like CQ is source code organization. I’ve worked on a lot of projects from very small to very big enterprise, and I can tell you I’ve seen some crazy spider-webs of analytics code dispersed throughout many source files. I once picked up a PHP project where the previous developer had copied and pasted analytics code onto each template in the site, and then modified each pasting slightly to fit the needs there. It got ugly over time. In CQ, componentizing and modularizing it all into one encapsulated and controlled place is a real relief and will surely be a time saver as the customer’s intentions with Omniture mature and grow.
With more than 12 years of client-side development experience and seven years in server-side programming on the Java platform, Lance consistently strives for success. He has worked with business and government in varied sectors, from...
- Descriptive JMX Beans in AEM/CQ
- Invisible requirements within Business requirements
- Building a better Options Predicate
- Extensionless URLs with Adobe Experience Manager
- The Life of a Tester in Adobe CQ World!
- Limitations of the CQ Parsys Model and the Implementation of a Nested Paragraph System
- Using Apache FOP to generate a PDF document based on a form submission data
- Configuring SAML in AEM 5.6