Insider Source

1. From the Source catalog page click Add Source.
2. Search for Insider in the Sources Catalog, select click Insider, and click Add Source.
3. On the next screen, give the Source a name and add any labels to help you organize and filter your sources. You can give the source any name, but Segment recommends a name that reflects the source itself, as this name auto-populates the schema name. For example, the source name Insider creates the schema insider.
4. Click Add Source to save your settings.
5. After configuring settings, contact your Insider Customer Success Manager to set up the Segment Source Integration using your writekey.

Stream

Insider uses a server-side track method to send data to Segment. These events are then available in any destination that accepts server-side events, and available in a schema in your data warehouse, so you can query using SQL.

The default behavior is for Insider to pass the uuid (unique user ID) associated with the user as the userId. This is the same userId that Insider originally receives from the downstream destination with Segment. You can easily change the identity attribute to email, phone number, uuid, or any custom attribute. If the selected identifier is not present or you want to pass additional identifier under anonymousID, Insider is capable of sending a secondary selected identifier as anonymousID.

The table below lists events that Insider sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations.

The table below list the properties included in the events listed above.

Insider is capable of sending traits associated with a user in a track call to Segment. The traits will be passed along in the context object.

1
{
2
  "anonymousId": "c1da3de8-b4b7-4cf2-b496-6a271890ff40",
3
  "context": {
4
    "library": {
5
      "name": "Insider",
6
      "version": "1.0.0"
7
    },
8
    "traits": {
9
      "email": "f***.p***@h***.c***",
10
      "phone": "6***"
11
    }
12
  },
13
  "event": "Email Open",
14
  "integrations": {},
15
  "messageId": "api-2HgvQRYmsMWNlgqEuOKQmMWt5Wb",
16
  "originalTimestamp": "2022-11-17T21:12:00.335Z",
17
  "properties": {
18
    "campaign_id": "10305",
19
    "campaign_name": "20221117_midmonthsalethe1_cdsonp... Copy",
20
    "email": "f***.p***@h***.c***",
21
    "ip_address": "1***.2***.7***.1***",
22
    "user_agent": "Mozilla/5.0",
23
    "variation_id": "10305"
24
  },
25
  "receivedAt": "2022-11-17T21:12:03.554Z",
26
  "timestamp": "2022-11-17T21:12:00.335Z",
27
  "type": "track"
28
}

The table below list the traits that can be included in the events listed above.

Now that your Source is set up, you can connect it with Destinations.

Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don't appear, check the Event Delivery tool, and refer to the Destination docs for each tool for troubleshooting.

If there are any issues with how the events are arriving to Segment, contact the Insider support team.