When using the Google Cloud Messaging API to send messages between a backend server and an Android/Chrome client, the backend server can, at times, receive a rate limit exce
CCS downstream ack is not accounted in the quota.
The DeviceMessageRateExceeded quota is hit when you send too many messages to a single device - you don't need to backoff all sending, just to that registration ID. Please make sure you handle "Canonical" registration ID response - it is possible to have multiple regids pointing to the same device.
The 'quota_exceeded' was used in C2DM - GCM doesn't currently return it. If anyone is still using C2DM - the handling is to throttle/backoff sending for all messages. Or even better - to migrate to GCM which doesn't have this global quota.