Set up EMM notifications

Google Play generates notifications, referred to as EMM notifications, in response to various events that affect an enterprise. For example, when an app is approved, the system sends a ProductApprovalEvent notification.

EMM notifications are associated with a specific enterprise service account (ESA). As an EMM, you can set up your console to display alerts or messages to enterprise IT administrators based on the notifications that you receive.

EMM notifications are sent using Google Cloud Pub/Sub. For detailed information on how to set up a Pub/Sub notifications, see the Subscriber Overview and Pull Subscriber Guide.

To confirm that you have successfully set up your system to receive EMM notifications from Google Play and to retrieve the name of the Cloud Pub/Sub topic that you need to connect your subscription to, call Enterprises.sendTestPushNotification.

Sending a test notification validates your EMM integration with the Google Cloud Pub/Sub service for the enterprise. If EMM notifications are properly configured, the API returns the following:

    {
        topic_name: "/projects/project-name/topics/play-work-012345",
        message_id: "128976912439"
    }

Pull notifications

Google Cloud Pub/Sub supports two different notification mechanisms: pull and push. However, only pull notifications are recommended. The pull approach doesn't require any external server setup, and works with both programmatically and manually created ESAs. Another advantage of pull notifications is that they require little to no additional configuration or maintenance by your customers. use Enterprises.pullNotificationSet and Enterprises.acknowledgeNotificationSet to receive and acknowledge EMM notifications over long-running outgoing connections.

When calling Enterprises.pullNotificationSet, we recommend leaving the requestMode to its default value (waitForNotifications). This causes the request to wait until one or more notifications are present before returning a response. If no notifications are present after some time, the request returns an empty notification list, after which you can try the request again.

After you receive notifications, call Enterprises.acknowledgeNotificationSet to ensure that the same notifications aren't returned the next time you call Enterprises.pullNotificationSet.

You also have the option of setting requestMode to returnImmediately when calling Enterprises.pullNotificationSet. You'll receive a response to the request immediately, containing any pending notifications or an empty list if no notifications are present. This requestMode option may be useful when you initially test your notifications implementation.

Examples of EMM notifications

Here are some examples of events and the notification types that they generate:

Note: The following notification types have been deprecated: ProductApprovalEvent, AppUpdateEvent, NewPermissionsEvent, AppRestrictionsSchemaChangeEvent, ProductAvailabilityChangeEvent, and NewDeviceEvent. For AppUpdateEvent, you must use high-priority update mode as per our recommendations.