Quick View Event Pixel
What are Quick View Pixels
Any time a user opens a Quick View to display more details about a product on your site, Bloomreach expects a Quick View Event to fire.
Quick Views are commonly found on Product Listing pages, but if there are any other locations on your site that trigger a Quick View, please install this Pixel there as well.
How to Implement Quick View Pixels
If you do not have Quick View functionality on your site, you can skip implementing this Pixel.
Follow the steps below:
- Copy and paste the Quick View Event Tracking Snippet on all of your Quick View links or Quick View buttons to install the Pixel.
- Configure the Quick View Event Variables in the Tracking Snippet.
- Make sure to review the implementation scenarios to ensure that the Quick View Event data is correctly sent to Bloomreach.
Quick View Pixels Variables Checklist
Listed below are the tracking variables required specifically for Search Event Pixels.
Required Variables
| Variable | Value type, Example | Description |
|---|---|---|
| acct_id | String, “1235” | The Bloomreach-provided Account identifier. Value must be consistent with the account_id value passed in API call. |
| group | String, “cart” | This specifies the event grouping. Allowed values: suggest, cart, product, widget |
| etype | String, “click” | Specifies the event’s action type. Allowed values: click, click-add, quickview, submit |
| prod_id | String (Case sensitive), “prod1234” | The unique product ID, which describes a product, product bundle, product collection or SKU set. |
Optional Variables
| Variable | Value type, Example | Description |
|---|---|---|
| user_id | String, “61WwurfPU9f9dB5” | If you track users via a universal customer ID, populate this parameter with that ID. This should be an anonymized string and not any PII. |
| prod_name | String, “Men’s Fleece Jacket” | The name of the product being viewed or added to the cart. |
| sku | String, “sku7778” | Unique sku ID representing the selected variant of this product (e.g., size M, color blue of a t-shirt). This must match the SKU ID field in the feed. |
| prod_collection_id | String, “collection5678” | The unique ID of a Product Collection. This needs to be passed when the relevant Event occurs from a Product Collection page. |
Conditional variables - based on your implementation
| Variable | Value type, Example | Description |
|---|---|---|
| view_id | String (Case sensitive), “10200” | The name of the product catalog view that would be searched against on the page where the event occurred. It identifies the catalog view to show when one Bloomreach account ID hosts multiple site versions. |
| domain_key | String (Case sensitive), “bloomreach_fr” | The Bloomreach-provided ID of the domain receiving the request. Set Domain Key to the name of the product catalog that would be searched against on the page where the event occurred. |
| title | String, “Best Sellers” | This is the title of the current page or screen name of the app view. |
| ref | String, “https://www.homeoasis.com/category/mens-clothes" | This is the URL from the referrer screen. For a native mobile app, “ref” follows a synthetic structure that is used for identifying the content within the app rather than actual navigable URLs. |
For a full list of required and optional variables, see Pixel Reference
Implementation Scenarios
Product ID Scenarios
If you sell Collections, you can implement the pixel in several different ways. The table below outlines multiple scenarios and the pixel requirements for each.
| Scenario | Examples |
|---|---|
| Product Collections have their own unique ID and are sold exactly like standalone products | Enter the collection ID. Make sure that this collection ID is sent in the feed as a product ID. If your collection ID is collection5678, prod_id="collection5678" |
| Product Collections have their own unique ID, but cannot be purchased as a whole; only a collections' individual parts can be purchased. Each of these individual parts have their own ID | Enter the collection ID. Make sure that this collection ID is sent in the feed as a product ID. If your collection ID is collection5678, prod_id="collection5678" |
| Products that are a part of a Collection but can be purchased from their own individual product page | Enter the product ID. If your product ID is prod1234, prod_id="prod1234" |
Quick View on Category Page with Product ID and Sku ID
Example:
BrTrk.getTracker().logEvent("product", "quickview",
{"prod_id": "348574","prod_name":"Levi's Jeans Model 505", "sku":"348574"});
Tracking Snippet for Quick View Pixels
JavaScript Implementation
BrTrk.getTracker().logEvent("product", "quickview", {"prod_id" : "348574","prod_name": "Levi's Jeans Model 505","sku":"348574"});
Non-JavaScript Implementation
To integrate Bloomreach Pixels in a Non-JS Environment, you can choose one of the following options:
Validate Pixel Implementation
Once Pixel implementation is complete, use the Pixel Validator Chrome Plug-in to validate if the Quick View Event Pixel is working as expected. Follow the scenarios listed in the Test Scenarios - QuickView guide.
Troubleshooting
Refer to the following help articles to troubleshoot issues related to the Quick View Event Pixel:
Monitor and Manage Pixel Data
For long-term monitoring, use Pixel Monitor to get more detailed trend lines and set pixel error alerts. We recommend that you subscribe to pixel alerts.
Updated 23 days ago