You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

2mee Destination

Destination Info

Accepts Identify and Track calls.
Refer to it as 2mee in the Integrations object
This integration is partner owned. Please reach out to the partner's support for any issues.

2mee 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.

Getting Started

From the Destinations catalog page in the Segment App, click Add Destination.
Search for 2mee in the Destinations Catalog and it.
Click Configure 2mee.
Choose which Source should send data to the 2mee destination.
Go to 2mee and copy the API Key and Application ID from the 2mee Dashboard.
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.

Identify

Send Identify calls to check if a user exists within your application. For example:

1{
2      "type": "identify",
3      "userId": "<userId>"
4}

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 calls to track the actions your users perform.

Configure the HoloCapsule setting in the 2mee app.

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

1{
2      "type": "track",
3      "event": "<event_name>",
4      "userId": "<userId>"
5}

Segment sends Track calls to 2mee as a track event.

Engage

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.

(information)

Real-time to batch destination sync frequency

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.

Property nameTypeRequiredDescription

API Keystring

required

Application Idstring

required