Pixel Overview

This guide contains all you need to know about Bloomreach Pixels and getting started with Pixel integration on your site/application.

What is a Pixel?

A Bloomreach Pixel is a piece of tracking code that you must add to your site/application’s pages to capture and send necessary tracking data to Bloomreach.

The Pixels track your users’ behavior with your online touchpoints - Navigation and Interactions.

  • Navigation tracking usually captures page views on your website or screen changes on your mobile app.
  • Interaction tracking captures the user's actions in those locations, such as clicks on buttons.

All of this serves as vital behavioral learning data for Bloomreach's algorithm. Over a period of time, data captured by the different pixels amounts to a powerful, intuitive search solution.

How do Pixels work?

The Bloomreach Pixels added to your site load along with the rest of your site’s code. When a customer visits your site, the pixels pick up activities as events and send them to Bloomreach.

Why are Pixels needed?

Pixels are an important part of your integration because of the following reasons:

  • Bloomreach uses the information captured by the Pixels to learn about your site and your customers to dynamically optimize Bloomreach features such as personalizing user experience.
  • It is the primary component to generate site analytics (Insights) that give you visibility into how customers use your site (and track conversions) so that you can make informed, strategic decisions to grow your business.

Which Bloomreach Pixels are needed?

By default, all Bloomreach integrations will need the Core Bloomreach Pixels. Additionally, there are different Bloomreach Pixels for optimizing different features. You will need different Pixels based on the Bloomreach solution that you are integrating.

Core Pixels

The Core Pixels for Bloomreach consist of the following types based on interactions:

  • Page View Pixels for tracking user navigation, such as views on a Product Details page, Category listing page, Content page, Search results page, or Conversion page.
  • Event Pixels for tracking user interactions such as Add-to-cart (ATC), Search, Suggest, and Quickview events.

Feature Pixels

Based on the features that you are integrating, you will need additional Pixels other than the Core Pixels.

The feature-specific pixels available are:

The table below gives you a quick overview of the Pixels you will need for your integration based on the features:

Bloomreach SolutionCore PixelsFeature Pixels
SearchN/A
Organic Search (brSEO)SEO tracking is captured by defining the ptype and sid variables. Learn more here.
Recommendations and PathwaysThe Recommendations and Pathways tracking is captured via the Widget Pixels.
Relevance by SegmentThis feature-specific Pixel is additive, so you will need only to add a few additional Pixel variables.
The Relevance by Segment feature is tracked via the segment name that you choose to pass additionally. Read more here.

What´s next?