### **Category Page View Tracking **
Go to your Category Page Template and add the category specific tracking parameters in the Global Tracking snippet. If your category pages are loaded via Dynamic Refresh outside the regular page load cycle, please add additional handlers to be able to [track virtual page view interactions](🔗).
#### Faceting, Filtering and Pagination on Category Pages
If a user applies a facet filter and refreshes results, Bloomreach expects that the Category Page View pixel fires each time a filter is applied. Bloomreach uses this information to understand which filters are commonly used. In case your implementation is such that pages don't reload when a user applies a filter or facet, please add additional handlers to each filter/ facet to be able to [track virtual page view interactions](🔗). If your category pages are paginated, Bloomreach expects that the Category Page View pixel fires each time a user navigates to the next or previous category page. If your category pages don't reload when a user navigates to the next or previous page, please add additional handlers to the 'next' and 'previous' links to be able to [track virtual page view interactions](🔗).
## Category Page View Variables
| Variable | Value type, example | Description |
| br_data.cat_id | string (case sensitive), "106121" | Unique category ID as referred to in the database/catalog. Bloomreach requires the cat_id field to be unique across your site. The _cat_id_ value needs to match the _crumb_id_ value in your feed. For Search implementations, the same _cat_id_ value needs to be passed in the API call. To determine what value to use for your category ID, refer to the [Category ID Scenarios](🔗). |
| br_data.cat | string (delimited by a | character), "106120|106121|106122" | The bread crumb of the page. Value needs to match the _crumb_ value in your feed. To determine what value to use for your bread crumb, refer to the [Bread Crumb Scenarios](🔗). |
## Category ID Scenarios
| Scenario | Category ID value | Example value |
| Unique Category ID for every category (preferred scenario) | Bloomreach expects the leaf node Category ID to be sent in the pixel. | br_data.cat_id="106121" |
| Site does not have a unique category ID for every category, but it has a unique crumb path for every category | Concatenate the unique crumb path without any delimiters or special characters, and send this value in the cat_id field. | For a unique crumb path of "jewelry|by-collection|inspirational-jewelry": br_data.cat_id="jewelrybycollectioninspirationaljewelry" |
| No unique category ID, no unique crumb path | Please talk to your Bloomreach TPM before or during the Kickoff call to discuss options for your implementation. | |
## Bread Crumb Scenarios
| Scenario | Bread crumb value | Example value |
| You have a numeric representation of your bread crumb | Bloomreach expects the full bread crumb path, separated by pipe (|). | The crumb path is Home > Top > Casual Top with the following category IDs: <li>Home = 106120</li><li>Top = 106121</li><li>Casual Top = 106122</li> br_data.cat="106120|106121|106122" |
| Your site has a unique bread crumb path for every category. | Bloomreach expects the full bread crumb path, separated by pipe (|). | The crumb path is Home > Clothing > Outerwear. br_data.cat="Home|Clothing|Outerwear" |
| No unique category ID, no unique crumb path | Please talk to your Bloomreach TPM before or during the Kickoff call to discuss options for your implementation. | |
## Native App Implementation
Discovery SDKs
For details on using the Discovery [Android](🔗) and [iOS](🔗) SDKs for specific Native App Implementation, refer to their respective linked guides.
You can include the [Global Page View variables](🔗) and the following variables for native app implementation.
ptype = category
cat_id (see above)
cat (see above)
Refer to the Implementation Scenarios above for specific use cases of cat_id and cat.
Example requests: