Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

CQ Sitecatalyst Integration - Custom Implementation advantages/features

Avatar

Former Community Member

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

1 Accepted Solution

Avatar

Correct answer by
Level 8

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/sitecatal... 

[1] http://dev.day.com/docs/en/cq/current/administering/integrating_with_adobe_marketing_cloud/sitecatal...

View solution in original post

2 Replies

Avatar

Correct answer by
Level 8

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/sitecatal... 

[1] http://dev.day.com/docs/en/cq/current/administering/integrating_with_adobe_marketing_cloud/sitecatal...

Avatar

Former Community Member

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