Search Results POST to /bin/statistics/tracker/result | Community
Skip to main content
AEM_Dan
AEM_Dan
Level 3
June 29, 2023
Solved

Search Results POST to /bin/statistics/tracker/result

  • June 29, 2023
  • 2 replies
  • 1114 views

Our search page is based off /libs/foundation/components/search/search.jsp. When a search is executed, there is a POST to /bin/statistics/tracker/query.  When a search result is clicked on, there is another POST to /bin/statistics/tracker/result.  Both result in a HTTP 403.

 

It appears there was a setting for this in prior AEM versions. http://www.aemstuff.com/osgi/aem62.html, search for TrackerServlet.  But that OSGi config no longer exists in 6.4 or 6.5.

 

Does anyone know what that was doing?  Is there a replacement for that in 6.5?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Tanika02

Hello @aem_dan -

 

  • The TrackerServlet mentioned in the AEM 6.2 documentation you referred to is responsible for handling the tracking of search queries and results. It captures and processes the search analytics data, such as query terms, clicked results, and other related information.
  • In AEM 6.4 and 6.5, the tracking functionality has been refactored and integrated into the Adobe Experience Platform (AEP) services. The TrackerServlet OSGi configuration no longer exists in these versions because the tracking and analytics capabilities are now managed through AEP services, such as Adobe Analytics.
  • To configure and enable search tracking in AEM 6.4 and 6.5, you will need to integrate AEM with Adobe Analytics or other relevant Adobe Experience Cloud services. This involves setting up the necessary configurations and integrating the required libraries and tags provided by Adobe Analytics or the Experience Cloud.

2 replies

Tanika02
Tanika02Accepted solution
Level 7
June 29, 2023

Hello @aem_dan -

 

  • The TrackerServlet mentioned in the AEM 6.2 documentation you referred to is responsible for handling the tracking of search queries and results. It captures and processes the search analytics data, such as query terms, clicked results, and other related information.
  • In AEM 6.4 and 6.5, the tracking functionality has been refactored and integrated into the Adobe Experience Platform (AEP) services. The TrackerServlet OSGi configuration no longer exists in these versions because the tracking and analytics capabilities are now managed through AEP services, such as Adobe Analytics.
  • To configure and enable search tracking in AEM 6.4 and 6.5, you will need to integrate AEM with Adobe Analytics or other relevant Adobe Experience Cloud services. This involves setting up the necessary configurations and integrating the required libraries and tags provided by Adobe Analytics or the Experience Cloud.
    AEM_Dan
    AEM_DanAuthor
    Level 3
    July 13, 2023

    Thanks for the detailed explanation.  That was helpful.  We do use Adobe Analytics so we are covered.

    Sudheer_Sundalam
    Community Advisor
    Sudheer_SundalamCommunity Advisor
    Community Advisor
    June 30, 2023

    @aem_dan 

     

    Often times POST requests are blocked at dispatcher and POST request paths must be explicitly allowed in dispatcher filter.any file.

     

    Please check if you can make the POST call directly to the Author/Publish URL using a tool like POSTMan. If the POST call via PostMan tool doesn't end in 403, then it must be the dispatcher that is rejecting this POST request.

    If you are testing this in non-prod environment, enable dispatcher log at debug level to see the information POST call.

      AEM_Dan
      AEM_DanAuthor
      Level 3
      July 13, 2023

      You are correct.  The POST was initially blocked but even when I allowed it, it was still returning 404 from the publisher.

      Terms & ConditionsAccessibility statement

      Loading footer...