Survicate (Actions) Destination

1. From the Segment web app, click Destinations.
2. Search for "Survicate (Actions)" 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.

Survicate (Actions) has the following presets

Build your own Mappings. Combine supported triggers with the following Survicate-supported actions:

• Track Event
• Identify Group
• Identify User

Invoke survey with Segment Track event

Track Event is a Web action. The default Trigger is type = "track"

Send group traits to Survicate

Identify Group is a Web action. The default Trigger is type = "group"

Set visitor traits with Segment Identify event

Identify User is a Web action. The default Trigger is type = "identify"

If you're not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

1
analytics.identify('userId123', {
2
  email: 'john.doe@example.com',
3
  jobTitle: 'CEO',
4
  companySize: '50'
5
});

When you call Identify, we pass Segment traits as respondents' attributes to Survicate. They can be used to trigger web 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.

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

1
analytics.identify('1234', {
2
    address: {
3
        street: '6th St',
4
        city: 'San Francisco',
5
        state: 'CA',
6
        postalCode: '94103',
7
        country: 'USA'
8
    },
9
    categories: ['startup','SaaS']
10
});

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

Categories attribute is omitted as it is an array attribute.

If you're not familiar with the Segment Specs, take a look to understand what the Group method does. An example call would look like:

1
analytics.group('group123', {
2
  name: 'Company Inc.'
3
});

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.

1
analytics.group('group123', {
2
    name: 'Company Inc.',
3
    address: {
4
        street: '6th St',
5
        city: 'San Francisco',
6
        state: 'CA',
7
        postalCode: '94103',
8
        country: 'USA'
9
    },
10
    categories: ['startup','SaaS']
11
});

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

Categories attribute is omitted as it is an array attribute.

A Segment track call, f.ex:

1
analytics.track('plan_purchased', {
2
    plan: 'Pro Annual',
3
    accountType : 'Facebook'
4
});

will trigger a Survicate call that sends the event name and properties to Survicate.

If you want to trigger your survey on a Segment event, you are able to do that by setting that condition in the panel in the targeting tab in the section: "When a user triggers an event" under "Where would you like to show the survey".

When the Segment event fires and other targeting conditions you've set in the panel are met - your survey will show.

Event properties are optional.

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.

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

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