Already have an account? Sign in

Revinate (v1)

Revinate integration summary

Stitch’s Revinate integration replicates data using theRevinate Porter API. Refer to theSchema section for a list of objects available for replication.

Revinate feature snapshot

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

Connecting Revinate

Revinate setup requirements

To set up Revinate in Stitch, you need:

• A Revinate account with API access. Reach out to your Revinate sales representative or account manager to obtain the correct permissions.

• A Revinate API token and secret. To obtain these credentials, reach out to your Revinate sales representative or account manager.

Step 1: Add Revinate as a Stitch data source

1. Sign into your Stitch account.

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

3. Click theRevinate 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 Revinate” would create a schema calledstitch_revinate in the destination.Note: Schema names cannot be changed after you save the integration.

5. In theUsername field, enter your Revinate username.
6. In theAPI Key field, paste your Revinate API key. Your Revinate API token must be obtained throughyour Revinate sales representative or account manager.
7. In theAPI Secret field, paste your Revinate API secret. Your Revinate API secret must be obtained throughyour Revinate sales representative or account manager.

Step 2: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Revinate 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 Revinate’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.

Step 3: 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.

Revinate 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.

Initial and historical replication jobs

After you finish setting up Revinate, 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.

Revinate replication

Extraction overview

When Stitch runs a replication job for Revinate, a few things will happen:

1. First, Stitch will get all the hotels that theauthenticating user has access to.
2. Stitch willreplicate review snapshot data (hotel_reviews_snapshot,hotel_reviews_snapshot_by_site,hotel_reviews_snapshot_by_time) for the hotel.
3. Stitch will replicate data about the hotel (hotels).
4. Stitch will repeat steps 2-3 until review snapshot and hotel data has been replicated for all accessible hotels.
5. Stitch will replicate review data (reviews) based on the last savedupdated_at value, which is the table’s Replication Key.

Replicating review snapshots

When Stitch extracts review snapshot data, it will do so using anAttribution Window of1 week. This means that during each replication job, Stitch will replicate snapshot data for that last completed week. For example: If the integration is scheduled to run every 30 minutes, then snapshot data for the last week will be replicated every 30 minutes.

This is applicable to thehotel_reviews_snapshot,hotel_reviews_snapshot_by_site, andhotel_reviews_snapshot_by_time tables.

Revinate table reference

hotel_reviews_snapshot.hotel_id = hotel_reviews_snapshot_by_site.hotel_id

hotel_reviews_snapshot.hotel_id = hotel_reviews_snapshot_by_time.hotel_id

hotel_reviews_snapshot.hotel_id = hotels.hotel_id

hotel_reviews_snapshot.hotel_id = reviews.hotel_id

hotel_reviews_snapshot_by_site.hotel_id = hotel_reviews_snapshot.hotel_id

hotel_reviews_snapshot_by_site.hotel_id = hotel_reviews_snapshot_by_time.hotel_id

hotel_reviews_snapshot_by_site.hotel_id = hotels.hotel_id

hotel_reviews_snapshot_by_site.hotel_id = reviews.hotel_id

hotel_reviews_snapshot_by_site.review_site_id = reviews.review_site_id

hotel_reviews_snapshot_by_time.hotel_id = hotel_reviews_snapshot.hotel_id

hotel_reviews_snapshot_by_time.hotel_id = hotel_reviews_snapshot_by_site.hotel_id

hotel_reviews_snapshot_by_time.hotel_id = hotels.hotel_id

hotel_reviews_snapshot_by_time.hotel_id = reviews.hotel_id

hotels.hotel_id = hotel_reviews_snapshot.hotel_id

hotels.hotel_id = hotel_reviews_snapshot_by_site.hotel_id

hotels.hotel_id = hotel_reviews_snapshot_by_time.hotel_id

hotels.hotel_id = reviews.hotel_id

reviews.hotel_id = hotel_reviews_snapshot.hotel_id

reviews.hotel_id = hotel_reviews_snapshot_by_site.hotel_id

reviews.review_site_id = hotel_reviews_snapshot_by_site.review_site_id

reviews.hotel_id = hotel_reviews_snapshot_by_time.hotel_id

reviews.hotel_id = hotels.hotel_id

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.