# Userlens By Wudpecker Destination

## Destination Info

* Refer to it as **Userlens by Wudpecker** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.
* This destination is **Beta.**

[Userlens By Wudpecker](https://userlens.io/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) is the Next-Gen of Product Intelligence. Userlens combines quantitative data from products like Segment and PostHog, and qualitative feedback from products like Intercom and Wudpecker user interviews, to give you a full picture of how your users are using your products and features.

This destination is maintained by Wudpecker. For any issues with the destination, [contact the Wudpecker Support team](mailto:ankur@wudpecker.io).

## Getting started

1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) 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](https://app.userlens.io/settings?tab=integrations\&subtab=SEGMENT) in the Userlens app to copy the **API key**.
5. Enter the **API Key** in the Userlens destination settings in Segment.

## Supported methods

Userlens supports the following methods, as specified in the [Segment Spec](/docs/segment/connections/spec).

### Identify

Send [Identify](/docs/segment/connections/spec/identify) calls to identify users in Userlens. For example:

```js
analytics.identify('userId123', {
  email: 'john.doe@example.com'
});
```

Segment sends Identify calls to Userlens as an `identify` event.

### Track

Send [Track](/docs/segment/connections/spec/track) calls to add events in Userlens. For example:

```js
analytics.track('Login Button Clicked')
```

Segment sends Track calls to Userlens as a `track` event.

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/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.

> \[!NOTE]
>
> Real-time audience syncs to Userlens By Wudpecker  may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field   | Description           | Required | Type   |
| ------- | --------------------- | -------- | ------ |
| API Key | Your Userlens API key | Yes      | string |