---
title: "Get Google Play Event Diagnostics"
method: GET
path: "/v2/projects/{id}/applications/{application_id}/integrations/google-play/event-diagnostics"
tags: ["Google Play V2"]
---

# Get Google Play Event Diagnostics

`GET /v2/projects/{id}/applications/{application_id}/integrations/google-play/event-diagnostics`

Returns recent Google Play notification counts split by outcome — received, converted to revenue, failed conversion, and failed detail lookups (grouped by cause). Answers whether a configuration that validates is actually receiving traffic. Requires applications:read scope.

## Path parameters

- `id` string, required — Project ID
- `application_id` string, required — Application ID

## Response `200`

Success

- object
  - `object` 'google_play_event_diagnostics', required — Object type, always `google_play_event_diagnostics`
  - `webhook_received` object, required — Notifications received from Google Play
    - `count` number, required — Number of events in the window
    - `latest` string, nullable, required — ISO 8601 timestamp of the most recent event, or `null` when there were none
  - `revenue_ok` object, required — Notifications successfully converted into revenue events
    - `count` number, required — Number of events in the window
    - `latest` string, nullable, required — ISO 8601 timestamp of the most recent event, or `null` when there were none
  - `revenue_error` object, required — Notifications that failed revenue conversion
    - `count` number, required — Number of events in the window
    - `latest` string, nullable, required — ISO 8601 timestamp of the most recent event, or `null` when there were none
  - `details_error` object, required — Notifications that failed while fetching purchase details from Google
    - `count` number, required — Number of events in the window
    - `latest` string, nullable, required — ISO 8601 timestamp of the most recent event, or `null` when there were none
  - `details_errors` object[], required — Detail-fetch failures grouped by cause, most frequent first
    - `count` number, required — Occurrences of this error
    - `latest` string, nullable, required — ISO 8601 timestamp of the most recent occurrence
    - `error_summary` string, required — Grouped error description
  - `total` number, required — Total events across all buckets
  - `has_any_events` boolean, required — False when nothing has ever arrived — the signal that delivery is not wired up

## Other responses

- `400` — The request did not match the expected schema
- `401` — No API key was provided in the request
- `403` — The API key does not have permission to perform this action
- `404` — The requested resource was not found
- `429` — Too many requests have been made in a short period
- `500` — An unexpected error occurred on the server

---

[API](https://skmtc.dev/superwall/apis/superwall-api-v2.md) · [All operations](https://skmtc.dev/superwall/apis/superwall-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/superwall/superwall-api-v2/revisions/44900ad77d2c/schema)