Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Adobe Experience Manager for Pega Marketing and Pega Customer Decision Hub

Updated on September 10, 2021

Adobe Experience Manager (AEM) is a content management solution which provides users with an interface to build, deliver, and maintain digital experiences. The Pega AEM Connector allows you to connect your AEM assets to Pega offers and treatments, so that you can apply advanced analytics to existing AEM assets. You can navigate the Adobe Experience Manager folder structure and browse Adobe Experience Manager assets from inside Pega Marketing or Pega Customer Decision Hub. The Pega AEM Connector uses the Query Builder API provided by Adobe. For more information about the API, see the Adobe API documentation.

Deploying Adobe Experience Manager

For information about installing and deploying Adobe Experience Manager, see the Adobe Experience Manager documentation.

Connecting Adobe Experience Manager and Pega Marketing or Pega Customer Decision Hub

  1. Download the Pega AEM Connector from Pega Exchange.
  2. In Dev Studio, click the down arrow by the name of your application, then clickDefinitionto open the Application rule form.
  3. On the Definition tab, in the Enabled components section, click Manage components.
  4. Click Install new, select the file that you downloaded from Pega Exchange, and click Open.
  5. Select the Enabled check box to enable this component for your application, and click OK.
  6. In the list of enabled components, verify that the Pega AEM Connector is selected, and save your changes to the rule form.
  7. In Dev Studio, click Records > SysAdmin > Repository.
  8. Click Create.
  9. Enter a description and a name for your repository.
  10. Click Create and open.
  11. In the Definition tab, click Select.
  12. Select Adobe Experience Manager as the repository type.
  13. Optional: By default, Pega Marketing can create and delete files and folders in Adobe Experience Manager. If you want to disable this functionality, select Read-Only.
  14. In the Repository configuration section, in the Publish host name field, enter the host name of your Adobe Experience Manager repository. Pega Marketing will use this host name to access Adobe Experience Manager.
  15. Optional: If you want to automatically publish content to Adobe Experience Manager, enter the Author host name of your Adobe Experience Maanger repository in the Author host name field, and select Auto Publish. The Author host name field is only available if you did not set the Adobe Experience Manager repository to Read Only in step 13.
  16. In the Root path field, enter the name of the folder where Adobe Experience Manager assets are stored. The Pega AEM connector will allow you to browse the assets in this folder from inside Pega Marketing.
    Note: The Root folder path must not start with the / character.
  17. In the Authentication section, in the Authentication profile field, enter the name of a new authentication profile and click the Open icon to configure the profile. The authentication profile stores the credentials that Pega Marketing needs to authenticate with the Adobe Experience Manager API.
  18. In the Type field, select Basic.
  19. Enter a name and description for your authentication profile.
  20. Click Create and open.
  21. Enter the user name, password, realm and host name required to authenticate with Adobe Experience Manager. For more information, refer to the Adobe API documentation.
  22. Select Preemptive authentication.
  23. Click Save.
  24. On the Definition tab of your repository, click Test connectivity. If there are any errors, ensure that the credentials in the authentication profile are correct, and that Pega Marketing can access the URLs you entered in the Publish host name and Author host name fields.
  25. Click Save.
  26. Click Records > SysAdmin > Dynamic System Settings.
  27. Edit the following Dynamic System Settings:
    • MarketingImageAssets/IsRepositoryStorageEnabled – Set the value to True
    • MarketingImageAssets/CustomRepositoryName – Enter the name of the repository you created
    • MarketingImageAssets/Folder – Enter a valid sub-folder of the Root folder. If you leave this field blank, the Root folder is used as the destination folder for your images.
  28. Flush the D_RepositorySettings data page to make sure the configuration changes are applied.
    1. Click Records > Data Model > Data Page.
    2. Open the D_RepositorySettings data page.
    3. On the Load Management tab, click Clear data page.
    4. Select Flush All.
    5. Click Submit.

Allowing Pega Marketing or Pega Customer Decision Hub to access images from Adobe Experience Manager

Images stored in AEM are treated as images from an unknown source by Pega Marketing. To allow your application to access an image from Adobe Experience Manager, add the Adobe Experience Manager host in the Content security policy.

  1. In Dev Studio, click the down arrow by the name of your application, then click Overview.
  2. Click Integration & security.
  3. In the Content security section, open the content security policy.
  4. Expand the Image-Source section
  5. In the Allowed Websites table, click Add a row.
  6. Enter the URL of your Adobe Experience Manager host.
  7. Save the content policy.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us