# Insight Glossary

### Visitors (UV) <a href="#fang-wen-zhe-uv" id="fang-wen-zhe-uv"></a>

The number of people who visited the website within a specified time period. Within that period, the same user is counted as 1 UV regardless of how many times they visit. Whether a user is the same person is determined by the user identifier (uid). If the uid is the same, they are considered the same user. The uid is stored in the browser's cookie, so switching browsers or devices will result in being counted as a different user. Additionally, in Safari, because the cookie retention period is 7 days, if a user revisits after more than 7 days, the cookie will be deleted and they will be counted as a new user.

### Sessions <a href="#fang-wen-ci-shu" id="fang-wen-ci-shu"></a>

The number of visits to the website. Also known as session count. When a user visits the website, it counts as 1 session. If the user leaves the website and then returns, it counts as another session. A session ends (the user leaves) in the following situations:

1. The browser (tab) is closed. 2. The user navigates to a page within the project that is not being tracked. 3. The user has no activity for a certain period of time.

Note: Definition of no activity for a certain period of time. Activity: Behaviors such as clicking, scrolling, typing, reloading a page, or opening a new page have not occurred. Time: The default session timeout is 30 minutes. You can also customize this duration.

Within the above time period, if the user returns from a different traffic source (excluding direct traffic), it will be counted as a second session. If the traffic source is the same, a new session will not be counted.

### Pageviews (PV) <a href="#liu-lan-liang-pv" id="liu-lan-liang-pv"></a>

The number of times a page is loaded. "Loaded" refers to the number of times Ptengine's JavaScript tracking code is loaded; each load counts as 1 PV.

### Pages per Visitor <a href="#ren-jun-liu-lan-ye-shu" id="ren-jun-liu-lan-ye-shu"></a>

The average number of pages viewed per visitor, reflecting both website content quality and visitor quality.

### Clicks <a href="#dian-ji-shu" id="dian-ji-shu"></a>

PC: The number of "mouse clicks".\
Smartphone: The number of "touches." All taps are counted regardless of whether a link exists, and consecutive clicks/touches are also counted.

\*For smartphones and tablets, touches from swiping and pinch-to-zoom gestures are not counted as clicks.

### New Visits (New Session Count) <a href="#xin-fang-xin-fang-ci-shu" id="xin-fang-xin-fang-ci-shu"></a>

The total number of sessions from users visiting the website for the first time since the profile was created.\
If there is no historical visit record within the project's website, the visitor is considered new. Even if they have visited before, if the user has deleted cookies or other data, they will be considered a new visitor.

### New Visit Percentage <a href="#xin-fang-ci-shu-bai-fen-bi" id="xin-fang-ci-shu-bai-fen-bi"></a>

The proportion of new visitor sessions out of total sessions.\
New Visit Percentage = New Sessions / Total Sessions.

### Return Visits (Return Session Count) <a href="#hui-fang-hui-fang-ci-shu" id="hui-fang-hui-fang-ci-shu"></a>

The number of sessions from users who have visited the website 2 or more times within the cookie retention period (\*).\
Return Sessions = Total Sessions - New Sessions.

(\*) When a user interacts with Ptengine's tracking code, Ptengine provides a persistent cookie to the browser that does not expire. Whether a visitor is classified as "new" or "returning" depends on whether this cookie is retained. However, due to ITP, for Safari users, we distinguish between new and returning visitors based on the past 7 days.

### Return Visit Percentage <a href="#hui-fang-ci-shu-bai-fen-bi" id="hui-fang-ci-shu-bai-fen-bi"></a>

The proportion of return visitor sessions out of total sessions.\
Return Visit Percentage = Return Sessions / Total Sessions.

### Average Load Time <a href="#ping-jun-jia-zai-shi-chang" id="ping-jun-jia-zai-shi-chang"></a>

The average time it takes for a page to finish loading.\
This measures the time from the page request to the completion of page loading for each page.\
Average Load Time = Total page load time across all visits / Number of visits. ms = 1/1000 of a second; for example, 629ms = 0.629 seconds.

### Average Time on Site <a href="#ping-jun-ting-liu-shi-jian" id="ping-jun-ting-liu-shi-jian"></a>

\#Calculated separately based on sessions and pages:

* Session-based\
  The average duration of a session.\
  Average Time on Site = Total time from entry to exit across all visits / Total number of visits.
* Page-based\
  The average time spent on a specific page (view duration).\
  Average Time on Page = Total time spent on the specific page / Total PV count for that page.

### Dimension <a href="#wei-du" id="wei-du"></a>

We commonly use "dimension" to describe characteristics such as size or color, but in data analysis, it typically refers to user attributes: traffic source, device, channel, geographic information, etc.

### Metric <a href="#zhi-biao" id="zhi-biao"></a>

In web data analysis, metrics generally fall into two types: volume metrics and quality metrics. Volume metrics: Sessions, PV, UV\
Quality metrics: Average session duration, pages per visit, bounce rate, new visit percentage.

### Filter Toggle <a href="#guolkai-guan" id="guolkai-guan"></a>

You can quickly view a specific attribute in the data center. For example, you can use the segment feature to view metrics such as PV and sessions for smartphone users only.

### Segment <a href="#xi-fen" id="xi-fen"></a>

A feature that allows you to group specific sessions or users together. Using segments, you can split and analyze subsets of your data. For example, by applying a segment to an ad channel, you can determine which ads led to conversions.

### Bounces <a href="#tiao-chu-shu" id="tiao-chu-shu"></a>

A bounce occurs when a user lands on a page and ends their visit without navigating to any other page.

### Bounce Rate <a href="#tiao-chu-l" id="tiao-chu-l"></a>

Bounce Sessions / Total Sessions.\
Reflects both page quality and visitor quality.

Note: Compared to Google Analytics, Ptengine's bounce rate tends to be higher because Ptengine considers a visit ended if the user has no activity on the site for a certain period of time. Different measurement tools have different session timeout limits.

Ptengine:\
By default, PC: 5 minutes (for projects created on or after January 11, 2021, PC is 30 minutes), Mobile: 5 minutes.

Google Analytics:\
30 minutes for both PC and mobile.\
Therefore, especially for smartphones, Ptengine's criteria are stricter than Google Analytics, which tends to result in a higher bounce rate.

### Exits <a href="#tui-chu-shu" id="tui-chu-shu"></a>

The number of times a page was the last page viewed in a session. This means the visit ended on that page.

### Exit Rate <a href="#tui-chu-l" id="tui-chu-l"></a>

Exit Rate = Number of Exits / PV count for that page.\
The exit count is the number of times a page was the last page viewed in a session, meaning the visit ended on that page.

### Keywords <a href="#guan-jian-ci" id="guan-jian-ci"></a>

The keywords a user searched for on a search engine when visiting the website.

### Traffic Acquisition <a href="#liu-liang-huo-qu" id="liu-liang-huo-qu"></a>

A method of grouping traffic by rules. Ptengine's default channels include External Links, Search Engines, Social Media, Direct Traffic, and Ads. You can also create custom channels based on traffic sources. For information on custom channels, please refer to \[here].

### Profile <a href="#dang-an" id="dang-an"></a>

Refers to the website used for data measurement. By setting up a website as a profile, you can measure that website's data.

### Entry Page <a href="#jin-ru-ye-mian" id="jin-ru-ye-mian"></a>

Also known as a "landing page." The first page a user visits.

### Entry Count <a href="#jin-ru-ci-shu" id="jin-ru-ci-shu"></a>

The number of times a page was visited as the entry page.\
The entry page is also known as a "landing page" -- the first page a user visits.

### Entry Rate <a href="#jin-ru-l" id="jin-ru-l"></a>

Entry Count / PV count for that page.

### Raw Page <a href="#yuan-shi-ye-mian" id="yuan-shi-ye-mian"></a>

Refers to pages with unique URLs.\
For example, you can view the original URL and URLs with parameters separately:\
`http://aaa.com/about/`\
`http://aaa.com/about/?gclid=18jnie97dg`\
`http://aaa.com/about/?utm_source=google`

### Merged Page <a href="#he-can-ye-mian" id="he-can-ye-mian"></a>

Used to merge data for the original URL and URLs with parameters.\
Example:\
Merged page:\
`http://aaa.com/about/`\
When viewing data with a merged page, the data includes all of the following URLs:\
`http://aaa.com/about/`\
`http://aaa.com/about/?gclid=18jnie97dg`\
`http://aaa.com/about/?utm_source=google`

### Heatmap <a href="#re-tu" id="re-tu"></a>

The heatmap feature visually displays user behavior on a website. It shows where users look and click, as well as what content attracts their attention.

### Conversion (CV) <a href="#zhuan-hua-cv" id="zhuan-hua-cv"></a>

Refers to detecting when a desired goal or action is achieved by a user on the website.\
In Ptengine, conversions are measured in the following 3 scenarios:

1. Visiting a specific page URL. By specifying the page a user will see after completing a specific action, you can measure outcomes.\
   Examples:\
   \*Member registration: A page containing "Submit"\
   \*Product purchase: A "Thank\_You" page, etc. If a user reaches the specified page, 1 conversion is counted.
2. Visiting a specified page group. When a user visits a page in the specified page group, 1 conversion is recorded.
3. Triggering an event. When a user completes an event configured in Ptengine, 1 conversion is recorded.

### Conversion Count <a href="#zhuan-hua-shu" id="zhuan-hua-shu"></a>

The number of sessions in which a conversion occurred.

### Conversion Rate <a href="#zhuan-hua-l" id="zhuan-hua-l"></a>

Conversion Count / Total Sessions.

### Standard Conversion <a href="#chang-gui-zhuan-hua" id="chang-gui-zhuan-hua"></a>

Standard conversions such as revenue, orders, and form submissions.

### Negative Conversion <a href="#fu-xiang-zhuan-hua" id="fu-xiang-zhuan-hua"></a>

Negative conversions such as membership cancellations and returns.

### Conversion Value <a href="#zhuan-hua-jia-zhi" id="zhuan-hua-jia-zhi"></a>

The assigned value per conversion multiplied by the number of conversions. For example: 1 conversion = $20, 20 conversions, so conversion value = 20 x 20 = $400.

### Conversion Funnel <a href="#zhuan-hua-lou-dou" id="zhuan-hua-lou-dou"></a>

The conversion funnel lets you understand the steps users take to reach a conversion goal, how many users proceed to the next step at each stage, and how many drop off at each stage.

### Event <a href="#shi-jian" id="shi-jian"></a>

Events refer to user interaction behaviors on a website that can be configured through Ptengine.

Examples:\
How many "Add to Cart" button clicks occurred\
How many clicks occurred on the hero banner\
How many clicks occurred on key CTAs... and so on.


---

# 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/glossary.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.
