Skip to main content

​
Overview

This destination lets you send customer transaction data from your data warehouse to Bazaarvoice. This enables you to automatically submit transaction data for review and rating collection, helping you gather authentic customer feedback and display reviews on your products.

​
Supported syncing

For more information about sync modes, refer to the sync modes docs.

​
Connect to Bazaarvoice

Go to the Destinations overview page and click the Add destination button. Select Bazaarvoice and click Continue. You need to provide the following credentials:
  • Client ID: Your Bazaarvoice OAuth Client ID. You can obtain this from the Bazaarvoice Developer Portal or from your Bazaarvoice representative.
  • Client Secret: Your Bazaarvoice OAuth Client Secret. You can obtain this from the Bazaarvoice Developer Portal or from your Bazaarvoice representative.
  • API Environment: Select whether to use the Production or Staging environment.

​
Create API credentials

  1. Log in to the Bazaarvoice Developer Portal.
  2. Navigate to your application settings or contact your Bazaarvoice representative to obtain API credentials.
  3. Create or access your OAuth Client ID and Client Secret credentials.
  4. Copy your Client ID and Client Secret.
  5. Ensure your credentials are activated. If you see a “Developer Inactive” error, contact Bazaarvoice support to activate your credentials.

​
Sync configuration

Once you’ve set up your Bazaarvoice destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Bazaarvoice destination you want to sync to.

​
Objects

Hightouch supports syncing to Bazaarvoice transactions with the following sync mode:

​
Configuration

Enter the following field into Hightouch:
  • Client Name: Your Bazaarvoice client instance name (e.g., mycompany-en_us, mycompany-fr_fr). This identifies which Bazaarvoice deployment zone to send transactions to.

​
Field mapping

Hightouch lets you sync transaction fields via field mapping. You can map data from any of your model columns to the Bazaarvoice transaction fields. Bazaarvoice requires the following fields, so you must map them to complete your configuration: Required fields:
  • Transaction ID: A unique identifier for the transaction
  • Email Address: The customer’s email address
  • User ID: A unique identifier for the user
  • Customer Name (nickname): The customer’s display name
  • Locale: The locale code (e.g., en_US, fr_FR)
  • Transaction Date: The date and time of the transaction
  • Deployment Zone: The Bazaarvoice deployment zone identifier
  • Products: An array of product objects. Each product must include:
    • id: Product identifier (required)
    • name: Product name (required)
    • imageUrl: Product image URL (required)
    • money: Object with amount (number) and currency (string)
    • incentivizedReview: Optional string field
Optional fields:
  • Transaction Channel: The channel through which the transaction occurred
Use the inline mapper to structure the products array. The products field requires an array of objects, so you’ll need to use the inline mapper to transform your source data into the required format.

​
Batch processing

Bazaarvoice processes transactions in batches of up to 200 transactions per request. Hightouch automatically batches your transactions to optimize API usage and ensure efficient data transfer.

​
Error handling

The Bazaarvoice API returns a 207 Multi-Status response, which means some transactions in a batch may succeed while others fail. Hightouch automatically handles these partial failures and reports which specific transactions failed, allowing you to troubleshoot individual issues without affecting successful transactions.

​
Tips and troubleshooting

To see the exact API requests and responses from each sync run, use the live debugger. To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up sync alerts. If you run into an issue this page doesn’t cover, .
Last modified on November 17, 2025