# Page Group

## Page Group

> **SUCCESS**
>
> **What is Page Group**
>
> Page Group is a feature that integrates multiple URLs and pages for unified management and analysis. This allows you to centralize scattered data and conduct analysis efficiently. "Average Page Duration" indicates the time visitors spend on each page group.

> **INFO** "Average Page Duration" refers to the time visitors spend on each page group.

## 💡**Common Use Cases**

Page groups are recommended for use in the following website operations scenarios.

### **1. Measuring Multiple Domains in the Same Project**

With Ptengine's paid version, you can register multiple domains in a single project.

The digest screen in the numerical report displays visitor data for all domains.

If you want to see data by domain, grouping pages by domain using page groups makes it easier to view.

### **2. Performance Analysis of Featured and Article Pages**

In web media where many pages with the same structure exist, such as articles and featured pages, using the page group feature allows for efficient comparative analysis of each page's performance.

For example, by batch-analyzing similar pages, you can accurately understand which content is being read better by visitors and which content attracts the most visitors.

### **3. Traffic Analysis for Owned Media**

The page group feature also plays an important role in traffic acquisition activities through owned media.

For example, you can list the performance of a series of articles related to a specific campaign and develop more efficient traffic acquisition strategies.

### **4. User Behavior Analysis on E-commerce Sites**

E-commerce sites have many pages with the same structure, such as product category pages and product detail pages.

By using the page group feature, you can analyze heatmaps of these pages in batch and understand user behavior patterns.

This allows you to gain insights for improving site usability.

### **5. Pages with Different UI Based on Parameters**

This is a pattern commonly seen in advertising landing pages (LPs) and similar cases.

When page UI is separated by parameter values and each provides different messaging to users, setting up page groups is necessary to check behavior data in batch. For example:

`www.ptengine.jp/?utm_campaign=``mail001``&utm_source=facebook&utm_keyword=ptengine`

`www.ptengine.jp/?utm_campaign=``mail002``&utm_source=facebook&utm_keyword=ptengine`

In the case of URLs like those above, the page UI and content differ for each parameter value (utm\_campaign) value (mail001, mail002).

It's convenient to set up page groups to analyze the performance of each.

By utilizing Ptengine's page group feature in scenes like those above, more detailed and efficient analysis becomes possible.

## **⚙️ Configuration Method**

🎦 You can view the video operation guide [here](/en/insight/data-center/content-page-group.md).

You can create page groups by going to "Settings" >> "Page Group Settings".

When you click "Add", the following popup appears.

① Enter the name.

② Select the matching rule.

Single Rule: You can group by setting URLs and following URL rule conditions. You can specify applicable URLs all at once by separating them with line breaks.

Multiple Rules: You can group in a form where multiple URL rules are mixed. You can select regular expressions here.

③ You can change the URL rule.

④ Enter the URL string. There is a character limit of 4000.

> **DANGER**
>
> **Important Notes**
>
> Page group data is accumulated from the point when the setting is configured. Therefore,
>
> Past values cannot be retroactively consolidated
>
> Only data after configuration is reflected


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://helps.ptengine.com/en/insight/data-center/content-page-group.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.