Sherlock Destination

1. From the Segment web app, click Catalog.
2. Search for "Sherock" in the Catalog, select it, and choose which of your sources to connect the destination to.
3. Enter your Sherlock API Key in the Segment UI.
4. Start sending data!

Sherlock's system processes data for all tracking calls with the following notes.

When Sherlock receives page calls, they record a Viewed Page event. Sherlock sets a Viewed Page: Page Name property on it with the name from the page call.

Similarly when Sherlock receives a screen call, they record a Viewed Screen event with a Viewed Screen: Screen Name property.

When Sherlock receives a group call, they record all traits specified for the group. They also assign a Group ID trait to to the user indicating membership.

When they receive an alias call, they record an alias for the specified userId and previousId. Data under both names are then merged into a single record.

Sherlock's system flattens nested property and trait values into key/value pairs. Consider an object:

1
{
2
  "id": 42,
3
  "item": {
4
    "name": "Hat",
5
    "details": {
6
      "color": "red",
7
      "size": "small"
8
    }
9
  }
10
}

This would be flattened into pairs with keys for each path delimited by .:

1
{
2
  "id": 42,
3
  "item.name": "Hat",
4
  "item.details.color": "red",
5
  "item.details.size": "small"
6
}

Array values are unsupported and ignored by Sherlock's system.

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.