Legacy Knowledge Base
Published Jul. 2, 2025

Disable 'track' requests from Audience Targeting

Written By

Cristina Rodriguez

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Sometimes there is a need to get rid of the following calls from Audience Targeting:
    • /o/analytics-processor/track
  • For example some of the browsers which attempt to send analytics events to Liferay may experience higher latency, and if not needed we can reduce the impact by ensuring that all browsers do not push analytics events to Liferay.
  • But it is not posible to do so through Audience Targeting's Control Panel Options.

Environment

  • Liferay DXP + Audience Targeting.

Resolution

  • In this case, the specific bundle that manages those requests should be blacklisted:
    com.liferay.content.targeting.analytics.processor
  • This bundle provides two components:
    • com.liferay.content.targeting.analytics.processor.internal.processor.AnalyticsProcessorImpl: an AnalyticsProcessor that updates the page to include a POST to /o/analytics-processor/track
    • com.liferay.content.targeting.analytics.processor.internal.servlet.AnalyticsProcessorServlet: a servlet that processes posts to /o/analytics-processor/track
  • Si by blacklisting the entire bundle no more track events will be sent and processed.

Additional Information

 

 

 

Did this article resolve your issue ?

Legacy Knowledge Base