# Survicate Destination

## Destination Info

* Accepts [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify) calls.
* Refer to it as **Survicate** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

### Components

* [Browser](https://github.com/Survicate/analytics.js-integration-survicate)
* [iOS](https://github.com/Survicate/analytics-swift-survicate)
* [Android](https://github.com/Survicate/analytics-kotlin-survicate)

## Connection Modes

[Learn more about connection modes.](/docs/segment/connections/destinations/#connection-modes)

### Device-Mode

* web: yes
* mobile: yes
* server: no

### Cloud-Mode

* web: no
* mobile: no
* server: no

[Survicate](https://survicate.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) is a complete toolkit for customer feedback. From website optimization and customer satisfaction surveys to complex customer insight processes integrated with your email campaigns.

This destination is maintained by Survicate. For any issues with the destination, [contact the Survicate Support team](mailto:help@survicate.com).

## Getting Started

1. From the Segment web app, click **Catalog**.
2. Search for "Survicate" in the Catalog, select it, and choose which of your sources to connect the destination to.
3. Enter the "Workspace Key" into your Segment Settings UI which you can find from your [Survicate Workspace Settings](https://panel.survicate.com/).

## Identify

If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/segment/connections/spec/identify/) does. An example call would look like:

```text
analytics.identify('userId123', {
  email: 'john.doe@example.com',
  jobTitle: 'CEO',
  companySize: '50'
});
```

When you call Identify, we pass Segment traits as respondents' attributes to Survicate. They can be used to trigger website surveys or filter survey results.

All traits passed in Identify calls will be available in Survicate - once you view a respondent profile or export survey data.

All `camelCase` attribute keys are translated to `snake_case`.

Attributes which are standardized in Survicate include: `first_name`, `last_name`, `email`, `organization`, `department`, `job_title`, `phone`, `website`, `country`, `address_one`, `address_two`, `city`, `state`, `zip`, `fax`, `annual_revenue`, `employees`

All *object attributes* will be flattened to attributes prefixed by object key. All *array attributes* will be omitted.

```text
analytics.identify('1234', {
    address: {
        street: '6th St',
        city: 'San Francisco',
        state: 'CA',
        postalCode: '94103',
        country: 'USA'
    },
    categories: ['startup','SaaS']
});
```

The above described call creates following respondent's traits in Survicate:

| key                   | value         |
| --------------------- | ------------- |
| id                    | 1234          |
| address\_street       | 6th St        |
| address\_city         | San Francisco |
| address\_state        | CA            |
| address\_postal\_code | 94103         |
| address\_country      | USA           |

*Categories* attribute is omitted as it is an array attribute.

## Group

If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/segment/connections/spec/group/) does. An example call would look like:

```text
analytics.group('group123', {
  name: 'Company Inc.'
});
```

All Group traits will be passed to respondent attributes with `group_` prefix. All `camelCase` attribute keys are translated to `snake_case`. All *object attributes* will be flattened to attributes prefixed by object key. All *array attributes* will be omitted.

```text
analytics.group('group123', {
    name: 'Company Inc.',
    address: {
        street: '6th St',
        city: 'San Francisco',
        state: 'CA',
        postalCode: '94103',
        country: 'USA'
    },
    categories: ['startup','SaaS']
});
```

The above described call creates the following respondent's 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           |

*Categories* attribute is omitted as it is an array attribute.

### Sending survey answers to Segment

Once the Segment integration is enabled in Survicate Integrations tab, it starts sending track events from your client-side source. Here's a sample call that will be triggered when a survey is answered.

```text
analytics.track('survicate_survey_answered', {
  answer: 'Great suppport!',
  answer_type: 'text',
  question: 'What makes us stand out from the competition?',
  survey: 'Advantages Over Competition Research',
});
```

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field         | Description                                                                                        | Required | Type   |
| ------------- | -------------------------------------------------------------------------------------------------- | -------- | ------ |
| Workspace Key | Your Workspace Key can be found \[here]\(https://panel.survicate.com/o/0/w/0/settings/web-surveys) | Yes      | string |