When exporting AEM Content Fragments as JSON Offers to Adobe Target, you may encounter an error preventing the successful integration. This post details the issue, its root cause, and the steps to resolve it.
Issue
The AEM Content Fragment Export to Adobe Target failed with the following exception:
06.03.2025 12:59:31.223 *DEBUG* [[0:0:0:0:0:0:0:1] [1741287571223] GET /content/dam/content-fragments/test/test-cf/.permissions.json HTTP/1.1]
com.test.core.filters.LoggingFilter request for /content/dam/content-fragments/test/test-cf/, with selector permissions
06.03.2025 12:59:40.706 *DEBUG* [[0:0:0:0:0:0:0:1] [1741287580703] POST /content/dam/content-fragments/test/test-cf.cfm.targetexport HTTP/1.1]
com.test.core.filters.LoggingFilter request for /content/dam/content-fragments/test/test-cf, with selector cfm
06.03.2025 12:59:40.710 *ERROR* [[0:0:0:0:0:0:0:1] [1741287580703] POST /content/dam/content-fragments/test/test-cf.cfm.targetexport HTTP/1.1]
com.adobe.cq.dam.cfm.graphql.extensions.querygen.impl.service.QueryGeneratorServiceImpl
Cannot find Sites GraphQL endpoint resource, cannot generate GraphQL query
Root Cause
This issue occurs because no GraphQL endpoint is defined for Adobe Target to fetch Content Fragment details. The export process requires a valid GraphQL endpoint to retrieve structured content from AEM and send it to Adobe Target.
Solution
To resolve this issue, follow these steps to define a global GraphQL endpoint in AEM:
Log into AEM and navigate to Tools → General → GraphQL.
Create a new GraphQL endpoint and associate it with /conf/global.
Save and publish the endpoint to make it accessible.