Events

The events API suite provides comprehensive user behavior analytics and event tracking capabilities for your application. These endpoints enable measurement of user engagement, feature adoption, and behavioral patterns through flexible multi-dimensional analysis. Key capabilities include tracking event frequencies and unique device reach, analyzing user interactions across different segments like platforms and geographic regions, and measuring actual user engagement through unique device counting rather than raw event volumes. The APIs support customizable grouping configurations, timezone-aware data aggregation, and hierarchical data organization for complex analytical queries.

Download Events OpenAPI Document

End Points

GET

/event/devicecount

GET

/event/multigroup

Get event-based active device Count

The get events and their active devices count API provides unique device counts for events within a specified time period and timezone context. This endpoint measures user engagement by tracking how many distinct devices triggered specific events, offering insights into actual user reach rather than simple event frequency. The API requires date range, environment mode, and timezone parameters, with optional filtering by platform and application bundle. It returns event data with active device counts, where response keys follow the format "event_name(group_name)" and values represent the number of unique devices that generated each event during the specified period. This API is particularly valuable for understanding true user engagement, measuring feature adoption rates, and analyzing the actual reach of specific user actions.
OAuth Scope : JProxy.jmobileapi.ALL

Query Parameters

startdate

string

(Required)

Beginning of date range for data retrieval, required format - dd-MM-yyyy

enddate

string

(Required)

End of date range for data retrieval, required format - dd-MM-yyy

mode

string

(Required)

Environment filter. 0 for development, 1 for production. Default - 1 (production).

platform

string

Platform to filter Events (iOS, Android, Windows, tvOS, watchOS, macOS). Default - all platforms.

timezone

string

(Required)

Timezone for events data aggregation.(e.g., "America/New_York", "Asia/Tokyo")

bundle

string

Application id filter. Need to be used in combination with platform param(e.g., "com.example.demo")

limit

string

Number of results per page. Default and maximum: 500. Use smaller values to limit response size.

offset

string

Starting position for result pagination (default - 0). Increment by limit value for next page (e.g., 501, 1001).

curl --request GET \
  --url 'https://apptics.zoho.com/cx/api/v1/event/devicecount?startdate=02-08-2025&enddate=24-08-2025&mode=0&timezone=Asia%2FKolkata' \
  --header 'Authorization: Zoho-oauthtoken 1000.41d9xxxxxxxxxxxxxxxxxxxxxxxxc2d1.8fccxxxxxxxxxxxxxxxxxxxxxxxx125f' \
  --header 'projectid: 12345689' \
  --header 'zsoid: 10234695'

{
    "result": {
        "event_name(group_name)": 121,
        "module_click(module_group)": 100
    },
    "status": "success"
}

Get events count by group

The get events Count by group API provides flexible event analytics with customizable grouping and aggregation capabilities. This endpoint allows you to analyze event data across multiple dimensions simultaneously, creating hierarchical breakdowns of event counts based on specified grouping criteria. The API requires a date range and grouping configuration, with optional filtering by platform, group name, and event name. The unique grouping system enables multi-dimensional analysis by combining up to three grouping entities such as device type, platform, bundle, date, app version, country, and event type. The response structure dynamically adapts to match your grouping configuration, creating nested JSON hierarchies that reflect the specified group order. For example, grouping by "platform,country,devicetype" returns data organized first by platform, then by country within each platform, and finally by device type within each country. This flexible structure supports complex analytical queries and enables detailed segmentation analysis.
OAuth Scope : JProxy.jmobileapi.ALL

Query Parameters

startdate

string

(Required)

Beginning of date range for data retrieval, required format - dd-MM-yyyy

enddate

string

(Required)

End of date range for data retrieval, required format - dd-MM-yyy

group

string

(Required)

Comma-separated list of grouping entities (devicetype, platform, bundle, date, appversion, country, event). Maximum 3 groups. Response structure follows the specified group order in nested JSON format.

platform

string

Platform to filter Events (iOS, Android, Windows, tvOS, watchOS, macOS). Default - all platforms.

groupname

string

Group Name of an Event to Filter. Need to be used in combination with eventname param.

eventname

string

A specific Event to filter. Need to be used in combination with groupname param.

limit

string

Number of results per page. Default and maximum: 500. Use smaller values to limit response size.

offset

string

Starting position for result pagination (default - 0). Increment by limit value for next page (e.g., 501, 1001).

curl --request GET \
  --url 'https://apptics.zoho.com/cx/api/v1/event/multigroup?startdate=02-08-2025&enddate=24-08-2025&group=platform%2Cdevicetype' \
  --header 'Authorization: Zoho-oauthtoken 1000.41d9xxxxxxxxxxxxxxxxxxxxxxxxc2d1.8fccxxxxxxxxxxxxxxxxxxxxxxxx125f' \
  --header 'projectid: 12345689' \
  --header 'zsoid: 10234695'

{
    "result": {
        "iOS": {
            "iPhone": 155248,
            "iPad": 3496
        },
        "Android": {
            "Phone": 40011,
            "Tablet": 1110,
            "Foldables": 1186
        }
    },
    "status": "success"
}