Skip to main content

Insight data dependencies for product recommendations

What insight data you need to sync to use each type of product recommendation.

Written by Gareth Burroughes
Updated over a week ago

To use our product recommendations feature, you must sync the correct insight data from your ecommerce platform. Your products must be added as an account-scoped Insight data collection and the collection name must be prefixed with catalog_.


Dependencies

The table below details the types of product recommendation, the Insight data collections required to power them, and the fields used to match products between collections.

The Unique product identifier is set at the catalog level. By default, we use Name and SKU, but you can change this if you want to.

Learn more in Change the unique product identifier.

Product recommendation type

Required Insight data collections

Product match

Custom category

Products

N/A

Best sellers

Products, Orders

Unique product identifier

Most viewed

Products, WebInsight

Product URL

Last browsed

Products, WebInsight

Product URL

Trending

Products, Orders, WebInsight

Unique product identifier and product URL

Also bought*

Products, Orders

Unique product identifier

Lookalikes (predictive)

Products, Orders

Unique product identifier

Best next (predictive)

Products, Orders

Unique product identifier

New in store

Products

N/A

Bought together*

Products, Orders, Cart (optional)

Unique product identifier

Hybrid prediction

Products, Orders

Unique product identifier

*For Also bought and Bought together recommendations, we use orders or cart product SKU or order or cart product URL fields to access recommendations for a specific contact.

Data schemas

For product recommendations to work correctly, your product and order data needs to follow a specific structure. You can refer to our data schema to find this structure:

Read more in the Web behavior tracking section of our Help Centre.


Sync your data to Dotdigital

You can sync Insight data through an integration, or directly through the API.

Did this answer your question?