Connecting to Data¶

There are three categories of Data Connectors in Signals:

Enterprise Data Connectors are used to connect to internal databases or other 1st party data platforms in your organization.

3rd Party Data Connectors provide access to data owned by your organization but stored in 3rd party systems. Examples include salesforce, Google Analytics, and Zendesk among many others.

Public Data Connectors allow you to access data that anyone can view on the internet, but in a uniform format. We collect data from Amazon, Facebook, the Google Play store, consumeraffairs.com, and many other sites.

You can also upload a csv or excel file from your local computer.

Note

Enterprise Data Connectors and some 3rd Party Data Sources require you to map fields in your data prior to uploading. See Mapping Data to learn about this process.

Enterprise Data Connectors¶

The Enterprise Data Connector application allows users to connect with a variety of internal data sources.

Examples include:

Hive
mySQL
Microsoft SQL Server
PostgreSQL
Oracle SQL

3rd Party Data Connectors¶

3rd Party Data Connectors usually have a pop-up window that allows you to enter your credentials with the 3rd party in order to authenticate with Signals.

Note

Make sure you have pop-up blocking disabled when connecting with a 3rd Party Data Connector

salesforce
Foresee
Surveymonkey
Gmail
Livechat
Intercom
JIRA
UserVoice
Zendesk
Google Analytics
Trello

salesforce¶

Foresee¶

Surveymonkey¶

Gmail¶

Gmail allows you to connect with a Gmail account and enter a query that will pull data matching the query.

Livechat¶

The LiveChat connector allows you to select a date range and the type of user you want to analyze chats for: Agent, Visitor, or both.

Intercom¶

JIRA¶

With the JIRA Data Connector, you can select which projects you want to analyze. You can also specify a ticket type if desired. If nothing is specified, Signals will pull all of your JIRA data.

UserVoice¶

The UserVoice data connector requires a login and api key to connect to your uservoice data. The permissions associated with the login correspond with what data will be available through the connector.

Users can specify which objects you want to analyze.

Zendesk¶

Google Analytics¶

Trello¶

Twitter (with twitter account credentials)
Facebook (with facebook account credentials)
Weibo search
Youku
YouTube Comments

Consumer Financial Protection Bureau
Indeed
Consumer Affairs

iOS Store Reviews¶

Google Play Store Reviews¶

Home Depot Product Reviews¶

Lowes Product Reviews¶

Best Buy Product Reviews¶

Wal Mart Product Reviews¶

Etsy Shop Reviews¶

Etsy Product Reviews¶

Amazon Product Reviews¶

Twitter¶

Facebook¶

Weibo search¶

Youku¶

YouTube Comments¶

Consumer Financial Protection Bureau¶

Indeed¶

Consumer Affairs¶

Signals SDK¶

The Signals SDK should be used to upload files more than 500 MB.

It can also be used to develop custom connections and/or schedule uploads.

We offer a node.js wrapper for our SDK. https://www.npmjs.com/package/signals-api

To generate an API key:

go to Settings in the left-hand menu from the Signals homepage.
In the Settings page, click the button to generate an api key towards the bottom.
This API key will be generated and downloaded in JSON format to be included in your application.

After the API key has been generated, you can always download it again from the Settings page.

The “Revoke” button will immediately invalidate the API key from further use.

Note

API keys can only be generated by authenticated users. All API keys are tied exclusively to a single user account.