The user's distinct_id. If you are sending Events to Mixpanel in addition to Profiles, this property value should be identical to the distinct_id property attached to events so that you can connect events to profiles. Tell me more about distinct_id.

Properties contain information about the profile. For example, for a user profile, properties can be things like an email address, where they came from, or their age. These properties allow you to drill down to very specific segments of users/customers and learn more.

Properties are sent as key-value pairs where the key is the property name and the value is the property value. Tell me more about properties.

Certain property keys are special/reserved. For example, if you include the $email property, you can start sending targeted email notifications using Mixpanel's Notifications product. Other examples of special properties are $name, $phone and $unsubscribed. Learn more about Special/Reserved properties .

Select a list to add this contact to in Autopilot. This can be used to categorize contacts, or with the "added to list" trigger to trigger journeys.

Email address of the contact. Autopilot de-duplicates based on email address. If you provide a contact with an email address that already exists in Autopilot, the contact will be updated with any new fields that you provide.

The first name of the contact.

Last name of the contact.

Formal title for the contact, e.g. Mr. Mrs., Dr.

The company position of the contact, e.g. "CEO", "CMO", "Sales Engineer", "Engineer".

Map this field to the Trigger's Email field, and any contact with this email will be deleted in Autopilot.

A name for this Event. For example, 'Brand Mentioned in Tweet' or 'Payment Made'. Tell me more about Events.

A way to uniquely identify your users (or more generally, profiles). If you are sending Profiles to Mixpanel in addition to events, this property value should be identical to the Distinct ID property attached to the Profile so that you can connect events to people records. Tell me more about distinct_id.

Event Properties are bits of extra information that you send along with your Events describing the details of that action. They are usually specific to the Event they’re describing and don’t apply universally to other Events. Leveraging Event Properties allows you to conduct deeper analysis to better understand user behavior for a specific action. For example, a 'Song Added to Playlist' event could have 'Artist' and 'Playlist' as the properties. Properties are sent as key-value pairs where the key is the property name and the value is the property value. Tell me more about properties.

Use the + sign to add properties to this event.

Select a list to add this contact to in Autopilot. This can be used to categorize contacts, or with the "added to list" trigger to trigger journeys.

Email address of the contact. Autopilot de-duplicates based on email address. If you provide a contact with an email address that already exists in Autopilot, the contact will be updated with any new fields that you provide.

The first name of the contact.

Last name of the contact.

Formal title for the contact, e.g. Mr. Mrs., Dr.

The company position of the contact, e.g. "CEO", "CMO", "Sales Engineer", "Engineer".

Map this field to the Trigger's Email field, and any contact with this email will be unsubscribed in Autopilot.