Test Scenarios- User Cookies - Bloomreach Experience - Open Source CMS

Test Scenarios- User Cookies

Test Scenarios: User Cookies

 Scenario 1: Verify User Cookies

These first-party cookies are created by the Bloomreach tracking pixel library (BrTrk). They are randomly generated IDs that act as unique anonymous identifiers for every browser/device. The cookies have an expiration of 1 year.

For all pixels (across all pages), the following fields should be mandatorily active: cookie2 (_br_uid_2): User ID + User Extended Info.

Scenario Flow

Expected Result/ Pixels to Fire

Additional Verification

Start at the Homepage Homepage PageView Pixel 
The _br_uid_2 parameter in the PageView Pixel should be populated.
 
Navigate to a Category Page Category PageView Pixel
The _br_uid_2 parameter in the PageView Pixel should be populated.
 
Navigate to a Product Page Product PageView Pixel
The _br_uid_2 parameter in the PageView Pixel should be populated. 
 
Navigate to a Content Page Other PageView Pixel 
The _br_uid_2 parameter in the PageView Pixel should be populated.
 
Enter a Search Term in the Search Bar and Click Search 
Icon or hit Enter to start a Search.

This will bring you to a search results page.


Click on a Product.
Search Event Pixel



Search PageView Pixel
The _br_uid_2 parameter in the PageView Pixel should be populated.

 

Add the Product to the cart (from the PDP page) ATC Event Pixel
The _br_uid_2 parameter in the PageView Pixel should be populated.
If your site does not have Skus, leave the Sku field empty, even though the validator will show a red flag for Sku.
Check out the product Other PageView Pixel On the 'Thank you' page

The _br_uid_2 parameter in the PageView Pixel should be populated.

Make sure that “prod_id” for a given product is the same value across:

  1. Product Page View

  2. Add to Cart Event

  3. Basket in Conversion Event

  4. The product feed sent to Bloomreach

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?