If your site uses Ensighten Tag Manager to implement third-party tags such as the Bloomreach's Pixel, we have created this guide to help you implement our Pixel specification.

Bloomreach will provide you a list of Tags and Variables to add to your Ensighten container to help get you started.

It will be your responsibility:

• For each Bloomreach tag, associate the proper triggers needed for the tag specification as provided in the tag's notes section.

• For each Bloomreach variable, configure the variable's type and definition to return data that matches our specification provided in the variable's notes section.

The Step-by-Step Guide below assumes that:

• You already have a Ensighten account and a container published on your website.

• You have edit permissions to the container you wish to implement against.

If you need further help, please see the [main pixel specification](🔗) or consult with your Bloomreach representative.

## Step 1: Configure Bloomreach Tag Triggers

There are 5 different tags to fire from Ensighten for a Bloomreach Pixel implementation.

#### Bloomreach Page View Tag Trigger

This tag needs to fire on every page view, including any AJAX interactions that trigger an additional page view, but not a full page load. An important thing to note here is that getting an accurate page type ( ptype ) classification is a major component and is covered in further details in the **Data** section.

The conditions value is dependent on your site setup; however, example conditions using events have been added. These example events are described in the **Events** section.

🚧



The Page View Tag also needs to fire on any [virtual page views](🔗), such as AJAX interactions that load content outside of the normal page load cycle.

#### **_Page View Tag for Ensighten_**

#### Bloomreach ATC Tag Trigger

Any time a user adds an item to their cart, Bloomreach's Add To Cart Event should fire. Typically this includes the product display page and product listing pages such as category or search pages. If an Add To Cart button is located anywhere else on your site (e.g. Product Collection pages) , please also fire this tag there as well.

**_Add To Cart Tag for Ensighten_**

#### Bloomreach Suggest Tag Trigger

If you have an auto-suggest feature in your search form, when a user clicks on a search suggestion, Bloomreach expects a Search Suggest Event to fire.  If you do not have autosuggest, skip this section.  **_Suggest Tag for Ensighten_**

#### Bloomreach Search Tag Trigger

If a user types\`woven scarf\` and then clicks the search button or hits enter to submit the search, Bloomreach expects a search event pixel to fire that contains information about the search query.  **_Search Tag for Ensighten_**

#### Bloomreach Quick View Tag Trigger

The Quick View event should be fired directly after someone opens a product quick view, commonly found category display pages. However, if you have quick view on other page types as well, this event should be fired.

**_Quickview Tag for Ensighten_**

## Step 2: Configure Bloomreach Events

Creating these events in Ensighten will make firing the appropriate BloomReach pixel easier to work with. Recommendation is to use Named Events and add the appropriate call to Bootstrapper.ensEvent.trigger in your application javascript

### Add To Cart

**_ATC Event for Ensighten_**

### Suggest

**_Suggest Event for Ensighten_**

### Search

**_Search Event for Ensighten_**

### Quick View

**_Quick View Event for Ensighten_**

## Step 3: Configure Bloomreach Variables

It is possible to add these data elements inline in the associated Tag’s javascript; however, it’s recommended to separate them out into their own data elements for easier management and tracking.

Custom example values have been provided; however, if you need assistance please reach out.

**_Bloomreach Data Variables for Ensighten_**

**Account ID**

 **Ptype**

** Product ID**

 **Product Name**

** SKU**

** Category ID**

** Category Name/ Bread crumb**

** Search Term**

** Is Conversion**

 **Order ID**

** Basket Value**

** Basket**

**Additional Information** The key-value data you send us will be transformed into the format below:<br><br>E.g. !ipid123456'ssku789'nCashmere Sweater'q1.0'p69.95!ipid56789'nBlue Skinny Jeans'q1.0'p79.99<br><br>Each product in the cart will be separated by !. Each product's details will be separated by '.<br><br>

• i<prod_id> - This is the product id and not another id such as sku id or collection id. This should match the unique product id sent in the feed.

• s<sku> - Sku id, only applies if you have skus.

• n<product_name>

• q<quantity>

• p<price> - This should be the unit price per product and not total price. If the item is on sale, this is the unit sale price.

 **Search**

 **Suggest**

 **quickview**

** Domain Key (Only required for multiple language versions)**

 **View ID (Only required for multiple site versions)**

**User ID (Only required for tracking users with a universal customer ID)**

**Tms (Only required if you are transitioning from one tag manager to another)**