Gigya Job Openings

accounts.incrementCounters REST

Skip to end of metadata
Go to start of metadata

This method is part of Gigya's Signals for tracking behavioral data. When creating a custom counter, you first register it using accounts.registerCounters, then increment it using the current method. In addition to incrementing counters, you can optionally use this method to track the value for the user action that is counted (e.g., a purchase). 

Request URL

Where <Data_Center> is:
  • us1.gigya.com - For the US data center.
  • eu1.gigya.com - For the European data center.
  • au1.gigya.com - For the Australian data center.
  • ru1.gigya.com - For the Russian data center.
  • cn1.gigya-api.cn - For the Chinese data center.

If you are not sure of your site's data center, see Finding Your Data Center.

Parameters

RequiredNameTypeDescription
UIDstringThe unique ID of the user for which to increment the count. Use either this parameter or regToken.
* If you call this method through an external OAuth2 SDK, then the UID may be passed implicitly within the access_token.
regTokenstringThe regToken returned from accounts.initRegistrationaccounts.register or accounts.login API calls when the registration process has not been finalized. Please note that the regToken you receive from Gigya is valid for only one hour.
 * You are required to pass only one of the parameters either UID or regToken.
countersarray of objectsAn array of counter objects, each object has the following fields:
  • class (required) -  specifies the type of action that is counted, e.g. "shares".
  • path (required) - specifies a path that provides an extra classification for the action, e.g. "/news/sport". If you don't want to provide a specific path, use "/". By default paths can be no deeper than two levels, where "/news/sport" is two levels and "/news/sport/football" is three levels. Access to deeper level counting is available on request. Paths other than "/" must be registered before they can be incremented. For more information, see accounts.registerCounters.
  • value (optional) - specifies a value for the count. If, for example, the action that is counted is purchases, this value can be the accumulative amount. The default value is 0.
  • count (optional) - specifies the count for this class and path. The counter will be incremented according to this value. The default value is 1.

For example:
 { counters: [
   {
     "class" : "_purchases",
     "path" : "/",
     "value" :  200
   },
  {
    "class" : "_adClicks", 
    "path" : "/sport"
  } 

] }

             
format string Determines the format of the response. The options are:
  • json (default)
  • jsonp - If the format is jsonp then you are required to define a callback method (see parameter below).
callback string This parameter is required only when the format parameter is set to jsonp (see above). In such cases this parameter should define the name of the callback method to be called in the response, along with the jsonp response data.
httpStatusCodes Boolean The default value of this parameter is false, which means that the HTTP status code in Gigya's response is always 200 (OK), even if an error occurs. The error code and message is given within the response data (see below). If this parameter is set to true, the HTTP status code in Gigya's response would reflect an error, if one occurs.

Authorization Parameters

Each REST API request must contain identification and authorization parameters.

Some REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as client-side calls and all client-side rate limits will apply. In order to not reach client-side rate limits that may impact your implementation when using server-to-server REST calls, it is Recommended Best Practice to always sign the request or use a secret. A non-exhaustive list of REST APIs that this may apply to are as follows:

  • accounts.login
  • socialize.login
  • accounts.notifyLogin
  • socialize.notifyLogin
  • accounts.finalizeRegistration
  • accounts.linkAccounts

Please refer to the Authorization Parameters section for details. 

Sample Requests

Example of a call to accounts.incrementCounters

The following code increments the counter "my_counter" with the path "/sport".

 

Response Data

FieldTypeDescription
 
errorCode integer The result code of the operation. Code '0' indicates success, any other number indicates failure. For a complete list of error codes, see the Error Codes table.
errorMessage string A short textual description of an error, associated with the errorCode, for logging purposes. This field will appear in the response only in case of an error.
errorDetails string This field will appear in the response only in case of an error and will contain the exception info, if available.
fullEventName string The full name of the event that triggered the response. This is an internally used parameter that is not always returned and should not be relied upon by your implementation.
callId string Unique identifier of the transaction, for debugging purposes.
time string The time of the response represented in ISO 8601 format, i.e., yyyy-mm-dd-Thh:MM:ss.SSSZ or
statusCode integer The HTTP response code of the operation. Code '200' indicates success.
This property is deprecated and only returned for backward compatibility.
statusReason string A brief explanation of the status code.
This property is deprecated and only returned for backward compatibility.

 

 

Response Example

{
        "statusCode": 200,
        "errorCode": 0,
        "statusReason": "OK",
        "callId": "ddb3f8e144c84cb5b1bc5f010bddab2b",
        "time": "2015-03-22T11:42:25.943Z"
}