Indicative Destination

1. Create an Indicative account.
2. To integrate Segment as a data source go to Settings > Integrations > Segment
3. Click Enable with Segment under One-click Setup.
4. Select which Segment Source you want to connect to Indicative.
5. To connect multiple sources to this project, simply repeat steps 2 - 4.

You're all set! Walkthrough the Interactive Demo to get ramped up quickly and easily!

For additional information, contact support@indicative.com.

If you're not familiar with the Segment Specs, take a look to understand what the Identify method does.

When you call identify, we send the entire call as is to Indicative's server.

1
analytics.identify('ze8rt1u89', {
2
  name: 'Katherine Johnson',
3
  gender: 'Female',
4
  email: 'katherine@example.com',
5
  pioneer: true,
6
  building: 'Katherine G. Johnson Computational Research Facility'
7
  address: {
8
    city: 'Hampton',
9
    state: 'VA',
10
    postalCode: '23681'
11
  }
12
});

If you're not familiar with the Segment Specs, take a look to understand what the Track method does.

When you call track, we send the entire call as is to Indicative's server.

1
analytics.track("Calculation Completed", {
2
  calculation: "Launch window",
3
  mission: "Mercury mission"
4
  year: 1961
5
});

If you're not familiar with the Segment Specs, take a look to understand what the Page method and Screen method does.

Both page and screen calls will be sent to Indicative as events.

1
analytics.page({
2
  userId: "some_user_id", // on A.js client-side, you can leave out the `userId`
3
  category: "Merchant",
4
  name: "Settings",
5
})
6

7
// Note: `screen` calls are not possible from the A.js client-side.
8
analytics.screen({
9
  userId: "some_user_id",
10
  category: "Merchant",
11
  name: "Settings",
12
})

Indicative's documentation states that the values in the properties must not exceed 255 characters. Segment will still accept the call, but any values that exceed 255 characters will be trimmed (meaning only the first 255 characters will be sent to Indicative).

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.