Google Commerce Search Deployment Guide - Manual (Page 24)

These numbers do take into account SAYT and Autocompletion queries, which are not counted
towards yearly GCS quota.
API Console Traffic Reports
Another place to find some usage statistics is in the Traffic Reports section of the API console:
https://code.google.com/apis/console/
To view the Traffic Reports, click the Search API for Shopping link (should show a status
of “ON”).
This graph simply shows the total number of API requests for the given time period. As
mentioned in
Chapter 1 , it is a good idea to have separate keys for your server-side component,
and any client-side code (SAYT/Autocomplete). The Traffic Reports have separate reports for
each key, so you can get a better view of where API requests are being used.
Google Analytics integration
If you’re already using Google Analytics on your site, getting useful data from GCS queries is
easy. If you’re not currently using GA, see the “Getting Started Guide” for Analytics at
http://www.google.com/support/analytics/ .
There is currently no direct integration between GCS and GA. You can implement Google
Analytics by:
1. Installing the Google Analytics Tracking code on your pages.
2. Configuring Site Search settings in the Analytics control panel.
While you could install the tracking code only on search results pages, it is recommended to
install the tracking code on all pages of your site. The Recommendations feature in GCS relies
on Google Analytics data for providing recommendations, and to measure the true impact of
GCS, it is important to track conversion results.
Configuring Site Search
GCS usage on your site is tracked in the Site Search section of Google Analytics. Once you
have the tracking code installed on your site, follow the instructions for configuring Site Search
tracking at
https://www.google.com/support/googleanalytics/bin/topic.py?topic=12626 .
The most important thing to capture is the Query Parameter. This is what is passed to the q
parameter in the Shopping API request, although your own form and server-side code could
have it named anything (keyword, substring, and so on).
The Category parameter can be used to log refinements. Typically this would be for a category
refinement, but it could be used for any attribute. The results show up in the Site Search >
Categories report, giving a list of the top category refinements.
With just this data you’ll be able to get valuable reports, such as:
● Top query terms
24