Live demo improvement about consuming resources

We decided to identify any client using the live demo using his IP. Maybe this is no the best way of doing:

What if I use dinyamic IPs? People going to the web page once, create a subscription (queue) that maybe will not use again The service we used to detect IPs is not always working (quota exceeded, and similar things). At the end, we have rabbit full of unused queues consuming resources. We need an smart way of implementing that demo:

Using IP but deleting the subscription when you close, login, etc? We can delete all the queues created for the live demo from time to time We can identify unique users in a better way?