Survicate Cloud Mode (Actions) Destination

1. Open the Survicate Connect tab for the Segment (Cloud Mode, Actions) integration and copy your destination key.
2. Open the Segment app and click Destinations.
3. Search for "Survicate Cloud Mode (Actions)" in the Catalog, select it, and choose which of your sources to connect the destination to.
4. Enter the destination key into your Survicate Cloud Mode (Actions) destination settings page.

Survicate performs the following data normalization on Segment events:

• Translates all camelCase attribute keys to snake_case.
• Flattens all object attributes to attributes prefixed by object key.
• Omits all array attributes.

Survicate Cloud Mode (Actions) has the following presets

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

• Identify Group
• Identify User
• Track Event

Send group traits to Survicate

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

Send user traits to Survicate

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

Send events to Survicate

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

If you're not familiar with the Segment Spec, read more about the Identify method.

An example Identify call takes the following format:

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

When you call Identify, Survicate receives Segment traits as respondent attributes. Use these actions in Survicate to trigger web and mobile surveys or filter survey results.

All traits passed in Identify calls are available in Survicate after you view a respondent profile or export survey data.

If you're not familiar with the Segment Spec, read more about the Group method.

Here's an example Group call:

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
});
12

The preceding call creates the following traits in Survicate:

Survicate omits the categories attribute, as it's an array.

If you're not familiar with the Segment Spec, read more about the Track method.

Here's an example of a Track call:

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

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

To trigger a survey on a Segment event, set that condition in Survicate. Open the survey's Target > Audience and add the event to the active audience targeting conditions.

When the Segment event fires and you've met any preset targeting conditions, Survicate shows your survey.

Event properties are optional for Track events.

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

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