Survicate Beta
3 minute read
This destination is maintained by Survicate. For any issues, contact integrations@survicate.com.
Survicate is a customer feedback platform that helps businesses collect, analyze, and act on customer insights across every channel.
With this integration, you can send user attributes, company attributes, and events from RudderStack to Survicate, and use them to target surveys at the right audience and filter survey results.
Find the open source transformer code for this destination in the GitHub repository.
Connection compatibility
| Destination Information | |||
|---|---|---|---|
| |||
Setup
In your RudderStack dashboard, add a source. Then, from the list of destinations, select Survicate.
Connection settings
| Setting | Description |
|---|---|
| Destination Key | Enter your Survicate destination key. In the Survicate panel, go to Integrations > RudderStack, click Connect in the upper right corner. Then, copy the destination key from the Connect tab. |
Identify
Use the identify call to send user traits to Survicate. Survicate stores them as respondent attributes, which you can use to target surveys at specific users and filter survey results.
Note that:
- All traits passed in
identifycalls are available in Survicate once you view a respondent profile or export survey data. - All
camelCaseattribute keys are translated tosnake_case. - All object attributes are flattened to attributes prefixed by the object key.
- All array attributes are omitted.
Example
rudderanalytics.identify("1hKOmRA4GRlm", {
address: {
street: "6th St",
city: "San Francisco",
state: "CA",
postalCode: "94103",
country: "USA",
},
categories: ["startup", "SaaS"],
});The above call creates the following respondent traits in Survicate:
| Key | Value |
|---|---|
id | 1hKOmRA4GRlm |
address_street | 6th St |
address_city | San Francisco |
address_state | CA |
address_postal_code | 94103 |
address_country | USA |
The categories trait is omitted as it is an array attribute.
Group
Use the group call to to send company traits to Survicate.
Note that:
- All
grouptraits are passed to respondent attributes with thegroup_prefix. - All
camelCaseattribute keys are translated tosnake_case. - All object attributes are flattened to attributes prefixed by the object key.
- All array attributes are omitted.
Example
rudderanalytics.group("group123", {
name: "Company Inc.",
address: {
street: "6th St",
city: "San Francisco",
state: "CA",
postalCode: "94103",
country: "USA",
},
categories: ["startup", "SaaS"],
});The above call creates the following respondent traits in Survicate:
| Key | Value |
|---|---|
group_id | group123 |
group_name | Company Inc. |
group_address_street | 6th St |
group_address_city | San Francisco |
group_address_state | CA |
group_address_postal_code | 94103 |
group_address_country | USA |
The categories attribute is omitted as it is an array attribute.
Track
Use the track call to send events to Survicate.
You can use the event names to trigger Survicate surveys. In the Survicate panel, go to the survey’s Target tab > Audience and add the event to the active audience targeting conditions.
A sample track call is shown below:
rudderanalytics.track("plan_purchased", {
plan: "Pro Annual",
});Note that:
- Survicate uses only the event name for survey targeting — event properties are not available for targeting.
- In case of key conflicts,
traitsorcontext.traitstake precedence overproperties
FAQ
Where can I find the Survicate API Key?
- In the Survicate panel, go to Integrations > RudderStack.
- Click Connect in the upper right corner.
- Copy the destination key from the Connect tab.
Can I send survey responses back to RudderStack?
No — this integration only receives data from RudderStack. Survey responses are not sent back to RudderStack.