Connect to an AEM Assets Content Hub repository

If you have assets in Adobe Experience Manager (AEM), you can follow these steps to make them accessible in GenStudio for Performance Marketing.

recommendation-more-help

Prerequisites:

The following steps require administrative access to Admin Console and AEM Assets as a Cloud Service.

Step 1: Enable AEM Assets Content Hub

Follow the Deploy Content Hub self-service process to enable Content Hub for your existing AEM Assets in Cloud Manager. See Deploy Content Hub in the AEM as a Cloud Service documentation.

After you enable AEM Assets Content Hub, you have a new instance with the contenthub suffix within AEM Assets as a Cloud Service on Admin Console.

IMPORTANT
Administrators should verify that the AEM Assets Content Hub repository is within the same organization as GenStudio for Performance Marketing.

Step 2: Onboard GenStudio users

In the Admin Console, add a GenStudio for Performance Marketing user or user group to the AEM Assets Content Hub product profile. If a content reviewer does not have access to the same organization as the AEM Assets Content Hub repository, they may experience difficulties in reviewing and approving content.

Step 3: Approve assets

Approve assets for use in AEM Assets Content Hub, which makes them available in GenStudio for Performance Marketing.

See Approve assets in Experience Manager in the AEM as a Cloud Service documentation.

Step 4: Configure asset visibility

In AEM Assets Content Hub configuration options, review each set of configuration options for filters, asset details, search, and branding.

See Configure Content Hub user interface in the AEM as a Cloud Service documentation.

Step 5: Verify the connection

In GenStudio for Performance Marketing Content, the Location list is available above the gallery on the right side. The list is not available if you do not have access or your organization has not deployed and connected an AEM Assets Content Hub repository.

See Assets location to read about the Location list and changing repositories.

28475a92-7296-4969-af5f-82e50c3f1519