Client buys our analytics services and includes our analytics SDK in his mobile app. Users who download the app will start sending us lots of data. When the client stops paying for our analytics all the data is still coming and it affects our bandwidth and clutters our request handling.
We can easily stop all SDK from sending data but it will be final, so if the client decides to renew the service he will have to re-upload SDK again which takes time and effort on his part. We can also lower the amount of calls to 1 per 24h but with lots of clients that is till a lot of useless data calls.
Is there a way to design server architecture so that when a client stops paying for our services, all incoming calls from his apps will be excluded and will not effect the incoming server bandwidth and request handling?
Some cumbersome solutions: provide each client with a specific subdomain, or port. Then remove the subdomain or port after he stops using the service (limited and still affects request handling)
Thanks for help.