Segment

The SuprSend segment integration enables you to sync users and events from Segment to SuprSend. This allows for seamless migration of users from Segment to SuprSend and the ability to use events from Segment to power automated workflows within SuprSend.

​

Connector setup on SuprSend

Login to SuprSend dashboard. Go to Settings-> Connectors. Select “Segment” from the connectors list. This is how segment integration page looks like.

Before beginning the Segment integration, it is important to establish how Segment events and users will be mapped in SuprSend. The following form fields will assist in setting up the desired data mapping within SuprSend:

​

1. Add Prefix to track events

This option allows for distinguishing the events coming from multiple data sources such as SuprSend SDK and Segment, or any other connector. By enabling this feature, a prefix of segment : will be added to all event names coming from Segment. This is particularly useful for existing Segment and SuprSend users who are passing the same events from both SuprSend SDK and Segment. By default, SuprSend assumes that events coming from all sources are unique and does not add any prefix to the event name.

For example- if the segment track API call looks like this

{
  "type": "track",
  "event": "User Registered",
  "properties": {
    "plan": "Pro Annual",
    "accountType" : "Facebook"
  }
}

associated event JSON at SuprSend with add prefix enabled will look like this

event_name = "segment : User Registered"

properties = {
	"plan": "Pro Annual",
    "accountType" : "Facebook"
}

​

2. User preference mapping

There are certain reserved properties in SuprSend user profile, such as language preference. In order to map these reserved properties, you have to define the trait in Segment identify call whose value should be mapped to the reserved property.

e.g.. if you define language as the mapping key for Preferred Language in SuprSend. The value passed against language trait in Segment identify call will be mapped as user preferred language in SuprSend.

Example of Segment identify API call

{
  "type": "identify",
  "traits": {
    "name": "Peter Gibbons",
    "email": "peter@example.com",
    "language": "hi",
    "plan": "premium",
    "logins": 5
  },
  "userId": "97980cfea0067"
}

associated user JSON at SuprSend will be.

• SegmentuserIDis used to map thedistinct_idof user on SuprSend.

• All properties insidetraitsare considered as user properties which can be further used to map user channels and preferences in SuprSend.

distinct_id = "97980cfea0067"

properties = {
  "name": "Peter Gibbons",
  "email": "peter@example.com",
  "language": "hi",
  "plan": "premium",
  "logins": 5
}

and with language set as mapping key, hi will be set as the preferred_language in user profile

​

3. User channel mapping

For existing segment users, you can use the same mapping that is used to track user channels in your segment identify call in SuprSend as well. Just map the channel keys in the Segment identify call with the corresponding communication channel in SuprSend interface.

By default, the email trait in the Segment identify call is mapped to the Email channel in SuprSend, and the phone trait is mapped to the SMS channel. You can add the mapping of other channels in the similar way

For new users setting up a fresh Segment integration, below table can be used as a reference for mapping user channels in both SuprSend and Segment:

Example of Segment identify API call

{
  "type": "identify",
  "traits": {
    "name": "Peter Gibbons",
    "email": "peter@example.com",
    "phone":"+15555555555",
    "slack_email":"peter@abccompany.com",
    "language": "hi",
    "plan": "premium",
    "logins": 5
  },
  "userId": "97980cfea0067"
}

with below User Channel mapping

Communication channels in user profile will look like this

Click on Save Mapping to save the changes

Now that the desired mapping of Segment events and users in SuprSend has been established, the next step is to start Segment integration.

​

Setting up data sync from Segment to SuprSend

You’ll have to configure SuprSend as a destination in Segment.

Follow below steps to configure SuprSend Destination in Segment:

Your setup is now complete, enabling events and users data to flow from Segment to SuprSend. You can use this info to automatically power SuprSend workflows without making any changes in your codebase.