Uploading your old Product Reviews to ResellerRatings
So you've already been collecting Product Reviews?
Perhaps your team can't keep up with the demands of modern syndication channels and feed management. Or maybe you want a modern product review solution that does more than your in-house solution.
- ResellerRatings only syndicates unique content generated by our platform to our channel partners like Google and Bing.
You may want to import Product Reviews if
- You want to switch product review vendors
- You've outgrown your in-house solution
- You want us to take care of feed management
If you've collect product reviews and imagery, and you don't want to lose the conversion power of your current content, you can import it into our system.
You might have a series of review content on an older or current review management platform. To migrate to the ResellerRatings Product Reviews platform you can consolidate all your old content, and syndicate proper content to Google if we have the correct data.
Send the file to an Account Manager and we’ll handle the rest of the details. Please ensure the order of the columns, otherwise it will cause issues with actual import process. The account manager will let you know when the import is done
- You don’t have to lose what you’ve collected before
- Consolidate disparate systems into one future proof system
What you can import from your old collection
- product reviews for individual products
- custom attributes
- custom questions
- past catalogue
How to do it
Please contact your account specialist and they will assist you. Imports can only be done by a ResellerRatings account specialist. They will instruct you on how to set up your CSV's.
Uploading data is straightforward, however it does require your team to put together a custom csv of a series of data points for our team to absorb in. You can can an RR administrator to upload this data into our system. The upload system is intended to be an initial one-time use and is considered to be a replacement for your current Product Review Solution.
Setting up your CSV and Required Data fields
to download an example csv go here.
There are a series of data fields that are required for your review system to come into sync with our data needs.
product_name - This name of the Product in string format. For example ‘Canon 5d Mark II’ or ‘Rachel Roy Red sweater’
sku - A unique product identifier
url - The product page that goes to the product itself
rating - Overall rating out of 5. Integer value 1 to 5
review_text - The review text body. String value
review _date - The date the review was submitted in your system. Format as follows (Y-m-d H:i:s) or (2016-12-1 17:50:22)
Review_email - The email address of the reviewer. We use this value to ensure it is an authenticated review
reviewer_name - Username of the reviewer
Optional Data fields
Optional fields are not required, but very important for future proofing content, syndication of content for publishers into Paid Ads and more. We always recommend collecting these fields, which come pre-installed with the ResellerRatings Product Reviews solution. The following two data fields helps syndication into Publishing platforms as they require this information to more easily place Ads.
mpn - Manufacturing Part Number - used in Google Syndication
GTIN - Global Trade identification Number, used in both Google and Bing syndication
The following data fields helps organize and categorize your product listings in your dashboard so you can see collection rates by brand and category. It also helps your teams start pulling measurement data from various categorical trends.
brand - The Brand the product belongs to, “Nike, Puma, Coke, etc”
category - The Category the product belongs to, ‘Apparel, etc’.
Title - The title or headline for the review.The beginning of the review body is generally used if no title is provided
Invoice - If the review was solicited after the sale, provide the invoice of the order made by the reviewer.
Location - Location the reviewer is from (city name).This will show below the reviewers name when rendered.
verified Is this a verified review (yes , or no).This will show the user is verified.
recommend Is this a recommended review, yes or no.This will display a recommended checkmark by the review.
status Approved or Rejected – the status of the review content in case old review content is rejected for flag violations.
review_id Older review_id matching to your system.This will be critical for UGC matching.
Importing Custom Questions and Attributes
- Custom questions are effectively specific feedback questions your team uses to get more information regarding products. For example, ‘How was the unboxing experience of this product?’
- Custom Attributes are specific attributes to a product that your customers can rate. For example – the FIT of a shoe or the COMFORT
Uploading Custom Attributes
Let's start off with Custom Attributes. Uploading custom question data you may have had in the past is relatively easy providing you can output the correct format.
Formatting your Custom Attributes
Custom attributes and custom data are PART of the custom import data review files. They are not separate files. Include all the data into one file.
- Custom Attribute Rules
- Limit of 5 custom attributes per SKU
- Each consist of two elements (attribute name and rating)
- Attribute Ratings are integers from 1-5
The column names follow the format: the column corresponding to the attribute name is “attribute_x”, and its corresponding rating column name is of the form “attribute_rating_x”, where x is an integer from 1 – 5.
For example, if there were two custom attributes, the columns would look like:
With two custom attributes for two reviews, this would look like:
If a review doesn’t have a rating for a given custom attribute, both the attribute and attribute rating can be left blank.
Importing Custom Questions
Custom Questions are very similar to Custom Attributes in formatting.
Custom questions consists of three column elements
- A short form question
- The question model type
- An Answer
For example, if there were two custom attributes, the columns would be:
With values from two reviews your csv would include the following:
As with custom attributes, if a review does not contain an answer for a particular question, those values can be left blank.
Ingesting parent / hierarchy data
Sometimes you may want to collect reviews for individual products, but display them all under an aggregate rating. For example, perhaps you have sunglasses that have different colored frames, all with different SKUS. But you want to use the aggregate of that content.
All you have to do when ingesting content is to create a new column with parentID (which can be a sku).