var KMConfig = {
  /**
   * There are three possibe values for AUTOCOMMIT: true, false, and "on_page_load". 
   * If AUTOCOMMIT is true then all calls to record are logged immediately.
   * If AUTOCOMMIT is false then all calls to record are logged after you call log_all_actions.
   * If AUTOCOMMIT is "on_page_load" then all actions before page load are queued up and sent
   *    after the page has loaded. AUTOCOMMIT is then set to true on page load and all actions
   *    recorded after page load are sent immediately.
   * In all cases each action that is logged is still sent as an individual HTTP request
   *
   * The reason this is important is because we want to wait to log actions until all of the various
   * plugins and user customization have had a chance to call assign. Assigns are applied when the action
   * is logged, not when it is recorded. So this way if you record a page_view action and then a plugin
   * that is loaded after assigns some property, the page_view action will get the assigned property when it
   * is logged.
   *
   * Most assigns will happen prior to page load, thus it is safest to just leave AUTOCOMMIT to "on_page_load".
   * However, if you know you will be doing an assign after the page loads then you'll want to change this value.
   * For example, if you load in some assign via AJAX (or some other mechanism that happens after page load)
   * then you would want to set AUTOCOMMIT to false and then make sure to call log_all_actions after you have set your
   * assign. If you don't call log_all_actions (like if your AJAX call fails or timesout) though then nothing will be recorded.
   */
  AUTOCOMMIT: "on_page_load",
  
  /**
   * The URL that KISSmetrics will log to
   *
   */
  LOG_URL: "/wp-content/plugins/kissmetrics/log.php",
  
  /**
   * The prefix that KISSmetrics will use for all of it's cookie values.
   * If you change this you MUST change the corresponding value in the server-side
   * conf file.
   */
  COOKIE_PREFIX: "__km_"
}