Developer engagement Stay organized with collections Save and categorize content based on your preferences.
This pageapplies toApigee andApigee hybrid.
View Apigee Edge documentation.![]()
What does this dashboard tell me?
The Developer Engagement dashboard tells you which of your registered app developers are generating the most API traffic. For each of your developers, you can find out who is generating the most API traffic and the most errors. For example, if a particular developer's app is generating a lot of errors relative to other developers, you can proactively address the problem with that developer.
The Developer Engagement dashboard
Required roles: To access theDeveloper Engagement dashboard, you must have the following IAM predefined roles:roles/apigee.analyticsViewerroles/apigee.analyticsEditorroles/apigee.addonsconfig.get
For more information, seeHow to specify a predefined role.
Access the Developer engagement dashboard:
In the Google Cloud console, go to theAnalytics> Developer analysis> Developer engagement page.
Note: The Cloud console dashboard only shows active data. For example, if an API proxy is deployed, but not getting any traffic, it won't show up in the dashboard.The Cloud console dashboard has these sections:
The dashboard is shown:

Overview tab
TheOverview tab shows the following information:
| Metric | Description |
|---|---|
| Top 10 developer apps by traffic | A ranking of the number of API proxy calls associated with individual developer apps. |
| Top 10 developers by traffic | A ranking of developers based on the number of API proxy calls associated with them. |
TheEngagement details table in the Overview tab shows the following information:
| Detail | Description |
|---|---|
| Developer app | The name of the app. |
| Proxy | The name of the API proxy associated with the app. |
| Developer | The email address of the developer who registered the app or the AppGroup Id in the case of an AppGroup. |
| API product | The product name associated with the app. |
| Traffic | The amount of traffic generated by the app for the selected time period. |
| Errors | The total number of errors generated by the app for the selected time period. |
| Error Rate | The error percentage calculated by dividing total errors by total traffic for the selected time period. |
Sum of traffic tab
TheSum of traffic tab shows API proxy traffic details for the filtered items. Itincludes:
| Metric | Description |
|---|---|
| Traffic by proxy | API calls recorded for the selected API proxies. |
| Traffic by developer | API calls recorded for API proxies associated with selected developers. |
| Traffic by products | API calls recorded for API proxies associated with selected API products. |
| Traffic by app | API calls recorded for API proxies associated with selected developer apps. |
Sum of error count
TheSum of error count tab shows API proxy traffic error counts for the filtered items. Itincludes:
| Metric | Description |
|---|---|
| Errors by proxy | API errors recorded for the selected API proxies. |
| Errors by developers | API errors recorded for API proxies associated with selected developers. |
| Errors by products | API errors recorded for API proxies associated with selected API products. |
| Errors by app | API errors recorded for API proxies associated with selected developer apps. |
Average of total response time
TheAverage of total response time tab shows response time or latency information for the filtered items. It includes:
| Metric | Description |
|---|---|
| Average of total response time by proxy | Average of total response time for the selected API proxies. |
| Average of total response time by developer | Average of total response time recorded for API proxies associated with selected developers. |
| Average of total response time by products | Average of total response time recorded for API proxies associated with selected API products. |
| Average of total response time by app | Average of total response time recorded for API proxies associated with selected developer apps. |
Using the dashboard
The dashboard has a set of dropdown menus that you can use to filter the information shown in the dashboard. The filter dropdown menus are dynamic. For example, if you select a developer from the Developers dropdown, then any proxies, apps, and API products associated with that developer are automatically selected in the other dropdown menus, charts, and tables . For more information, seeAbout filter properties in the Looker Studio documentation.
Use the date selector to pick a start and end date to measure. The date selector only lets you select dates in day increments. You can't select a time range increment that is smaller than a day.
Note: Seeing a dimension entity named(not set)? For more information, see What does an analytics entity named (not set) mean?Make a copy in Looker Studio
You can edit, save, and share a copy of the dashboard inLooker Studio. To get started:
- ClickMake a copy in Looker Studio.
- From the dropdown menu, select the report you wish to copy.
- In Looker Studio, clickSave and share.
- ClickAcknowledge and save.
You can now edit the copy saved in your user account. For details on usingLooker Studio to edit and create reports, see theLooker Studio documentation.
Note: Any changes you make in Looker Studio are not reflected back in the Apigee dashboard.Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.