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 .

A publicly accessible link where we can grab the image.

Enter a Property on the left and a Value on the right.

Determines which App Extensions will appear in the dropdown below.

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 an existing metric, or enter a custom value to create a new metric.

The email of the person who triggered this event.

A unique identifier you can define for an event.

A numeric value to associate with this event (e.g. the dollar value of a purchase).

Enter a Property on the left and a Value on the right.

For double opt-in lists, a confirmation email will be sent to the subscriber when this Zap runs. For single opt-in lists, subscribers will be added immediately. Learn More

A publicly accessible link where we can grab the image.

Enter a Property on the left and a Value on the right.

API docs for Klaviyo are located here https://developers.klaviyo.com/en/v1-2/reference/api-overview

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.

A publicly accessible link where we can grab the image.

Enter a Property on the left and a Value on the right.