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).
Note: This method is also supported in our REST API. If you wish to execute this method from your server, please refer toREST API > accounts.incrementCounters.
The following table lists the available parameters:
|||counters||array of objects||An array of counter objects, each object has the following fields:|
A reference to a callback function. Gigya calls the specified function along with the results of the API method when the API method completes.
The callback function should be defined with the following signature: functionName(Response).
The "Response Object Data Members" table below provides specification of the data that is passed to the callback function.
A string of maximum 100 characters length. The CID sets categories for transactions that can be used later for filtering reports generated by Gigya in the "Context ID" combo box. The CID allows you to associate the report information with your own internal data. For example, to identify a specific widget or page on your site/application. You should not define more than 100 different context IDs.
A developer-created object that is passed back unchanged to the application as one of the fields in the response object.
Response Object Data Members