Skip to main content


Troubleshooting Paid Media Manager

Suggest edit Updated on January 19, 2022

Use the following troubleshooting tips to help solve issues related to Paid Media Manager configuration.

Issue: Paid media synchronization and audience count reporting is slow even after enabling elastic search

To improve the performance of the audience count reporting, you should enable elastic search on the paid media master database table. For more information, see "Enabling elastic search for Paid Media Manager" in the Pega Customer Decision Hub Implementation Guide on the Pega Customer Decision Hub product page.

If the performance of the report is slow even though you previously enabled elastic search in your application, enable the dedicated data-data-paidmediamaster search index is available.

  1. In Dev Studio, click Records SysAdminCustom Search Properties.
  2. Open the Data-PaidMediaMaster data instance.
  3. In the Properties section, select the Use dedicated index check box.
  4. Save the Data-PaidMediaMaster data instance.Note: Saving the data instance automatically creates the dedicated index.
  5. Run the Data-PaidMedia-.CheckAndBuildReIndex activity to rebuild the data-data-paidmediamaster search index.

Issue: Paid media synchronization job takes more time when the elastic search index is enabled

After enabling the elastic search index, the master table grows, and the paid synchronization job takes longer. To solve this issue, you can disable the dedicated elastic search index.

  1. In Dev Studio, click ConfigureSystemSettingsSearch.
  2. In the Search indexing section, click Dedicated.
  3. Delete the index with the name data-data-paidmediamaster.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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