Skip to main content
Insight data: Review data - Magento 1

Map and synchronise customer reviews against contacts in Dotdigital.

Gareth Burroughes avatar
Written by Gareth Burroughes
Updated over 8 months ago

Before you start

Things you need to know:

  • This feature requires OrderInsight to be enabled on your Dotdigital account. Contact your Customer Success representative if you need help with this.


Enable review data sync

  1. Go to System > Configuration > Dotdigital > Sync Settings.

  2. Under Review Sync, expand the Enabled drop-down menu and select Yes.

  3. Select Save Config.

Magento confirms that the settings have been saved and the synchronisation begins.

List of synced review data

The review data that gets synced includes:

Name

Description

id

The Magento database ID of the review.

customer_id

The customer ID the review is associated with.

email

The email address of the customer the review is associated with.

product_name

The name of the product the customer left a review for.

product_sku

The SKU of the product the customer left a review for.

review_date

The date/time the review was left.

website_name

The website the review was left on.

store_name

The store name the review was left on.

price_rating_score

The score the customer left for price.

value_rating_score

The score the customer left for value.

quality_rating_score

The score the customer left for quality.

I've enabled the review sync but nothing is displaying in Dotdigital. Why is this?

This could be for the following reasons:

  • You don't have valid API credentials or saved details.

  • OrderInsight isn't enabled on your account.

  • Cron is not running on your site.

  • The importer is currently processing other imports and hasn't got to the review import yet.

Why is the review data marked as imported in Magento but not displaying in Dotdigital?

Insight data can take several minutes to import and show in Dotdigital, even after a sync is complete. You might want to ensure you don't already have review data imported with matching IDs, perhaps coming from a staging site, as this key must be unique.

Did this answer your question?