Skip to main content
Enabling Google Real-Time Developer Notifications speeds up events delivery time for integrations and webhooks and makes data in Qonversion analytics more real-time. RTDN is also a hard requirement for Refund Keeper on Google Play, not just a latency improvement: chargeback disputes reach Qonversion only through these notifications, so Refund Keeper cannot be enabled for Google Play until RTDN has delivered at least one message.

Google Developer Notifications Setup

If you haven’t completed the Android Store setup yet, do that first — it enables the Pub/Sub API and configures the service account credentials, both prerequisites for the steps below.
  1. Open your project’s Project Settings → Stores → Google Play Console → Real-time notifications (RTDN). If no Pub/Sub topic is shown, open Google Play store setup for the same project and click Connect to Google. Return to Real-time notifications (RTDN) and copy the topic.
  2. Open the Google Play Console for your application, then navigate to Monetization setup.
  3. In the Real-time developer notifications section:
  • check the Enable real-time notifications toggle,
  • insert your topic ID,
  • choose the correct Notification content for your app (with in-app products if you use them),
  • click on Save changes,
  • click on the Send Test Notification button.

Troubleshooting

Could not connect Qonversion to Google

  1. Confirm that the service account whose JSON key is saved in Qonversion has Pub/Sub Admin in the Google Cloud project containing the RTDN topic. The role belongs to the service account, not its JSON key. See Create a service account.
  2. Confirm that Cloud Pub/Sub API is enabled in the same project.
  3. Run Connect to Google again, at https://dash.qonversion.io/no-codes/stores/android, so Qonversion can create the topic.
  4. Once the topic appears under Real-time notifications (RTDN), make sure the topic in Google Play Console matches it, then use Send Test Notification in Google Play Console to check delivery. For JSON key replacement, follow the replacement steps before deleting the old key.

Apple Server-to-Server Notifications (S2S) Migrating In-App Subscriptions