Userlens By Wudpecker Destination

1. From your workspace's Destination catalog page search for Userlens.
2. Select Userlens and click Add Destination.
3. Select an existing Source to connect to the Userlens destination.
4. Go to the Userlens settings in the Userlens app to copy the API key.
5. Enter the API Key in the Userlens destination settings in Segment.

Userlens supports the following methods, as specified in the Segment Spec.

Send Identify calls to identify users in Userlens. For example:

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

Segment sends Identify calls to Userlens as an identify event.

Send Track calls to add events in Userlens. For example:

analytics.track('Login Button Clicked')

Segment sends Track calls to Userlens as a track event.

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.