Use BV Pixel to capture product purchases as well as non-transactional events, such as Store Locator or Where To Buy clicks. It can also be used to opt a user out of BV tracking.

BV Pixel is key to measuring the business impact of your consumer-generated content (CGC). Watch this video to learn why.

BV Pixel is implemented using JavaScript, and it is similar to other analytics-tracking services from Google Analytics or Omniture. You must implement BV Pixel on the following pages:

  • For product purchases, also referred to as "transaction" events, implement BV Pixel on all confirmation pages on your web site
  • For non-transaction events, also referred to as "conversion" events, implement BV Pixel on pages where the events will occur

After you implement BV Pixel, you can

  • Generate valuable insights into your consumer-generated content (CGC) program.
  • Discover key information about the impact of Bazaarvoice content on your online business.
  • Use Bazaarvoice features to increase the volume of CGC.
  • Generate return-on-investment (ROI) reports related to key performance indicators.
  • Evaluate return-on-ad spend (ROAS).
  • Use data collected about consumers along with CGC to target the right shoppers at the right time.
Note: If you have an existing BV Pixel implementation that uses the scout file (bvapi.js), refer to the BV Pixel v1 documentation instead of the topics linked from here. However, Bazaarvoice encourages you to migrate to v2 (using the BV loader file, bv.js) for performance improvements and future innovations.

Events captured by BV Pixel

The following event types are captured by BV Pixel:

  • Transactions—Product purchases. These events are captured if you implement BV Pixel on the confirmation page.
  • Conversions—Non-transactional events, such as clicks on a Store Locator or Where to Buy link, newsletter signups, product registration, or PDF downloads. These events are captured if implement BV Pixel on pages where the conversion events occur.
  • Page views—Page loads for web pages that contain Bazaarvoice code. These events are automatically captured when you set up your Conversations display code.
  • Impressions—Instances of Bazaarvoice content that are served to a device and loaded on the page. For example, a consumer viewing a review is an impression. Impressions include interactions with content hidden by code, such as on tabs and accordions. These events are automatically captured when you set up your Conversations display code.
  • Features events—Content views and interactions, including the following:
    • InView events, which indicate that content is visible on the page. This event is triggered only once per page load.
    • ViewedUGC events, which are triggered if Bazaarvoice content is visible on the page for at least five seconds. This event is triggered only once per page load.
    • Used events, which indicate user interactions with Bazaarvoice content and are used for clicked features such as Filter, Sort, and Paginate. This event is triggered only once per page load.

    Feature events are automatically captured when you set up your Conversations display code.

Steps to implement BV Pixel

For eCommerce sites, perform these steps:

  1. Add the BV loader.
  2. Add the transaction event.
  3. To send post-interaction email messages (optional), add PII parameters to the transaction event.
  4. Add the conversion event (optional).
  5. Test the implementation.

For non-eCommerce sites, perform these steps:

  1. Add the BV loader.
  2. Add the conversion event.
  3. To send post-interaction email messages (optional):
    1. Add the transaction event.
    2. Add PII parameters.
  4. Test the implementation.

For PRR clients, perform these steps:

  1. Confirm with your Bazaarvoice team that your Bazaarvoice instance is configured to take advantage of BV Pixel v2.
  2. Publish your implementation to Staging and Production by following these instructions:
    1. From the Workbench of the staging server , select Settings » Manage Applications to display the Site Manager page of the Conversations configuration hub.
    2. Click Deploy next to the implementation that is deployed to STAGING, verify that Environment:Staging is selected, and then click Next.
    3. Click Deploy next to the implementation that is deployed to PRODUCTION, verify that Environment:Production is selected, and then click Next.
  3. Follow the For eCommerce sites or For non-eCommerce sites instructions provided above this procedure, depending on your site.
Note: If your implementation uses an API, implement BV Pixel with the rest of the Bazaarvoice analytics events as described in the API Analytics documentation . If you have a native app, you can use the Mobile SDK.

Add the BV loader

To enable BV Pixel, you must add the BV loader to every web page where you intend to collect events. The BV loader loads the Bazaarvoice JavaScript library, which is required to track the activities on your website. After the BV loader is installed, you can define the transaction events (captures purchase data when a customer buys a product. This event tag captures information about the order, such as the purchaser's email address, and data about the items in the order, such as SKUs. You can generate return-on-investment (ROI) reports tied to revenue using transaction event data) and conversion events (captures events that are non-transactional, such as newsletter signups, product registration, downloads of a PDF, and requests for more information about a product or service. You can generate ROI reports related to key performance indicators) for data that should be collected.

Note: You must implement BV Pixel on a whitelisted domain. Bazaarvoice manages the domain whitelist internally. If you are in the implementation stage of a project, contact your Bazaarvoice implementation team to request changes to the whitelist. If you are in the support stage, contact Bazaarvoice Client Care to request changes.

To add the BV loader to a web page, edit the page and add the following code:

<!-- load BV loader -->
<script async src="https://apps.bazaarvoice.com/deployments/<client_name>/<site_ID>/<environment>/<locale>/bv.js"></script>

where:

  • <client_name>— The client name provided by Bazaarvoice. Be sure to use lowercase letters for the value.
  • <site_ID>—The ID of the deployment zone you want to use. This is set in the Bazaarvoice configuration hub within the Bazaarvoice Workbench. The default deployment zone is “main_site”. Check with your Bazaarvoice representative to ensure the correct ID, or click to the right of the deployment zone on the Site Manager page of the configuration hub.
  • <environment>—The deployment environment where you want to implement BV Pixel. For a production environment, include production in the path. If you are referencing a staging environment, include staging in the path.
  • <locale>—The locale used by the BV Pixel implementation. If you are not using US English (en_US), use the correct locale code.

Here is an example URL for Endurance Cycle's staging environment of the Main Site deployment zone:

https://apps.bazaarvoice.com/deployments/endurancecycles/main_site/staging/en_US/bv.js

Here is an example URL for Endurance Cycle's production environment of the implementation. The deployment zone (site ID) is named "mobile":

https://apps.bazaarvoice.com/deployments/endurancecycles/mobile/production/en_US/bv.js

Add the transaction event

After you install the BV loader, you can add the transaction event, which captures purchase data when a customer buys a product. A purchase comprises an order and the items purchased in the order. The transaction event is required on eCommerce sites. Typically, the transaction event is added to a confirmation page, such as a thank you page or payment confirmation page.

Note: You can send email messages to consumers to request reviews or answers to product questions by adding personally identifiable information (PII) parameters to the transaction event. See Step 3 below for details.

To add a transaction event, complete these steps:

Step 1: Add the transaction event to the confirmation page

Edit the confirmation page and add the transaction event and its required parameters below the BV loader, as shown in the following code example.

<!-- load bv.js -->
<script async src="https://apps.bazaarvoice.com/deployments/<client_name>/<site_ID>/<environment>/<locale>/bv.js"></script>

<!--load Transaction event and parameters-->
<script>
window.bvCallback = function (BV) {
  BV.pixel.trackTransaction({
    "currency" : "value",
    "orderId" : "value",
    "total" : "value",
    "items" : [
      {
        "price" : "value",
        "quantity" : "value",
        "sku" : "value",
        "optional_item_parameter" : "value"
      },
      ...
    ],
    "optional_order_parameter" : "value",
    ...
    "optional_PII_parameter" : "value",
    ...
  });
};
</script>
Note: Parameter names are case sensitive and must be specified as shown.

Required order parameters

Parameter Description Example value
currency

The ISO 4217 alphabetic currency code of the order.

Impact:

  • Conversion Impact report (CIR)—For multi-locale clients, currency is needed to break out revenue (each currency is its own row).

    Note: If currency is not included, USD is used in the Conversion Impact report.
  • Return on ad spend (ROAS)—Required to calculate total sales consistently across the network.

  • Can be used in maintenance-free post-interaction (PIE) messages.
CHF
orderId

The unique ID of an order generated by a site.

Impact: 

  • This parameter is required to distinguish unique counts of orders.
  • Order ID is an important factor in measuring ROI.
55555
total

Total amount of the product order (all items) including discounts and coupons applied but excluding tax and shipping. Specify the value for total in the English format (two decimal places) and do not include the currency symbol (such as $ for USD).

Impact:

  • Conversion Impact report (CIR)—Affects revenue.

  • Return on ad spend (ROAS)—Required to calculate total sales consistently across the network.

  • Order total is an important factor in measuring ROI.
178.07
items An array of the individual items in the transaction. See item parameters below.  

Required item parameters

All of the following item parameters are important factors in measuring ROI.

Parameter Description Example
price

Individual price of the item, not price X quantity.

Specify the value for price in the English format (two decimal places) and do not include the currency symbol (such as $ for USD).

12.95
quantity The number of items that are being purchased. 3
sku

The product ID, which must match the product <ExternalId> in your Bazaarvoice product feed. Do not set this to standard SKU unless that is the number that is sent in your product feed.

908736

Step 2: Add optional order and item parameters to the event

Note: If you do not need an optional parameter, do not include it in the event. For example, if the tax parameter has no data, do not set add "tax" : "" (an empty string). Instead, omit the parameter. Remember that parameter names and values are case sensitive.

Optional order and item parameters

Parameter Description Example
name

The name of the item.

Serena Boots
category

Item parameter that captures the product category used on the site. This parameter is recommended.

Impact: This is an important factor in measuring ROI by category.

Mens casual boots
shipping

Order parameter that captures the cost of shipping the order. Specify the value for shipping in the English format (two decimal places) and do not include the currency symbol (such as $ for USD). This parameter is recommended.

Impact: Used to ensure the total is correct to understand true product order cost.

10.00
tax

Order parameter that captures the amount of tax applied to the order Specify the value for tax in the English format (two decimal places) and do not include the currency symbol (such as $ for USD). This parameter is recommended.

Impact: Used to ensure the total is correct to understand true product order cost.

11.44
city

Order parameter that captures the end user specifying the order’s city.

Detroit
state

Order parameter that captures the end user specifying the order’s state.

Utah
country

Order parameter that captures the end user specifying the order’s country.

Canada
deploymentZone Order parameter that specifies the ID of the deployment zone to which the implementation is deployed. Specify this parameter if multiple deployment zones are used. This instructs Bazaarvoice to use the implementation's email templates when sending PIE messages. The implementation where the templates are configured must be published to the deployment zone before you reference the deployment zone in the PIE feed. If you omit this parameter, the deployment zone specified by <environment> in the BV loader's path is used. secondary_site

Step 3: Add optional PII parameters to the event

If you add personally identifiable information (PII—Personally identifiable information, which comprises data that is personal and often private to consumers. PII could potentially identify a specific individual or distinguish one person from another(de-anonymizing)) parameters to the transaction event, you can perform the following tasks:

  • Send personaized email messages to consumers to request reviews if Post-Interaction Email (PIE) is enabled
  • Request answers to product questions if Ask a Product Owner is enabled
  • Send consumers additional notifications about their reviews or questions

Refer to Add PII parameters to events for more information.

Add the conversion event

After you install the BV loader, you can add the conversion event, which captures events that are non-transactional, such as Store Locator or Where to Buy clicks, newsletter signups, product registration, or PDF downloads. This event is required on non-eCommerce sites, such as brand websites, and it is optional on eCommerce sites. It can be added to any page where an event can occur. With this event, you can generate ROI reports related to key performance indicators.

Note: Data captured by the conversion event cannot be used in post-interaction email (PIE) messages. To send PIE messages, use the transaction event.

To add the conversion event, complete these steps:

Step 1: Add the conversion event

Add the conversion event and its parameters to the page below the BV loader, as shown in the following example code.

<!-- load BV loader -->
<script async type="text/javascript" src="https://apps.bazaarvoice.com/deployments/<client_name>/<site_ID>/<environment>/<locale>/bv.js"></script>

<!--load Conversion event and parameters-->
<script>
window.bvCallback = function (BV) {
BV.pixel.trackConversion({
  "type" : "value",
  "label" : "value",
  "value" : "value"
});
};
</script>
Note: Parameter names are case sensitive and must be specified as shown.

Parameters

Parameter Description Example
type

Type of conversion that is taking place. Refer to the Recommended Values table below to define the values of this parameter.

This parameter is required.

Impact: Creates conversion events that are measured in the Conversion Impact report, which are shown in the Non-Commerce Goals section of the report after two to three days.

StoreLocator
value Value attributed to the conversion.

This parameter is optional.

55781
label Descriptive label to apply to the conversion.

This parameter is optional.

ProductPage

Recommended values for the type parameter

Bazaarvoice can support any value for the type parameter, but the following list provides recommended values for specified conversion types. If you see a permutation that better matches your needs, use it as the value for label to make it more specific to your site.

Type Value Description
StoreLocator

Enables the consumer to locate a store or determine where to purchase products offline.

Permutations: DealerLocator, FindStore

WhereToBuy Indicates where to buy products (online or in store).
BuyNow

Enables the consumer to purchase now.

Permutations: BuyOnline, ClickToBuy

Download Enables the consumer to download various documents like owners manual, etc.
Compare Enables the consumer to compare two or more products.
ProductDetail   Provides additional product details.
AddToCart Adds a product to a cart.
ContactUs Provides contact information such as a phone number, email address, or physical address.
Coupon

Provides a coupon or promotional code for a product.

Permutations: promo, promotion

Quote Enables a consumer to request a price quote.

Step 2: Add optional PII parameters to the event

You can add personally identifiable information (PII) parameters to the conversion event to collect information about the consumer. Refer to Add PII parameters to events for more information.

Note: Conversion events do not trigger post-interaction email (PIE) messages or other automated messages. To do so, add the transaction event.

Add PII parameters to events

You can add personally identifiable information (PII) parameters to the BV Pixel transaction and conversion events. However, only the transaction event sends automated email messages. By adding PII parameters, you can perform the following tasks:

  • Send personalized email messages to consumers to request reviews if Post-Interaction Email (PIE) is enabled.
  • Request answers to product questions if Ask a Product Owner is enabled.
  • Send consumers additional notifications about their reviews or questions.
Note: Be aware that PII is never associated with the Bazaarvoice persistent cookie, and it is always transmitted over HTTPS. PII is encrypted before writing to disk and stored separately from non-PII data. It is never processed by Bazaarvoice analytics.

If you add PII parameters to an event, you must add the required parameters. You can also add optional parameters based on your needs.

Required parameters

Some parameters are required if you are using a specific Conversations feature, such as site authentication. This information is noted in the table when necessary.

Note: All parameters are case sensitive and must be formatted correctly. For example, "userId" should not be "UserID".
Parameter Description Example
email

The customer's email address.

username@example.com
locale

The locale to use to determine the language-specific email template to use. Refer to Supported locales and languages for the list of supported values.

This parameter is required if you are sending unique templates for multiple locales.

fr_CA
nickname

The customer's first name or nickname, captured when the customer creates an account. Used to personalize the email greeting.

This parameter is required if your site is injecting a nickname. Otherwise, it is recommended.

MaryO
userId

The customer's user ID, which must match the userToken (user ID) that is sent to Conversations during the review submission process.

This parameter is required if you are using site authentication. It can be omitted if an ID is not created, such as in the case of guest purchasers.

Note: If you are using Conversations PRR, ensure your PIE configuration worksheet reflects this parameter value accurately.
7448dc2

Optional parameters

If you are providing PII parameters in a transaction event, you can specify parameters for the order or item. If you are providing PII parameters in a conversion event, only order-level parameters are available.

Note: If you do not need an optional parameter, do not include it in the event. For example, if the orderID parameter has no data, do not set add "orderID" : "" (an empty string). Instead, omit the parameter. Remember that parameter names and values are case sensitive.

Order parameters

Parameter Description Example
shippingDate

Used instead of the transaction date to determine when Bazaarvoice sends the post-interaction email (PIE) message. The date must be in the following format: YYYY-MM-DD.

If a first PIE delay is configured, that delay is added to the date specified here. For example, if you specify "shippingDate" : "2016-12-21" and the PIE delay is set to 10 days, the PIE message is sent on Dec 31, 2016 (2016-12-31).

You can use shippingDate or shippingDelay, but do not use both.

2016-12-21
shippingDelay

Used to increase the time (in days) between the transaction date and the date Bazaarvoice sends the PIE message. This can be useful if you expect delayed fulfillment.

This delay is added to the first PIE delay. For example, if the PIE delay is set to 10 days and you specify "shippingDelay" : "10", the PIE message is sent on May 25 if the transaction date is May 5.

You can use either shippingDelay or shippingDate, but do not use both.

25

Item parameters

Parameter Description Example
imageURL

The full, absolute URL to the product image (not a relative path). If omitted, Bazaarvoice will retrieve the value from our database by matching the sku parameter to the product <ExternalId> sent in your product feed.

This parameter is useful if you want to use a specific image. For example, if your product feed includes a picture of a white shirt but a blue shirt is purchased, the email message can display the blue shirt.

http://www.test.com/1.jpg
shippingDate

Used instead of the transaction date to determine when Bazaarvoice sends the post-interaction email (PIE) message. The date must be in the following format: YYYY-MM-DD.

If a first PIE delay is configured, that delay is added to the date specified here. For example, if you specify "shippingDate" : "2016-12-21" and the PIE delay is set to 10 days, the PIE message is sent on Dec 31, 2016 (2016-12-31).

You can use shippingDate or shippingDelay, but do not use both. Also, if shippingDate is specified as an item parameter, it overrides the value of shippingDate that is specified in the order parameter.

2016-12-21
shippingDelay

Used to increase the time (in days) between the transaction date and the date Bazaarvoice sends the PIE message. This can be useful if you expect delayed fulfillment.

This delay is added to the first PIE delay. For example, if the PIE delay is set to 10 days and you specify "shippingDelay" : "10", the PIE message is sent on May 25 if the transaction date is May 5.

You can use either shippingDelay or shippingDate, but do not use both. Also, if shippingDelay is specified as an item parameter, it overrides the value of shippingDelay that is specified in the order parameter.

25

Add an opt-out function

If a user does not want their personal data and events tracked by BV Pixel, you can invoke the doNotTrack() function, which will stop Bazaarvoice from tracking a user across your domain.

Stopping tracking for an individual user is as simple as calling the following function:

BV.pixel.doNotTrack();

For example, you can create on a button on your site that a user clicks to state that they do not want to be tracked:

// Example of logic where you might have a "BV opt-out" button.
<script src="bv.js"></script>
<script>
// Usage of the "BV" global *must* be wrapped inside bvCallback to ensure
// it is present when called.
window.bvCallback = function () {
  // Create a button.
  var button = document.createElement(button);
  // Add an onClick function
  button.onClick = function () {
    // Invoke the "doNotTrack" function, which will stop BV from tracking
    // this user across your domain.
    BV.pixel.doNotTrack();
  }
  // Append button.
  body.appendChild(button);
}
</script>

As in the above example, the BV global is only accessible after the BV loader has loaded. As always, to ensure you have access to the doNotTrack() function, redeploy your implementation to update the BV loader.

For more detailed information, see the doNotTrack() implementation documentation in the Bazaarvoice Developer portal.

Note: doNotTrack() only opts the user out of personal data collection on your domain, per browser. For example, if your site uses mydomain.com and has a redirect to otherdomain.com, you must call doNotTrack() again for each domain.

See our Privacy Policy for more on how users can opt out of sending their analytics and tracking data across the Bazaarvoice Network.

Test your BV Pixel implementation

You can test BV Pixel using a Google Chrome browser.

Test in the web browser

The Bazaarvoice Analytics Inspector extension for Google Chrome displays messages that are valuable for debugging. They show events that are executed and data that events might be missing.

To use the extension for testing, complete these steps:

  1. Add the Bazaarvoice Analytics Inspector extension to Chrome.
  2. View Bazaarvoice content on your company's website.
  3. Click in the browser menu to display the Analytics Inspector.

Transaction event

To test a transaction event, go through the process of a transaction and land on the confirmation page. You can use a fake product or dummy credit card number to place an order and get to the confirmation page. After the confirmation page is displayed, information similar to the following is displayed in the extension.

To view details, click Conversion under Event Counts. The type is "Transaction."

  • One order parameter is listed in each row. Verify that all required parameters are listed.
  • Item parameters are listed in the items row. Verify that all required parameters are listed.

Conversion event

To test a conversion event, click the event on the web page that corresponds to the conversion event that was added to the code, and then watch for the event to occur. Click Conversion under Event Counts in the analyzer to display details. The type is "Conversion".

PDP page

To test the various product display page (PDP) events, go to any PDP with Bazaarvoice, load the page, which causes the PageView event to occur. Click PageView under Event Counts to see details.

Note: A Feature event occurs for each of your Bazaarvoice products.
  • When you scroll down to Bazaarvoice content on the page, an InView event should fire. Click Feature under Event Counts to see details.
  • If the Bazaarvoice content is displayed in view for at least five seconds, a ViewedUGC event should fire. Click on Feature under Event Counts to see details.
  • When you interact with Bazaarvoice content, a UsedFeature event should fire. Click on Feature under Event Counts to see more details.

In the following example, the InView count is 2 because the user scrolled down to Ratings and Reviews and Questions and Answers on the page. The ViewedUGC event count is 2 because the user viewed the Bazaarvoice content on that page for at least five seconds. Lastly. the user interacted with the content, so additional events were captured—the user clicked to ask a question (Ask), clicked to write a review (Write), closed the submission form (Close), and used a filter (Filter).

FAQs

The following frequently asked questions can help you understand the security and performance impact of BV Pixel.

For eCommerce sites, perform these steps:

  1. Add the BV loader by inserting this code into the page:
    <!-- load BV loader -->
    <script async type="text/javascript" src="https://apps.bazaarvoice.com/deployments/<client_name>/<site_ID>/<environment>/<locale>/bv.js"></script>
    
  2. Add the transaction event to the confirmation page:
    <!-- load bv.js -->
    <script async type="text/javascript" src="https://apps.bazaarvoice.com/deployments/<client_name>/<site_ID>/<environment>/<locale>/bv.js"></script>
    
    <!--load Transaction event and parameters-->
    <script type="text/javascript">
    window.bvCallback = function (BV) {
    BV.pixel.trackTransaction({
      "currency" : "value",
      "orderId" : "value",
      "total" : "value",
      "items" : [
        {
          "name" : "value",
          "price" : "value",
          "quantity" : "value",
          "sku" : "value",
          "optional_item_parameter" : "value"
        },
        ...
      ],
      "optional_order_parameter" : "value",
      ...
      "optional_PII_parameter" : "value",
      ...
    });
    };
    </script>
  3. Add the conversion event (optional):
    <!-- load BV loader -->
    <script async type="text/javascript" src="https://apps.bazaarvoice.com/deployments/<client_name>/<site_ID>/<environment>/<locale>/bv.js"></script>
    
    <!--load Conversion event and parameters-->
    <script type="text/javascript">
    window.bvCallback = function (BV) {
    BV.pixel.trackConversion({
      "type" : "value",
      "label" : "value",
      "value" : "value"
    });
    };
    </script>
  4. Test the implementation by using the Bazaarvoice Analytics Inspector extension for Google Chrome. View Bazaarvoice content on your company's website and click in the browser menu to display the Analytics Inspector.

For non-eCommerce sites, perform these steps:

  1. Add the BV loader by inserting this code into the page:
    <!-- load BV loader -->
    <script async type="text/javascript" src="https://apps.bazaarvoice.com/deployments/<client_name>/<site_ID>/<environment>/<locale>/bv.js"></script>
    
  2. Add the conversion event (optional):
    <!-- load BV loader -->
    <script async type="text/javascript" src="https://apps.bazaarvoice.com/deployments/<client_name>/<site_ID>/<environment>/<locale>/bv.js"></script>
    
    <!--load Conversion event and parameters-->
    <script type="text/javascript">
    window.bvCallback = function (BV) {
    BV.pixel.trackConversion({
      "type" : "value",
      "label" : "value",
      "value" : "value"
    });
    };
    </script>
  3. To send post-interaction email messages (optional), add the transaction event with PII parameters:
    <!-- load bv.js -->
    <script async type="text/javascript" src="https://apps.bazaarvoice.com/deployments/<client_name>/<site_ID>/<environment>/<locale>/bv.js">
    </script>
    
    <!--load Transaction event and parameters-->
    <script type="text/javascript">
    window.bvCallback = function (BV) {
    BV.pixel.trackTransaction({
      "currency" : "value",
      "orderId" : "value",
      "total" : "value",
      "items" : [
        {
          "name" : "value",
          "price" : "value",
          "quantity" : "value",
          "sku" : "value",   //(ExternalId in product catalog and productID on PDPs)
          "imageURL" :  "value",
          "optional_item_parameter" : "value"
          ...
        },
        ...
      ],
      "optional_order_parameter" : "value",
      ...
      "email" : "value",
      "locale" : "value",
      "nickname" : "value"
      ...
    });
    };
    </script>
  4. Test the implementation by using the Bazaarvoice Analytics Inspector extension for Google Chrome. View Bazaarvoice content on your company's website and click in the browser menu to display the Analytics Inspector.
Note: If your implementation uses an API, implement BV Pixel with the rest of the Bazaarvoice analytics events as described in the API Analytics documentation . If you have a native app, you can use the Mobile SDK.

Then, use the Bazaarvoice Analytics Inspector extension for Google Chrome to test your BV Pixel implementation:

  1. Add the Bazaarvoice Analytics Inspector extension to Chrome.
  2. View Bazaarvoice content on your company's website.
  3. Click in the browser menu to display the Analytics Inspector. For details, see Test your BV Pixel implementation.