Calixa Destination

1. Login to your Calixa account.
2. Go to the Integrations page and click Add Integration.
3. Select the Segment Integration and sign in to your Segment account to grant Calixa access.

If you aren't familiar with the Segment Spec, take a look at the Track method documentation to learn about what it does. An example call would look like:

1
{
2
  'userId': '019mr8mf4r',
3
  'action': 'track',
4
  'event': 'Account Created',
5
  'properties': {
6
    'account_name': 'Initech'
7
  },
8
  'context': {
9
      'groupId': 'acct_123'
10
      }
11
}

Calixa supports the following Track calls from Segment's B2B Spec:

• Signed Up - Creates a user in Calixa
• Account Created - Creates an account in Calixa
• Account Deleted - Deletes an account in Calixa
• Account Added User - Adds a user to an account
• Account Removed User - Removes a user from an account

If you aren't familiar with the Segment Spec, take a look at the Identify method documentation to learn about what it does. An example call would look like:

1
analytics.identify('userId123', {
2
  email: 'john.doe@example.com'
3
});

Segment sends Identify calls to Calixa as an identify event. When you identify a new user, Calixa creates a new User record. If the User already exists, Calixa updates the User's properties.

If you aren't familiar with the Segment Spec, take a look at the Group method documentation to learn about what it does. An example call would look like:

1
{
2
  'type': 'group',
3
  'groupId': '0e8c78ea9d97a7b8185e8632',
4
  'traits': {
5
    'name': 'Initech',
6
    'industry': 'Technology',
7
    'employees': 329,
8
    'plan': 'enterprise',
9
    'total billed': 830
10
  }
11
}

Segment sends Group calls to Calixa as an group event. A group event can create an Account or associate a User to an Account within Calixa.

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.