This section applies if you are using Oracle ATG Web Commerce Search as part of your Commerce site, and want to report on the integration between these products. Search logs information when searches are performed, and when customers click links in search results to view or purchase items. See the ATG Search Administration Guide for information on the former; this section discusses the latter.

To associate search terms with items that are viewed or purchased, your sites must record “click-through” events. These occur when a customer clicks on a product or SKU returned by a search, to view it or purchase it. The recording of these events works like this:

  • For each search result, the /atg/search/droplet/GetClickThroughId servlet bean generates a click-through ID, which you append to the URL for that result using a query parameter. The servlet bean also adds the result document to a cache.

  • When a customer clicks a link to view a search result, the /atg/search/servlet/pipeline/SearchClickThroughServlet examines the request URL, finds the click-through ID, and uses it to look up the document in the cache. If it finds the document, the servlet fires an JMS event containing the search request and response objects and the selected document. This event is logged to be used for reporting.

The QueryFileLogger component logs the search information; see Data Logging for Reports in the ATG Search Administration Guide for information on this component.

For more information about configuring your Commerce site to log data for Commerce Search reports, see the ATG Search Administration Guide.