--- title: "Pages" slug: "react-next-page" updated: 2025-03-27T14:03:32Z published: 2025-03-27T14:03:32Z canonical: "docs.mapp.com/react-next-page" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.mapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Pages ## 1 Overview This page provides a comprehensive guide on how to track and analyze page-related data in Mapp Intelligence. It details the configurable properties, analysis locations, and request parameters. ### 1.1 Individual Setup Only **name** and **search** are automatically available when data is transmitted. All other properties—whether Page Parameters, Categories, or Goals—require individual setup. While most customers receive a predefined configuration, all these elements can be fully customized based on tracking requirements. Before defining new parameters, categories, or goals, check your existing setup to determine which elements are already available and which need to be configured manually. --- ## 2 Configurable Properties The following table outlines all supported properties, their descriptions, and request parameters. | Property | Description | Data Type | Request Parameter | | --- | --- | --- | --- | | **name** | Unique identifier of your page. By default, the page URL is used. Parameters and hash in the URL are excluded. This property is **automatically available**. The value is analyzed in *Navigation > Pages > Pages*. | String | `p` | | **search** | Contains terms entered in the internal search of the website or app. This property is **automatically available**. The value is analyzed in *Marketing > Search Phrases > Internal Search Phrases*. | String | `is` | | **numberSearchResults** | The number of results returned in an internal search query. This is a **Page Parameter** and requires setup. The value is analyzed as a **metric**. | Number | `cp771` | | **errorMessages** | Tracks error messages on the page, such as system errors or missing content warnings. This is a **Page Parameter** and requires setup. The value is analyzed in *Navigation > Page Parameters*. | String | `cp772` | | **paywall** | Indicates whether an article is behind a paywall. This is a **Page Parameter** and requires setup. The value is analyzed in *Navigation > Page Parameters*. | Boolean | `cp773` | | **articleTitle** | Captures the specific title of an article in addition to the general page name. This is a **Page Parameter** and requires setup. The value is analyzed in *Navigation > Page Parameters*. | String | `cp774` | | **contentTags** | Allows tagging articles with multiple categories or keywords for analysis. This is a **Page Parameter** and requires setup. The value is analyzed in *Navigation > Page Parameters*. | String | `cp775` | | **title** | Stores a readable version of the page title for improved reporting and analysis. This is a **Page Parameter** and requires setup. The value is analyzed in *Navigation > Page Parameters*. | String | `cp776` | | **type** | Defines the type of page (e.g., "overview"). This is a **Page Parameter**and requires setup. The value is analyzed in *Navigation > Page Parameters*. | String | `cp777` | | **length** | Specifies the length classification of the page (e.g., "large"). This is a **Page Parameter** and requires setup. The value is analyzed in *Navigation > Page Parameters*. | String | `cp778` | | **daysSincePublication** | Tracks how many days have passed since an article was published. This is a **Page Parameter** and requires setup. The value is analyzed in *Navigation > Page Parameters*. | Number | `cp779` | | **testVariant** | Stores the name of a test variant for A/B testing. This is a **Page Parameter** and requires setup. The value is analyzed in *Navigation > Page Parameters*. | String | `cp780` | | **testExperiment** | Captures the name of an experiment in A/B testing. This is a **Page Parameter** and requires setup. The value is analyzed in *Navigation > Page Parameters*. | String | `cp781` | | **parameter** | Tracks additional custom data points for a page. More details below. | Object | `cp[ID]` | | **category** | Groups pages into structured content categories. More details below. | Object | `cg[ID]` | | **goal** | Defines and tracks key website goals. More details below. | Object | `cb[ID]` | ### 2.1 Page Parameters Page parameters refer to individual pages and are used to track additional details such as error messages, content tags, and test experiments. - Mapp Intelligence provides a set of predefined Page Parameters, including those listed in the table above (e.g., `paywall`, `title`, `type`). These predefined parameters can be enabled as needed. - Additionally, users can create completely custom Page Parameters if their tracking requirements go beyond the predefined options. Custom parameters allow you to track any additional data relevant to your website. - Values can be analyzed in *Navigation > Page Parameters* if they are of type **text**, or as **metrics** if they are of type **number**. For setup instructions: [How to Set Up Custom Parameters](/v1/docs/how-to-set-up-custom-parameters) ### 2.2 Categories (Content Groups) Categories define **fixed classifications** for pages, typically used to group content into structured areas. - Categories are assigned once to a page, in the first-ever request of that page, and do not change unless imported manually. - The ID and data type (text/number) are defined during setup. - Categories are useful for defining **structural groupings**, such as: - **Main Section** of a website (e.g., "News," "Sports," "Lifestyle") - **Subsections** within a main section (e.g., under "News": "Politics," "Technology," "Economy") - It is recommended to implement page and content group tracking in parallel. - Values can be analyzed in *Navigation > Content Groups* if they are of type **text**, or as **metrics** if they are of type **number**. For setup instructions: [How to Set Up Categories](/v1/docs/how-to-set-up-categories) > [!NOTE] > Content groups are assigned one time to a page. If a page is tracked together with a content group, all subsequent page calls of the page will also be assigned to this content group. Only the first-ever tracked value will be shown. > > We, therefore, recommend implementing content IDs and content groups while embedding the pixel. > > See also [How can I replace missing values ("-") in categories?](/v1/docs/how-can-i-replace-missing-values-in-categories) ### 2.3 Goal Tracking Goal tracking allows you to measure when a specific action has been completed on a page. This is essential for evaluating user behavior and performance. - Goals can be used to track specific actions completed on a page, such as a newsletter signup or user registration. - They are crucial for campaign success analysis, enabling attributed campaign evaluation. Ideally, users interacting with a campaign complete a goal, which must be tracked. - If a goal should be tracked when a page loads, it needs to be explicitly passed. - The Order goal is predefined for e-commerce tracking and does not need to be manually set on a page. - Goals can be analyzed in *Marketing > Website Goals*. For setup instructions: [How to define website goals](/v1/docs/how-to-define-website-goals) --- ## 3 Implementation Example ```javascript import { WebtrekkSmartPixelReact, WebtrekkPageData } from "@webtrekk-smart-pixel/react"; ``` ```javascript import { WebtrekkSmartPixelReact, WebtrekkPageData } from "@webtrekk-smart-pixel/next"; ``` > [!NOTE] > If you do not have [automatic page tracking](/v1/docs/react-next-installation-and-integration) enabled, invoke the [track](/v1/docs/react-next-track) method after adding all relevant tracking information. ```javascript WebtrekkSmartPixelReact.page("name of the page", {      search: "search term",      numberSearchResults: 7,      errorMessages: "error: ...",      paywall: false,      articleTitle: "article title",      contentTags: "content tags",      title: "page title",      type: "page type",      length: "medium",      daysSincePublication: 5,      testVariant: "test variant",      testExperiment: "test experiment",      parameter: {5: "parameter value 5"},      category: {8: "category value 8"},      goal: {2: "goal value 2"} }); ``` > [!NOTE] > If you do not have [automatic page tracking](/v1/docs/react-next-installation-and-integration) enabled, invoke the [track](/v1/docs/react-next-track) method after adding all relevant tracking information. ```javascript render() {     return (         
                     
    ); } ``` A **Request Parameter** displays the name of the parameter included in a tracking request. This information is crucial for debugging purposes (e.g., via **Mapp Cloud Debugger**), allowing you to verify the data transmitted to Mapp and understand how it is recorded.