Tracking
Tracking Page Type & Page Subtype
The Tracking Page Type & Page Subtype replace the previous Website Section and serve as tracking parameters at page level so that all pages are correctly included in the reporting. Please do not change page type and subtype on existing pages, if you think something is wrong here please send us a COMSupport (Component: Tracking) ticket via Jira to check if the page type or subtype needs to be adapted. Otherwise the reporting could be falsified.
The fields only need to be maintained once per page and are then transfered automatically for all languages.
When we copy new pages into your projects, these fields are already maintained by us and you don't have to do anything. If you create new pages in your projects, please add the tracking information. If you are unsure about the types, please create a COMSupport (Component: Tracking) ticket via Jira to check which page type or subtype needs is correct.
Here you can see an overview on alle page types & page subtypes:
| Page Type | Sub Type | Usage |
|---|---|---|
| EDP | Product | should be used for product pages from PIM |
| EDP | Decor | should be used for decor detail pages from PIM |
| EDP | Campaign | should only be used for group-wide campaigns that have a global program ID (e.g. EDC Campaign with ID 891) |
| EDP | Local Topic | should only be used for local campaigns |
| EDP | Sustainability | should be used for pages such as "Healthy Living Products", "Antibacterial Surfaces", etc. |
| EDP | Services | should be used for EDC related services such as EDC App, Decor Data Download etc. |
| EDP | Content | should be used for content that is not campaign related and does not come from PIM (e.g. Textures, EDC collection page, etc.) |
| Page Type | Sub Type | Usage |
|---|---|---|
| EFP | Product | should be used for product pages from PIM |
| EFP | Decor | should be used for decor detail pages from PIM |
| EFP | Campaign | should only be used for group-wide campaigns that have a global program ID (e.g. EFP Aqua Campaign with ID 871) |
| EFP | Local Topic | should only be used for local campaigns |
| EFP | Sustainability | should be used for pages such as "Healthy Living Products", "Antibacterial Surfaces", etc. |
| EFP | Services | should be used e.g. Floorng installation, FAQs etc. |
| EFP | Content | should be used for content that is not campaign related and does not come from PIM (e.g. Surfaces, Formats, Underlays, etc.) |
| Page Type | Sub Type | Usage |
|---|---|---|
| EBP | Product | should be used for product pages from PIM |
| EBP | Decor | should be used for decor detail pages from PIM |
| EBP | Campaign | should only be used for group-wide campaigns that have a global program ID (e.g. Decowall Campaign) |
| EBP | Local Topic | should only be used for local campaigns |
| EBP | Sustainability | should be used for pages such as "Healthy Living Products", "Antibacterial Surfaces", etc. |
| EBP | Services | should be used for EBP related services such as Digital Planning Tool, FAQ etc. |
| EBP | Content | should be used for content that is not campaign related and does not come from PIM (e.g. Packaging, formwork, trade fair construction, etc.) |
| Page Type | Sub Type | Usage |
|---|---|---|
| CC | Group | should be used for content pages in the About us area, such as History, Our Locations, Our values and culture etc. |
| CC | Press | should be used for the Press section (Press Overview, Press Releases) |
| CC | Sustainability | should be used for pages such as "Green Energy", "Sustainability at heart", "Climate Action", etc. |
| CC | News | should only be used for web news |
| CC | Local Topic | should be used for any local content apart from the Corporate Content provided by the group (e.g. Wood Purchasing) |
| Page Type | Sub Type | Usage |
|---|---|---|
| HR | Career | should be used for the content defined from the Corporate HR department |
| HR | Local Topic | should be used for all HR content on local level apart from the group standard |
| Page Type | Sub Type | Usage |
|---|---|---|
| myEGGER | EDP | applies for all group-wide content from EDP |
| myEGGER | EFP | applies for all group-wide content from EFP |
| myEGGER | EBP | applies for all group-wide content from EBP |
| myEGGER | Customer Portal | applies for all CUPO service pages (claims, offers, orders, etc.) |
| myEGGER | Industry Portal | applies for all IND portal pages |
| myEGGER | Partner/Campaign Portal | should be used for all local partner portal pages (C&C in Overseas, Campaign Portal, Partner Marketing Portal etc.) |
| myEGGER | Webshop | should be applied for all web shop pages |
| Page Type | Sub Type | Usage |
|---|---|---|
| Overall | no subtypes | valid for pages that cannot be assigned to a certain category, e.g. pages under footer navigation "Support", Product overview page, Process pages (e.g. Newsletter cancelled, Search Result, Subscription Success) |
You can add page types & subtypes via the page settings:
[1] click on page level
[2] click on the 3 dots next to the page name
[3] click on edit
[1] select the page type
[2] select the page subtype
[3] please always click on the + to add the subtypes otherwise they won't be added
Tracking Description & ID
Most components have the following two tracking fields:
- Tracking ID
- Tracking Description
The tracking ID has sometimes a default value when you open the editor. The tracking description is usually empty.
These two fields are NOT mandatory, as these components are automatically tracked by default without you adding or changing any of the default values. However, sometimes making changes and therefore adapting these fields to certain purposes can be useful. For example if you want to track an A and B test. In general, however, it is better to leave these fields empty unless you have a very good reason to use them.
If you decide to use these fields, please follow the naming convention, which is still being defined but will be communicated to you as soon as possible.
Data Image ID
The Data Image ID is also NOT mandatory, as this is also automatically tracked. The Data Image ID is only available for certain components that require advanced tracking, such as all types of sliders.
The idea behind Data Image ID is that you can, for example, give each element within a slider its own ID and thus track it separately. If you decide to use the Data Image ID, please follow the naming convention, which is still being defined but will be communicated to you as soon as possible.
last updated: 04/2025