# 2mee Destination

## Destination Info

* Accepts [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **2mee** 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.

[2mee](https://2mee.com) is a Human Hologram platform that automatically cuts the person out from the background, removing the visual clutter, and places them in the familiar context of your phone or website so that they dominate the screen.

This destination is maintained by 2mee. For any issues with the destination, [contact the 2mee Support team](mailto:support@2mee.com).

## Getting Started

1. From the Destinations catalog page in the Segment App, click **Add Destination**.
2. Search for **2mee** in the Destinations Catalog and it.
3. Click **Configure 2mee**.
4. Choose which Source should send data to the 2mee destination.
5. Go to 2mee and copy the [API Key and Application ID](https://docs.2mee.com/documentation/segment) from the 2mee Dashboard.
6. Go back to Segment and paste the API Key and Application ID you just copied in the 2mee destination settings. Make sure to paste the API Key in this format: `Bearer <API Key>`.

## Supported methods

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

### Identify

Send [Identify](/docs/segment/connections/spec/identify/) calls to check if a user exists within your application. For example:

```js
{
      "type": "identify",
      "userId": "<userId>"
}
```

Segment sends Identify calls to 2mee as an `identify` event.

Identify calls with a `userId` not mapped to a device fails with a `400` error code.

## Track

Send [Track](/docs/segment/connections/spec/track/) calls to track the actions your users perform.

Configure the HoloCapsule setting in the [2mee](https://go.2mee.com/) app.

Segment requires the `userId`. Track calls without a `userId` or with a `userId` not mapped to a device fail with a `400` code.

```js
{
      "type": "track",
      "event": "<event_name>",
      "userId": "<userId>"
}
```

Segment sends Track calls to 2mee 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 2mee  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        | Login to your 2Mee account, find the key under Profile section.  | Yes      | string |
| Application Id | Login to your 2Mee account, get Company Id from Profile section. | Yes      | string |