page
- 3 Minutes to read
- Print
- DarkLight
page
- 3 Minutes to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Overview
| Value | Description | Data type | Default value | Required | Where to analyze | Request Parameter |
|---|---|---|---|---|---|---|
| name | Unique identifier of your page. By default, the page URL is used. Parameters and hash in the URL are excluded. See the chapter advanced to include it. | String | url based page name | Yes | Navigation > Pages > Pages | p |
| search | Contains internal search terms. | String | - | Marketing > Search Phrases > Internal Search Phrases | is | |
| numberSearchResults | The number of search results. | Number | 0 | - | Metric | cp771 |
| errorMessages | Send this parameter if an error message occurs. Send the error code an/or the error message as value. | String | - | Navigation > Page Parameters | cp772 | |
| paywall | Allows flagging paywall articles. | Boolean | false | - | Metric | cp773 |
| articleTitle | Title of the article. | String | - | Navigation > Page Parameters | cp774 | |
| contentTags | Tags contained in the article. You can send multiple tags | String | - | Navigation > Page Parameters | cp775 | |
| title | Title of the page. Improves readability in analyses and reports. | String | - | Navigation > Page Parameters | cp776 | |
| type | Page type. | String | - | Navigation > Page Parameters | cp777 | |
| length | Length of the page. | String | - | Navigation > Page Parameters | cp778 | |
| daysSincePublication | Days since the publication of the article. | Number | 0 | - | Navigation > Page Parameters | cp779 |
| testVariant | Name of the test variant. | String | - | Navigation > Page Parameters | cp780 | |
| testExperiment | Name of the test. | String | - | Navigation > Page Parameters | cp781 | |
| parameter | Use page parameters to add additional information to a page. Find details below. | Object | - | Navigation > Page Parameters | cp[ID] | |
| category | You can use this parameter to categorize pages. Find more details below. | Object | - | Navigation > Content Groups | cg[ID] | |
| goal | Use goals to track the success of your website and campaigns. Find more details below. | Object | - | Marketing > Website Goals | cb[ID] |
Further information
category
Page-related categories are called content groups. You can track them onsite or import data. Learn about use cases here. Before use, categories must be set up under Mapp Q3 > Configuration > Categorisation > Content Groups. The ID and data type (text/number) are defined for each parameter during setup. Find more info here.Example (parameter with ID "1"): {1:"Woman"}
Content groups are assigned once to a page only: in the first-ever request of a page. We, therefore, recommend implementing page and content group tracking in parallel.See also How can I replace missing values ("-") in categories?
parameter
In contrast to categories, parameters can track different values with each page request. Find more details here. Before use, parameters must be set up under Mapp Q3 > Configuration > Custom Parameters > Page Parameter. The ID and data type (text/number) are defined for each parameter during setup. Find more info here.Example (parameter with ID "1"): {1:"position-1"}
goal
Website goals help to track the success of your website. You can quickly analyze and filter individual goals in Mapp Intelligence. Furthermore, the calculation of the customer journey is based on website goals. This means you can track which campaigns are responsible for a goal's achievement. Find more info here. The website goal "Order" is predefined in Mapp. A goal parameter has to be set on the corresponding pages if you have other website goals.Typical examples are:
- newsletter registration
- signup
Configuration
- A parameter must be set up under Configuration > Custom Parameters > E-Commerce Parameter.
- The ID and data type (text/number) are defined during setup.
- Website goals have to be configured at Configuration > Goal.
- When configuring tracking in the pixel, you need to include the ID as a number and the respective value as a string.
The goal is set as achieved as soon as a parameter is tracked (no matter what value is submitted!).
Implementation Example
import { WebtrekkSmartPixelReact, WebtrekkPageData } from "@webtrekk-smart-pixel/react";import { WebtrekkSmartPixelReact, WebtrekkPageData } from "@webtrekk-smart-pixel/next";If you do not have automatic page tracking enabled, invoke the track method after adding all relevant tracking information.
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"}
});If you do not have automatic page tracking enabled, invoke the track method after adding all relevant tracking information.
render()
{
return (
<div>
<WebtrekkPageData
name="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"} }
/>
</div>
);
}Was this article helpful?