What are Conversion Page View Pixels

Conversion page view pixels are page view events that track views of conversion pages (e.g., post-purchase Thank you page).

How to Implement Conversion Page View Pixels

• Go to your Conversion/ Thank You Page Template and add basket and Conversion specific Page View parameters in the Global Tracking snippet.
• When your checkout page (or portions of it) is loaded dynamically via AJAX, remember to add additional handlers for single page application tracking.

Conversion Page View Variables Checklist

The following lists the tracking variables required specifically for conversion page view pixels. Please note that these must be included in addition to the Global Page View variables.

Basket Object

Each basket object contains an items array, which contains product objects with the following variables:

Basket Product ID and SKU ID Scenarios

You have to enter certain values for the prod_ID and sku, depending on what products are in the basket. Create a product object for each product ID (and SKU, if your site has SKUs) in the basket.

{
  "items": [
    {
      "prod_id": "pid123456",
      "sku": "sku789",
      "name": "Cashmere Sweater",
      "quantity": "1",
      "price": "65.95"
    },
    {
      "prod_id": "pid56789",
      "sku": "",
      "name": "Blue Skinny Jeans",
      "quantity": "2",
      "price": "79.99"
    }
  ]
}

{
  "items": [
    {
      "prod_id": "pid123456",
      "sku": "sku789",
      "name": "Cashmere Sweater White",
      "quantity": "2",
      "price": "120.00"
    },
    {
      "prod_id": "pid123456",
      "sku": "sku790",
      "name": "Cashmere Sweater Blue",
      "quantity": "1",
      "price": "60.00"
    },
    {
      "prod_id": "pid56789",
      "sku": "",
      "name": "Blue Skinny Jeans",
      "quantity": "2",
      "price": "79.99"
    }
  ]
}   
      

{
  "items": [
    {
      "prod_id": "collection223344",
      "sku": "",
      "name": "Linen Bed Sheet Set",
      "quantity": "1",
      "price": "265.95"
    },
    {
      "prod_id": "pid56789",
      "sku": "",
      "name": "Blue Skinny Jeans",
      "quantity": "2",
      "price": "79.99"
    }
  ]   
  

{
  "items": [
    {
      "prod_id": "pid1111",
      "sku": "",
      "name": "Linen Pillow",
      "quantity": "1",
      "price": "35.95"
    },
    {
      "prod_id": "pid2222",
      "sku": "",
      "name": "Linen Comforter",
      "quantity": "1",
      "price": "230.00"
    },
    {
      "prod_id": "pid56789",
      "sku": "",
      "name": "Blue Skinny Jeans",
      "quantity": "2",
      "price": "79.99"
    }
  ]
}
    

Additional Basket Information

Additional Basket Information for native implementation

The key-value data you send us in the basket will be transformed into the format below in the executed pixel (pix.gif) file:

E.g. !ipid123456'ssku789'nCashmere Sweater'q1.0'p69.95!ipid56789'nBlue Skinny Jeans'q1.0'p79.99

Each product in the cart will be separated by !.

Each product's details will be separated by '.

1. i - 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.
2. s - Sku id, only applies if you have skus.
3. n - product_name.
4. q - quantity of the product in the basket.
5. p - This should be the unit price per product and not the total price. If the item is on sale, this is the unit sale price.

Do not percent encode the ! separators

📘

For a full list of required and optional variables, see Pixel Reference

Implementing Pixel in a Test Environment

If you are implementing the Pixel in a test environment (development, staging, UAT, etc.), you must add the test_data variable. When set to “true”, this flags pixel data to be ignored during analytics processing. Read more about the test_data variable here.

Tracking Snippets for Search Result Page View Pixels

The following are customized tracking snippets for both JavaScript and Non-JS environments. Here ptype is set to “conversion” and is_conversion=”1” for the conversion page view pixel.

JavaScript Implementation

<script type="text/javascript">
  var br_data = br_data || {};
  // Global tracking parameters
  br_data.acct_id = "<Bloomreach Provided Account ID>"; 
  br_data.ptype = "conversion";
  br_data.title = "<title of current page>";
  br_data.domain_key = "";
  br_data.user_id = "";
  br_data.view_id = "";
  br_data.debug = true; // remove for production
  br_data.test_data = true; // remove for production


 
  // INSERT the Conversion & Basket specific Tracking Parameters in your Global Tracking Script
  // in your CONVERSION/ THANK YOU PAGE TEMPLATE. 
   br_data.is_conversion = 1;
   br_data.basket_value = "445.93";
   br_data.order_id = "12123455";
   br_data.basket =
   { "items":
    [
    {
      "prod_id" : "pid1111",
      "sku": "sku1234",
      "name": "Linen Pillow",
      "quantity": "1",
      "price": "35.95"
    },
    {
      "prod_id" : "pid2222",
      "sku": "",
      "name": "Linen Comforter",
      "quantity": "1",
      "price": "230.00"
    }, 
    {
      "prod_id" : "pid56789",
      "sku": "",
      "name": "Blue Skinny Jeans",
      "quantity": "2",
      "price": "79.99"
    }
   ]
  };
 ;
  // End - Conversion page specific tracking parameters
 
  (function() {
  var BrTrk = document.createElement('script');
  BrTrk.type = 'text/javascript';
  BrTrk.async = true;
  BrTrk.src = "//cdn.brcdn.com/v1/br-trk-{{BloomReach Account ID}}.js";
  var s = document.getElementsByTagName('script')[0];
  s.parentNode.insertBefore(BrTrk, s);
  })();
</script>

👍

Copying Snippet from Events diagnostics

You can copy the personalized tracking snippet from the Event diagnostics application. We recommend using personalized snippets instead of copying from the documentation page. Currently, only acct_id and debug values are populated in the snippet. In future feature iterations, we will add domain_key, view_id, and other variables to further personalize the snippet for easy click-copy use.

Non-JavaScript Implementation

To integrate Bloomreach Pixels in a Non-JS Environment, you can choose one of the following options:

• Android SDK
• iOS SDK
• Direct API Requests

https://p.brsrvr.com/pix.gif?
acct_id=6702
&cookie2=uid%3D1e7724c751a3f6e6241018d150144832e7528383%3Av%3Dapp%3Ats%3D0%3Ahc%3D1
&rand=86838131966165760
&type=pageview
&title=Conversion
&url=http%3A%2F%2Fmerchantname.app%2Fconversion
&ref=http%3A%2F%2Fmerchantname.app%2Fcategory%2Fdresses
&ptype=conversion
&is_conversion=1
&basket_value=30.00
&order_id=88332121
&basket=!i1234%27s563%27nBlue%20Lace%20Dress%27q2%27p10.00!i7892%27s121%27nRed%20Lace%20Dress%27q1%27p10.00

Validate Pixel Implementation

If you’re integrating the Pixel, you can start tracking the test pixel data using Event diagnostics. It gives you a broad overview of your pixel’s health in an instant. You can continue using this when you go live.

🚧

Integration mode in Events diagnostics

If you wish to inspect individual events from your test environment in real time, add debug=true. Such events will be treated as test data and will show in the Integration mode of Events diagnostics within seconds. Otherwise, you can inspect events in the Live mode with a delay of up to 2 hours.

For web validation

Once Pixel implementation is complete, use the Pixel Validator Chrome Plug-in to validate if the Product Page View Pixel is working as expected. Follow the scenarios listed in the Test Scenarios - Page View guide.

Troubleshooting

Refer to the following help articles to troubleshoot issues related to the Conversion Page View Pixel

• Missing or Empty Conversion Basket
• Total basket price inconsistent with basket_value parameters
• Non-unit pricing for basket item price parameters
• Missing or Invalid Quantity
• Missing or Invalid Revenue Value
• Missing or Empty Product ID Field

Monitor and Manage Pixel Data

For long-term monitoring, use Event alerts to get more detailed trend lines and set pixel error alerts. We recommend that you subscribe to Pixel alerts.