Release Status Coming Soon Supported By Singer community
Availability Free Status Page Wootric Status Page
Default Historical Sync 1 year Default Replication Frequency 30 minutes
Whitelisting Unsupported Destination Incompatibilities None

Connecting Wootric

Step 1: Retrieve Your Wootric API credentials

  1. Sign into your Wootric account.
  2. Click the user menu in the top right corner, then Settings.
  3. Click API in the left nav tab.
  4. Your Client ID and Client Secret will display:

    Wootric API credentials.

Leave this page open for now - you’ll need it to complete the setup in Stitch.

Step 2: Add Wootric as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Wootric icon.

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

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

  5. In the Client ID field, paste your Wootric Client ID.
  6. In the Client Secret field, paste your Wootric Client Secret.

Step 3: Define the Historical Sync

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

Change this setting if you want to sync data beyond Wootric’s default setting of 1 year. For a detailed look at historical syncs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

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

Stitch offers two methods of creating a replication schedule:

  • Replication Frequency: This method requires selecting the interval you want replication to run for the integration. Start times of replication jobs are based on the start time and duration of the previous job. Refer to the Replication Frequency documentation for more information and examples.
  • Anchor scheduling: Based on the Replication Frequency, or interval, you select, this method “anchors” the start times of this integration’s replication jobs to a time you select to create a predictable schedule. Anchor scheduling is a combination of the Anchor Time and Replication Frequency settings, which must both be defined to use this method. Additionally, note that:

    • A Replication Frequency of at least one hour is required to use anchor scheduling.
    • An initial replication job may not begin immediately after saving the integration, depending on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.

To help prevent overages, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Initial and historical replication jobs

After you finish setting up Wootric, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending 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.


Wootric Table Schemas

Replication Method: Key-based Incremental Replication Key : updated_at
Primary Key : id API Endpoint: getAllDeclines

The declines table contains info about declines, or the instances where a user is presented with a survey opportunity and opts out.

id
INTEGER

The decline ID.

updated_at
DATE-TIME

The last time the decline was updated.

created_at
DATE-TIME

The time the decline was created.

end_user_id
INTEGER

The ID of the end user who declined the survey opportunity.

survey_id
INTEGER

The ID of the survey associated with the decline.


Replication Method: Key-based Incremental Replication Key : updated_at
Primary Key : id API Endpoint: getAllEndUsers

The end_users table contains info about the end users associated with survey opportunities.

id
INTEGER

The end user ID.

updated_at
DATE-TIME

The last time the end user was updated.

created_at
DATE-TIME

The time the end user was created.

email
STRING

The end user’s email address.

last_surveyed
DATE-TIME

The time the end user was last surveyed.

external_created_at
DATE-TIME

The UNIX timestamp of when the user was created externally.

page_views_count
INTEGER

The end user’s total number of page views.


Replication Method: Key-based Incremental Replication Key : updated_at
Primary Key : id API Endpoint: getAllResponses

The responses table contains info about end user responses to surveys.

id
INTEGER

The response ID.

updated_at
DATE-TIME

The time the response was last updated.

created_at
DATE-TIME

The time the response was created.

score
INTEGER

The response’s score.

text
STRING

The response’s comment.

ip_address
STRING

The response’s IP address.

origin_url
STRING

The response’s origin URL.

end_user_id
INTEGER

The ID of the end user who gave the response.

survey_id
INTEGER

The ID of the survey associated with the response.

completed
BOOLEAN

Indicates if a response has been completed.

excluded_from_calculations
BOOLEAN

Indicates if a response should be excluded from calculations.

tags

Tags applied to the response.

This data may be de-nested into a subtable if your data warehouse doesn't natively support nested data.

This subtable would be named responses__tags and may contain the following attributes:

_sdc_source_key_id
INTEGER

The response ID.

_sdc_level_0_id
INTEGER

This column forms part of a composite key for the table. The value will auto-increment for each unique record, beginning with 0.

value
STRING

The tag applied to the response.



Questions? Feedback?

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