Just so this remains a light in a tunnel full ideas, I'm posting in agreement to the OP. Linking to HipChat would be way more useful if we could associate only certain pages/subpages to applicable HipChat rooms.

On our team space we post our projects and then drill down to various parts of it. When there is an update for one project, I don't want to update HipChat rooms related to projects other than the one I'm updating. 

I 100% agree with the OP.

It would be stupendously useful if we could have alerts about PAGE activity sent to a HipChat ROOM.  

Rooms are for groups, and groups often need to know what's going on with a page that corresponds to that group....they don't need to know about anything that gets updated in the whole SPACE.

Think about it this way.  You set up a TESTING space, and within that you have rooms for Software, Hardware, etc.  You don't want the software folks to get an alert in their Software HipChat room everytime the Hardware folks update their page within the same SPACE.

Hi everyone,

Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use HipChat so we can continue improving your experience. We have reviewed this issue and want to provide an update.

We've made significant investments in our Connect integration framework over the last year, and our integration teams are returning their focus to taking advantage of these new capabilities from Atlassian's other applications, like JIRA and Confluence.

We have no timelines to announce, but we're working to make the Confluence + HipChat integration more valuable.

We will continue to update this and the other top voted issues here in our public issues tracker, so please watch this issue and you'll be notified about future updates.

Please remember that your suggestions on jira.atlassian.com are one of many inputs for the HipChat roadmap. You can learn more about our process here.
We thank you for your feedback, and will continue to listen to you and all our customers to better understand your needs.

Regards,
The HipChat Team

Agreed - would happily follow the model used in Jira - this would work fine for my use case and allow me to pick the level of granularity I want.

A related request to Filter confluence notifications to hipchat room just came up on AAC - I suggested that implementing CQL filters similar to the JIRA HipChat integration would cover both requests (and much more) in the seemingly most natural way:

While CQL had been introduced as a developer level API only initially, the Confluence team has meanwhile surfaced CQL filters in the powerful Content by label macro, so adding it to the Confluence HipChat integration would be an obvious and similar powerful choice.

We'd also love this feature. Space level integration is too high level to use for a hc room.

We'd love to have this improvement. We've got several spaces that span multiple topics like social activities.

I can't vote enough for this improvement.

This is extremely useful as it allows for a room to be linked to a certain page (and/or children pages). For example, within our Confluence setup, we have a Projects space. This space consists of a myriad of project pages of varying and bewildering complexity and each of these projects are tied to specific teams. It would be great to have each project page (and children pages) pushing notifications to their respective HipChat rooms which in turn notifies the relevant team in real-time.

The current implementation of the HipChat integration only notifies users of changes at a Space level which is way too broad.

We would really like this since we can do similar things with the Jira->Hipchat integration.