The Conversations API lets you programmatically retrieve and submit Bazaarvoice Conversations data for use in your applications. To learn more, go to the Conversations API documentation home page.

Bazaarvoice Conversations Mobile SDKs
Developers starting new Mobile apps or who have the resources to update existing apps should use the Bazaarvoice Mobile SDKs available for iOS and Android instead of following the instructions on this page.

This tutorial documents how to use iovation's mobile SDKs and the Bazaarvoice Conversations API to create and submit a device fingerprint from a native mobile application.


(+ show- hide)


Mass advertising campaigns, trolling, and attempts at automated content submission are all sources of inauthentic content. To combat them Bazaarvoice has partnered with iovation, an industry leader in device reputation technology.

iovation offers both an Android SDK as well as an IOS SDK. iovation identifies devices through information collected by an iovation SDKs run on an end-user’s mobile device and generate a blackbox value. This blackbox value is then transmitted to Bazaarvoice and used in a reputation check.

Per the Bazaarvoice Authenticity Policy, you must send a device fingerprint attached to each submission. If you fail to send a device fingerprint with your submission, Bazaarvoice may take any action deemed necessary in Bazaarvoice’s sole discretion to protect the integrity of the network. Such actions may include but are not limited to: rejection of your content, halting syndication of your content on the Bazaarvoice network, revocation of your API key, or revocation of your API license.

Aquiring iovation SDKs

The iovation SDKs for Android and iOS can be downloaded from iovation's Github account at the following URLs:


You should dowload the latest available version.

Installation and usage

The README.html included with each SDK provides detailed installation, configuration and usage instructions.

Submitting device fingerprint to Bazaarvoice

Device fingerprints must be submitted to Bazaarvoice along with the consumer generated content (reviews, questions, etc). The following example demonstrates what the submission would look like as a raw HTTP request to the Bazaarvoice Converstaions API. You should refer to the documentation for your application programming environment to learn how to perform HTTP requests.


Name Description Default Value
fp Value is iovation device fingerprint black box string. N/A

Content types

The fp parameter is available for the following content types.

  • Review
  • Review Comment
  • Question
  • Answer


Submission should be performed using the HTTP POST method with a request body due to the length of the black box string and limitations imposed on query string length by some servers. Additional information on API submission can be found by reading the Submission Fundamentals tutorial.

The following example assumes you are performing the submission from the users device. If you are submitting to your server first and then to Bazaarvoice, then you must also capture the IP address of the user's device. See the Author IP address section of the Authenticity tutorial for more information.

This is a generic example. Your fields and API key will be different.
The following code applies to full submission only. It does not apply to progressive submission.
POST /data/submitreview.json HTTP/1.1
Content-Type: application/x-www-form-urlencoded


Ellipses (…) indicated that your app may generate additional headers.

Encoding the blackbox string

Failure to correctly encode the black box string will result in your content being considered inauthentic.

The black box string contains characters that are reserved for special purposes in a URI. For example, the plus sign (+) is an encoding for the white space character. Because submission is performed using the Content-Type: application/x-www-form-urlencoded header, our appliction will decode the black box string and interprete a plus sign as a white space character.

To correctly submit the black box string, you must ensure that the black box string is itself percent encoded, so that any reserved characters are not misinterpreted. For example, the percent encoding for a plus sign is %2B. When our application encounter that sequence of characters, it will be interpreted as a + character.

The following examples demonstrate unencoded and encoded black box strings:


The black box string depicted in this example should not be submitted to Bazaarvoice because it is not encoded.


Ellipses (…) indicated that the string has been shortened for demonstration purposes.


This black box string is encoded and is safe to submit to Bazaarvoice.


Ellipses (…) indicated that the string has been shortened for demonstration purposes.