Are there any reporting options for custom pages?

There is not reporting for custom pages - Reporting cues from content views and custom pages are technically not content items. Would recommend looking into Google Analytics or another page tracking product for more granular information about page navigation that isn't content items.

How would we work around this for custom pages (and presumably group 'home' pages?) as google analytics and adobe analytics are susceptible to lack of tracking due to Cookies being blocked due to consent requirements in Europe.

I think there is a misconception of what the functionality is meant to do.  It is meant to register views of content, not web page views.  There are other tools(such as the mentioned google analytics) for generic page view tracking, community is focusing on viewing community data.  If a custom page contains a widget with full content on it, and the widget implements the content view tracking, then the view of the content will be registered.

Patrick M. said:

and the widget implements the content view tracking

But what if the widgets don't have content associated with them for view tracking?

In the marketing world there's often "landing pages" created that are gateways to more content, and custom pages are used in this way. So in our scenario we want to track visits and views to that page.

As the 'custom page' is an entity on the community platform, we would expect that entity to be tracked in views. Especially as we mentioned the issue with google analytics and adobe analytics, gdpr comes into play because of passing the data to a third party, which is why a group or custom page as an entity tracking its views is important outside of those ecosystems.

Patrick M. said:

and the widget implements the content view tracking

But what if the widgets don't have content associated with them for view tracking?

In the marketing world there's often "landing pages" created that are gateways to more content, and custom pages are used in this way. So in our scenario we want to track visits and views to that page.

As the 'custom page' is an entity on the community platform, we would expect that entity to be tracked in views. Especially as we mentioned the issue with google analytics and adobe analytics, gdpr comes into play because of passing the data to a third party, which is why a group or custom page as an entity tracking its views is important outside of those ecosystems.

There is going to be a difference between content and pages and the platform has many associated pages that are not specifically loaded with content that do not track content views(like landing pages).  Its generally only when viewing a content item in its entirety, like a blog post page.