Skip to main content Skip to complementary content
Already have an account? Sign in

UserVoice (v1)

Last updated: 9/15/2026

UserVoice integration summary

Stitch’s UserVoice integration replicates data using the UserVoice API. Refer to the Schema section for a list of objects available for replication.

UserVoice feature snapshot

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

STITCH
Release status

Released on September 19, 2018

Supported by

Singer Community

Stitch plan

Standard

API availability

Available

Singer GitHub repository

singer-io/tap-uservoice

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Supported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Supported

Column selection

Supported

Select all

Supported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting UserVoice

UserVoice setup requirements

To set up UserVoice in Stitch, you need:

  • Access to Settings in your UserVoice account. This is required to generate API credentials for Stitch.

Step 1: Generate UserVoice API credentials

Step 1.1: Create a Stitch UserVoice API client

Add API key window in UserVoice
Add API key window in UserVoice

  1. Sign into your UserVoice account.
  2. Click Settings, which is in the bottom left corner.
  3. Click Integrations.
  4. Click UserVoice API keys.
  5. Click the Add API key button.
  6. In the window that displays, fill in the fields as follows:
    • Name - Enter a name for the API client. For example: stitch
    • Trusted - Check the checkbox.
  7. When finished, click the Add API key to create the API client.

Step 1.2: Locate API credentials

The API client will display on the page after it’s created. In the image below the API key and API Secret are highlighted:

UserVoice UI with highlighted API key and API secret fields
UserVoice UI with highlighted API key and API secret fields

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

Step 2: Add UserVoice 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 UserVoice 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 UserVoice” would create a schema called stitch_uservoice in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the UserVoice Subdomain field, enter your UserVoice subdomain. For example: If the full subdomain were stitch.uservoice.com, you’d enter stitch into this field.
  6. In the UserVoice API Key field, paste your UserVoice API key.
  7. In the UserVoice API Secret field, paste the API secret.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your UserVoice 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 replicate data beyond UserVoice’s default setting of 1 year. For a detailed look at historical replication jobs, 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.

UserVoice integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding 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 and columns 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.

For UserVoice integrations, you can select:

  1. Individual tables and columns

  2. All tables and columns

Click the tabs to view instructions for each selection method.

  1. In the integration’s Tables to Replicate tab, locate a table you want to replicate.
  2. To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.

  3. To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.

  4. Repeat this process for all the tables and columns you want to replicate.
  5. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
  1. Click into the integration from the Stitch Dashboard page.
  2. Click the Tables to Replicate tab.

  3. In the list of tables, click the box next to the Table Names column.
  4. In the menu that displays, click Track all Tables and Fields:

    The Track all Tables and Fields menu in the Tables to Replicate tab
    The Track all Tables and Fields menu in the Tables to Replicate tab

  5. Click the Finalize Your Selections button at the bottom of the page to save your data selections.

Initial and historical replication jobs

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

UserVoice table reference

categories

The categories contains info about the various categories in your UserVoice account. Categories are used to organize suggestions in a forum.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

categories schema on GitHub

UserVoice API method

comments

The comments table contains info about the comments forum users have made.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

comments schema on GitHub

UserVoice API method

external_accounts

The external_accounts table contains info about accounts from external systems.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

external_accounts schema on GitHub

UserVoice API method

external_users

The external_users table contains info about users from external systems.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

external_users schema on GitHub

UserVoice API method

feature_statuses

The feature_statuses table contains info about feature statuses, which are used to indicate a feature’s current state.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

feature_statuses schema on GitHub

UserVoice API method

features

The features table contains info about planned product features.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

features schema on GitHub

UserVoice API method

forums

The forums table contains info about your discussion forums.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

forums schema on GitHub

UserVoice API method

labels

The labels table contains info about labels in your UserVoice account, which admins use to internally organize suggestions.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

labels schema on GitHub

UserVoice API method

nps_ratings

The nps_ratings table contains info about NPS, or Net Promoter Scores. NPS is used to measure customer satisfaction on a scale from 0-10.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

nps_ratings schema on GitHub

UserVoice API method

product_areas

The product_areas table contains info about your product areas, which can be assigned to features to organize them into groups.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

product_areas schema on GitHub

UserVoice API method

requests

The requests table contains info about requests, which are specific pieces of feedback submitted by your end users. Requests are associated with suggestions, and users are counted as supporters of the suggestion.

Unlike suggestions, requests are captured by your team on behalf of end users.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

requests schema on GitHub

UserVoice API method

segmented_values

The segmented_values table contains info about segmented values, which are calculated columns that aggregate supporter metrics for a segment.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

segmented_values schema on GitHub

UserVoice API method

segments

The segments table contains info about segments, which are subsets of your end users and accounts defined by a set of criteria.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

segments schema on GitHub

UserVoice API method

status_updates

The status_updates table contains info about admin changes to the statuses of suggestions.

Replication Method

Key-based Incremental

Replication Key

updated_at

Useful links

UserVoice documentation

status_updates schema on GitHub

UserVoice API method

statuses

The statuses table contains info about the various suggestion statuses in your UserVoice account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

statuses schema on GitHub

UserVoice API method

suggestions

The suggestions table contains info about suggestions, or requested changes to your product. Suggestions can be created by your end users, your product team, or other people from your company.

Each suggestion is linked to a forum, where it can be visible publicly or to authorized users.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

suggestions schema on GitHub

UserVoice API method

supporters

The supporters table contains info about supporters, who are end users that are supporters of a suggestion.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

UserVoice documentation

supporters schema on GitHub

UserVoice API method

teams

The teams table contains info about the teams in your UserVoice account. UserVoice admins and contributors can be assigned to teams to organize feedback the feedback they capture by department, such as Sales, Support, or Product.

Replication Method

Key-based Incremental

Primary Key

id

Useful links

UserVoice documentation

teams schema on GitHub

UserVoice API method

users

The users table contains info about your users. This includes both UserVoice admins and end users.

Replication Method

Key-based Incremental

Primary Key

id

Replication Keys

updated_at

created_at

Useful links

UserVoice documentation

users schema on GitHub

UserVoice API method

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!