Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

Stop TwitterProfileData, FbProfileData calls

Avatar

Former Community Member

By adding the clientcontext as required by analytics integration, I get 404's for twitterprofiledata, fbprofiledata, fbinterestsdata in the path /etc/clientcontext/default/contextstores/ even though I am not doing any FB or Twitter integration?

<body>
<cq:include path="clientcontext" resourceType="cq/personalization/components/clientcontext"/>

Is there some other workaround to stop the clientcontext directory on my publish instance call fbprofiledata etc? 

1 Accepted Solution

Avatar

Correct answer by
Level 10

Here is the AEM Client Context documentation:

http://dev.day.com/docs/en/cq/current/developing/client_context_detail.html

If you feel there is missing information to do your job with AEM- - please log a bug here:

http://helpx.adobe.com/marketing-cloud/experience-manager.html

View solution in original post

2 Replies

Avatar

Correct answer by
Level 10

Here is the AEM Client Context documentation:

http://dev.day.com/docs/en/cq/current/developing/client_context_detail.html

If you feel there is missing information to do your job with AEM- - please log a bug here:

http://helpx.adobe.com/marketing-cloud/experience-manager.html