Skip to main content

Adobe CQ - Site Catalyst integeration.



Create SC Framework and mapping

1.       1. Click in cloud service

2.       2. Click on ‘Adobe Site Catalyst’





3.     3.Add configuration. After clicking create, it will ask for username and password. Please provide same credential which you will use for connecting the omniture site.


4   4.Create Framework for defining the mapping.


5   5. Define mapping between CQ and Site catalyst variables. Before doing this mapping, CQ variables should be created in ‘test\pages\base’. Note - Site catalyst variables are created at Omniture.

Define CQ variables –
     1. Create analytics node in test/pages/base. 

     2. In cq:trackevents mention all the event names 
       3. In cq:trackvars mention all the prop and eVar names.

 

    Implementation approach –

     1.       Create a new category ‘sitecatalyst-lib’ under ‘etc\clientlibs\gs-clientlibs’. We will include this js category at base page so that it will be available to all the pages. Create js files here to capture all the common onLoad events. For example country, language etc.  Also put omniture plug-in js here to capture data like days since last visit.
    2.       Create js files at template level to capture all the template level onLoad events.
    3.       Create js files at component level to capture all the component level onClick events.
 


 

Comments

  1. Could you please elaborate more on this? If you have any other references please do forward. I am currently integrating this and need this urgently.

    ReplyDelete

Post a Comment

Popular posts from this blog

AEM 6.3 - How to extend Granite UI

Here in this article, I am going to explain how to extent Granite UI that is basically used to create AEM 6.x consoles. There can be various use cases where in you may need that. In our case, author wants to take all the page creation requests through AEM instead of email communication. Authors are basically looking for a form in AEM authoring console so that requestor can login and submit page creation/Asset upload request. Overall requirement is - Need a link in Navigation so that author can click on it and go to a Intake form. Author must be able to fill and save the intake requests. Author must be able to see the history of submitted intake requests Able to see the details of submitted intake requests. Solution - 1. Create a following structure - /apps/cq/core/content/nav/form and add the details given in below screenshot - You basically need to add - href, title and icon. Href is the path of page where user will land on clicking it.  Af...

CQ Page Properties from Javascript

To get CQ page properties inside javascript you can use core CQ JS API. It can be convenient if you need to get this information inside your custom JS widgets.              var pageData = CQ.HTTP.get(CQ.HTTP.externalize(CQ.utils.WCM.getPagePath() + "/jcr:content.json")); After that you can retrieve any property you need (assuming it's present in JCR):              var resourceType = pageData ? CQ.Util.formatData(CQ.HTTP.eval(pageData))['sling:resourceType'] : null; Please do not overuse it because it invokes additional ajax call to server. It's OK to use it in edit mode on author instance. Copied from -  http://adobecms.blogspot.com/2014/04/cq-page-properties-in-javascript.html

AEM 6.3 - Check if page is published or not

If you want to know if the page is published or not you can use the below utility method to know if the page is published or not. Steps - Take Resource Object. Adapt it to Page Adapt page to ReplicationStatus, you will get the status Here is the code - public static Boolean isPublished(Resource resource) { Boolean activated; ReplicationStatus status = null; activated = false; if (resource != null) { try { Page page = resource.adaptTo( Page.class ); status = page.adaptTo( ReplicationStatus.class ); } catch (Exception e) { LOG.debug(e.getMessage (), e); } if (status != null) { activated = status.isActivated(); } } return activated; }