Already have an account? Sign in

Yotpo (v2)

Yotpo integration summary

Stitch’s Yotpo integration replicates data using theYotpo Core API. Refer to theSchema section for a list of objects available for replication.

Yotpo feature snapshot

A high-level look at Stitch's Yotpo (v2) integration, including release status, useful links, and the features supported in Stitch.

Connecting Yotpo

Yotpo setup requirements

To set up Yotpo in Stitch, you need:

• To be the Account Administrator in Yotpo.This is required to access your Yotpo API credentials.

Step 1: Retrieve your Yotpo API credentials

1. Sign into yourYotpo account.
2. Click the user menu (person icon) in the top right corner.
3. ClickAccount Settings.
4. On theAccount Settings page, click theStore tab.

5. Locate theAPI Credentials section:

   

6. TheApp Key field contains yourAPI Key, and theSecret Key is yourAPI Secret.

Leave this page open for now - you’ll need it to complete the next step.

Step 2: Add Yotpo as a Stitch data source

1. Sign into your Stitch account.

2. On the Stitch Dashboard page, click theAdd Integration button.

3. Click theYotpo icon.

4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

   For example, the name “Stitch Yotpo” would create a schema calledstitch_yotpo in the destination.Note: Schema names cannot be changed after you save the integration.

5. In theYotpo API Key field, paste the value from theApp Key field in your Yotpo account.
6. In theYotpo API Secret field, paste the value from theSecret Key field in your Yotpo account.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Yotpo integration. This means that dataequal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Yotpo’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In theReplication Frequency section, you’ll create the integration’sreplication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Yotpo integrations support the following replication scheduling methods:

• Replication Frequency

• Anchor Scheduling

• Advanced Scheduling using Cron (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 5: Set objects to replicate

The last step is to select the tables you want to replicate.Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

• Selection options
• Individual tables
• All tables

Initial and historical replication jobs

After you finish setting up Yotpo, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Yotpo replication

Every time Stitch runs a replication job for Yotpo, the last 30 days’ worth of data will be replicated.

This is applicable to all tables in the integration.

Stitch replicates data in this way to account for updates made to existing records within the default attribution window of 30 days, thus ensuring you won’t make decisions based on stale (or false) data.As a result, you may see a higher number of replicated rows than what’s being generated in Yotpo.

Setting the Replication Frequency to a higher frequency - like 30 minutes - can result in re-replicating recent data and contribute to greater row usage. Replicating fewer tables or selecting a lower frequency can help keep your row count low.

Refer to the documentation for each of these tables in the next section for more info.

Attribution window examples

In the tabs below are examples of attribution windows behave during historical (initial) and ongoing replication jobs.

• Historical and full re-replications
• Ongoing replications

SELECT*FROMyotpo.reviewsWHEREcreated_at>='2017-06-03 00:00:00'/* Min. Extraction Date */ORDERBYcreated_at

SELECT*FROMreviewsWHEREcreated_at>='2017-09-01 00:00:00'/* max Replication Key value - Attribution Window */ANDcreated_at<='2017-10-01 00:00:00'/* max Replication Key value from previous job */ORDERBYcreated_at

Yotpo table reference

emails.email_address = unsubscribers.user_email

product_reviews.product_id = products.yotpo_id

product_reviews.source_review_id = reviews.id

products.yotpo_id = product_reviews.product_id

reviews.id = product_reviews.source_review_id

unsubscribers.user_email = emails.email_address

Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.