Yotpo (Edge)

Configure Yotpo as a Source in your Pipeline

Perform the following steps to configure your Yotpo Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Yotpo.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Yotpo Source.

   • In the Connect to Yotpo section, specify the following:

     • Access Token: The access token that you generated using the secret key of your store.

     • Store ID: The app key of your store, which you copied from the API Credentials section. The Yotpo API documentation refers to this value as store_id.

6. Click Test & Continue to test the connection to your Yotpo Source. Once the test is successful, you can proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

For the Customers and Reviews objects, Hevo ingests new and updated records in each Pipeline run, as per the sync frequency. Changes are identified using the time at which the customer account or the review was last updated.

For all the other objects, Hevo ingests the entire data during each Pipeline run. For each product, Hevo also reads its variants, and the GTINs and options of the product and its variants. Custom properties of products are added as columns with the prefix custom_.

You can resync only the parent objects, Customers, Products, and Reviews. When you resync Products, Hevo also resyncs its child objects.

Yotpo limits the number of API requests that can be made for a store in a given period of time. Read Rate Limiting. If this limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Note: The Customers object uses the Append load mode, and all the other objects use the Merge load mode. You cannot change the load mode of an object. As each Pipeline run adds the new and updated customers as new records, the Customers table in the Destination can contain more than one record for a customer.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

The primary keys of the objects are:

• Customers: None. As the object uses the Append load mode, it has no primary key.

• Reviews: id

• Products: yotpo_product_id

• Product Variants: product_variant_yotpo_id

• Product GTINs, Product Variant GTINs, and Product Variant Options: gtin_key, variant_gtin_key, and variant_option_key. Hevo generates these keys from the IDs of the parent product and variant and the content of the record.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---