---
title: "Troubleshooting Real User Page Groups"
slug: "troubleshooting-real-user-page-groups"
updated: 2023-01-06T15:48:57Z
published: 2023-01-06T15:48:57Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting Real User Page Groups

## Overview

In some cases when Page Groups are set up, some pages may not show up under the intended group.

## Troubleshooting

1. View **App Settings**.
2. Scroll down to **Page Groups**.
3. Make sure the **Regex include hostname** setting is set to **Yes** if you are trying to group the page based on the hostname.
4. Make sure you do NOT have a generic regex setting all the way at the top.

Always put generic regex setting in the bottom since priority is given to the first URL regex in the App settings.

## Example

![](https://cdn.document360.io/cb4af8f9-6751-4fd2-b39c-07aae832badb/Images/Documentation/360000850331-mceclip3.png)

Notice how the **Checkout Page Group** has a generic regex in the above screenshot.

This causes pages such as `checkout.tele/account/login` to be pulled under the Checkout Page Group instead of the Login Page Group. Since Checkout was placed on the top, it took the highest priority when the page had a URL matching both Checkout and Login Page Groups.

## Solution

To fix this, move the Checkout Page Group to the bottom and update the regex to a more specific regex like **checkout/.** By doing this, the login Page group gets higher priority and now pages like `checkout.tele/account/login` will be pulled under the Login Page Group instead of the Checkout Page Group.
