Segment

• First you define how Segment users and events map to SuprSend
• Then you connect Segment to SuprSend as a webhook destination. Once live, your identify and track calls flow through automatically. (Click any step below to jump to its section.)

​

Connector setup on SuprSend

​

1. Event mapping

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

event_name = "User Registered"

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

​

2. User mapping

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

• User preference mapping — map traits to reserved profile fields such as Locale ($locale) and Timezone ($timezone). For example, mapping the language trait to Locale means the value in language (hi above) becomes the user’s preferred language.
• User channel mapping — map each SuprSend channel to the Segment trait that carries its value. Channels are not mapped automatically; you must define each one here for it to work. Use the channel keys below:

​

Setting up data sync from Segment to SuprSend

1

Add SuprSend as destination in your segment account

1. Login to your Segment account. Select Connections-> Destinations from the side navigation menu and click on “Add Destination”

2

Search for webhook

This will open destinations catalog. Search for webhook and select “Webhooks (Actions)”

3

Add Destination

On the Webhooks page, click on “Add destination”

4

Pick Data Source

Select the data source from which you are syncing your user and event data and click on “Next”

5

Add Destination Name

On the setup screen, add Destination name. Destination name can be “SuprSend {workspace}”. For example- For staging workspace, the destination name can be “SuprSend Staging”. Choose “Fill in settings manually” and click on “Create destination”.

6

Create a New Mapping

Now, on your webhook destination page, go to Mappings tab and create a +New Mapping.

7

Send an HTTP Request

Select Send an HTTP request in Add Mapping modal and add below details

8

Add below mapping in the send request:

• Select any of event type- track and identify
  
• In Add test event, select Load Test Event from Source
  
• In Select Mappings, add below details:

URL: https://hub.suprsend.com/connector/segment/
Method: POST
Authorization in headers: Bearer _api_key_(Please make sure to replace “api_key” with actual api key from segment connector settings page.)

9

Sending Test Event

Now, send a test event of type track or identify. You’ll see status 200 OK response and the corresponding event on SuprSend dashboard -> API logs page.

Callout ContentIf you don’t get 200 OK response in event tester, this means that Segment was unable to successfully setup your SuprSend connection. Double check Webhook URL and header in step-7 and see if its configured correctly in the Destination settings.

Once your SuprSend connection is successful, try sending a test identify call and see if the user channels are mapped correctly in SuprSend. You can see the synced user on SuprSend dashboard -> Subscribers page. Also, send a test track event call and check if the workflows are getting triggered.

10

Enable Mapping

1. After successful testing, Save and Enable the mapping.

11

Enable Destination in Settings

Also enable destination in Settings tab to start sending webhook data to SuprSend.

​

Handling anonymous users

{
  "type": "identify",
  "anonymousId": "507f191e810c19729de860ea",
  "traits": {
    "email": "peter@example.com"
  },
  "timestamp": "2026-01-01T00:00:00.000Z"
}

{
  "sourceId": "<SOURCE_ID>",
  "destinationId": "<SUPRSEND_DESTINATION_ID>",
  "title": "Drop events without userId",
  "description": "Anonymous users are not supported by SuprSend",
  "if": "length( userId ) < 1",
  "actions": [
    { "type": "DROP" }
  ],
  "enabled": true
}