CQ Sitecatalyst Integration - Custom Implementation advantages/features | Community
Skip to main content
A
Anonymous
October 16, 2015
Solved

CQ Sitecatalyst Integration - Custom Implementation advantages/features

  • October 16, 2015
  • 2 replies
  • 1495 views

Hi,

Wanted to check if there are any features/advantages available when we do the Sitecatalyst custom implementation(OOTB) in the CQ Sites instead of doing the traditional Sitecatalyst implementation.

My Thoughts:

- If we are doing basic implementation, then the OOTB Sitecatlyst CQ integration would be helpful and this will save some time for both developer & as well as for analytics person.

- If we go for custom implementation, then it will take some extra time for analytics ppl to create the node for that sitecatalyst variables and map those variables in the CQ Framework. 

         - But, if we go for traditional sitecatalyst implementation in the CQ sites, we can use the sitecatalyst variables directly in the page level instead of mapping & creating the nodes and doing all other stuffs.

Any thoughts??

 

Thanks,

Muthalagu

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Scott_Brodersen

I'm not sure that I understand your distinction between "basic implementation" and "custom implementation". Using the Integrating with SiteCatalyst page [0] as a reference, you would always have to map CQ variables with SiteCatalyst properties (create the configuration > create and configure the framework).

At any rate, you can use a SC integration framework and still add javascript to a page as required. You can even inject custom javascript into the framework if you use the same code for multiple pages [1].

scott

 

[0] http://dev.day.com/docs/en/cq/current/administering/integrating_with_adobe_marketing_cloud/sitecatalyst.html 

[1] http://dev.day.com/docs/en/cq/current/administering/integrating_with_adobe_marketing_cloud/sitecatalyst.html#Using%20Custom%20javascript%20Code%20in%20a%20SiteCatalyst%20Framework

2 replies

Scott_Brodersen
Scott_BrodersenAccepted solution
Level 8
October 16, 2015

I'm not sure that I understand your distinction between "basic implementation" and "custom implementation". Using the Integrating with SiteCatalyst page [0] as a reference, you would always have to map CQ variables with SiteCatalyst properties (create the configuration > create and configure the framework).

At any rate, you can use a SC integration framework and still add javascript to a page as required. You can even inject custom javascript into the framework if you use the same code for multiple pages [1].

scott

 

[0] http://dev.day.com/docs/en/cq/current/administering/integrating_with_adobe_marketing_cloud/sitecatalyst.html 

[1] http://dev.day.com/docs/en/cq/current/administering/integrating_with_adobe_marketing_cloud/sitecatalyst.html#Using%20Custom%20javascript%20Code%20in%20a%20SiteCatalyst%20Framework

A
Anonymous
October 16, 2015

Thanks for your comments Scott.

But, my question is why should we need to spend extra time on creating/configuring the framework, creating nodes for each variables & mapping variables etc. Instead of that, we can use the sitecatalyst variable directly in the page level or using custom javascript to get the values.

-Muthalagu

Terms & ConditionsAccessibility statement

Loading footer...