Insight data: Wishlist data - Magento 1

Map and synchronise customer wishlists against contacts in Dotdigital.

Henry Huish avatar
Written by Henry Huish
Updated over a week ago

Wishlists are synced and batched once they are created but are also updated within Dotdigital when any modifications are made to the wishlist after their creation.


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 wishlist data sync

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

  2. Under Wishlist 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 wishlist data

The wishlist data that gets synced includes:

Name

Description

id

The Magento database ID of the wishlist.

customer_id

The customer ID the wishlist is associated with.

email

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

updated_at

The last date/time the wishlist was updated.

The following information is also synced for every product within the wishlist:

Name

Description

sku

The SKU of the product.

name

The name of the product.

qty

The quantity of the product the customer has in their wishlist.

price

The price of the product.

I've enabled the wishlist 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 wishlist import yet.

Why is the wishlist data marked as imported in Magento but not showing 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 wishlist data imported with matching IDs, perhaps coming from a staging site, as this key must be unique.

Did this answer your question?