HomeEngagementContentDiscoveryOther Resources

This page describes different scenarios in which to use the Bloomreach pixels for proper Content Search integration. These scenarios take into account the following factors:

  • Site Type: Whether the site you wish to power search with is **Single** or **Multi-Site**.

  • Customer: If you are a **New** customer for Content Search or an existing product search customers looking to add content search.

  • Search Solution: If you are using Bloomreach solution to power **Product Search only** or **Product as well as Content Search**.

For merchants with multiple domains and site versions, it also takes into account:

  • Views: Views show selective content to selective users, such as content-based on regions or stores. This can be **Single** or **Multiple**.

  • Domain Keys: A merchant can have **Single** or **Multiple** domains and subdomains for sub-brands or multiple languages.

The examples given below are for **Search Page View** pixel integration in different scenarios:

## Merchants with Single Site Version

Merchants that only display a single version of their site to all customers.

**Site Versions: Single Solution: Product Only Pixel Sample: Search Page View Tracking Pixel** 


**Site Versions: Single
Solution: Product and Content
Scenario 1: When results are in a tabbed format and user is on the product catalog search page** 

**Scenario 2: When results are in a tabbed format and user is on the content catalog search page** 

**Scenario 3: When results for product and content are on the same page** 

## Merchants with multiple domains and versions of their site
Merchants that have either multiple domains or different versions of their site. For example, a site that has a version for English and another version for French.
**Site Versions: Multiple
Solution: Product Only
Views: Single
Domain Keys: Multiple
Scenario 1: When analytics need to distinguish between the two sites (e.g. when moving from an English site to a French site)** 

**Scenario 2: When there are two catalogs used interchangeably and analytics need not distinguish between the two versions:** 

**Site Versions: Multiple
Solution: Product and Content
Views: Single
Domain Keys: Multiple
Scenario 1: When you want analytics to distinguish between the two sites (e.g. when you are moving from an English site to a French site)** 

**Site Versions: Multiple
Solution: Product Only
Views: Multiple
Domain Keys: Single
Scenario 1: Views are used to power separate sites (e.g. each view is used to designate a different site)** 

**Scenario 2: Power different versions of the same site (e.g. a view for logged in users, a view for not logged in users)** 

**Site Versions: Multiple
Solution: Product and Content
Views: Multiple (only product Catalog has views)
Domain Keys: Single
Scenario 1: Views are used to power separate sites (e.g. each view is used to designate a different site)** 

**Scenario 2: Views are used to power different versions of the same site (e.g. a view for logged in users, a view for not logged in users)** 

**Site Versions: Multiple
Solution: Product and Content
Views: Multiple (product and content Catalog both have views)
Domain Keys: Single
Scenario 1: Views are used to power separate sites (e.g. each view is used to designate a different site)**