ATG Recommendations API Flavors

The Need for Flavors

The ATG Recommendations API is available in a variety of flavors enabling retailers to balance their recommendation needs with their existing infrastructure and bandwidth requirements.

Picking a Flavor

Only one flavor of the ATG Recommendations API may be included on an HTML page. The available flavors of the ATG Recommendations API:

atgsvcs.js
This is our most commonly used flavor. It includes our full suite of functionality and renderering capabilities. This file is served using GZip compression to compatible browsers.
Example:

<script type="text/javascript" charset="utf-8" src="//static.atgsvcs.com/js/atgsvcs.js"></script>

Test Mode
All API flavors are also available in an unpacked test mode. The test mode files contain a substantial amount of debugging output. Also, because it is uncompressed these files take longer to load. These test mode flavors are used by including the string “-test” immediately after the version number in the .js filename.
Example:

<script type="text/javascript" charset="utf-8" src="//static.atgsvcs.com/js/atgsvcs-test.js"></script>

Enabling Debug Output Capture
When a test mode flavor is in use the API will look for an element with the id “cs-debug”. Output will be inserted into this div, creating a log of executed functions.
Example:

<!-- DIV strictly for logging activity to in test mode. Not required, used, or recommended for production. -->
<div id="cs-debug" style="border: 1px dashed #c00; background-color: #fcc; margin-bottom: 25px; padding: 5px; color: #900; font: 11px Bitstream Vera Sans Mono, monospace">
  <div style="font-weight: bold">Debug Output:</div>
</div>