Event

Klaviyo lets you deliver amazing experiences across email and other owned channels.

The Klaviyo Create Event API is used to send event & profile data from mParticle to your Klaviyo account.

Prerequisites

In order to enable the mParticle integration with Klaviyo, you will need the Public API Key from your Klaviyo account, and a Private API Key with the events:write permission.

Supported Event Types

• Application State Transition
• Commerce
• Custom
• Screen View
• Session Start
• Session End

Supported User Identities

• Email
• Other - Other10
• Mobile Number
• Phone Number 2
• Phone Number 3

Supported Platforms

• iOS
• Android
• MobileWeb
• tvOS
• Roku
• Custom Feeds
• Alexa
• SmartTV
• FireTV
• Xbox

Data Processing Notes

User Identities:

• All events sent to Klaviyo must contain at least one user identity
• Phone number and Email address will be included based on the identity types chosen in the connection settings
• Note that phone numbers must be provided in E.164 format, and sending the $country user attribute (in ISO 3166-1 alpha-3 format) will help format phone numbers if country code is not provided

Sending the following attributes may unlock additional functionality in Klaviyo:

User Attributes & Additional Identifiers:

• $external_id
• $anonymous
• $exchange_id
• $first_name
• $last_name
• $organization
• $title
• $address1
• $address2
• $city
• $latitude
• $longitude
• $region
• $zip
• $country (expected format: ISO 3166-1 alpha-3)
• $timezone
• $ip
• $image

Event Attributes:

• $event_id
• $value

Event Configuration Settings

Setting Name	Data Type	Required	Default Value	Description
Public API Key	string	Yes		Your Public API Key / Site ID is a short alphanumeric value that identifies your Klaviyo Account.
Private API Key	string	Yes		A Private API Key from your Klaviyo account with the events:write scope.

Connection Settings

Setting Name	Data Type	Required	Default Value	Description
External Email Identity Type	enum	Yes	Email	The email identity type to forward to Klaviyo
Phone Identifier	enum	Yes	Mobile Number	The phone identity type to forward to Klaviyo. Expected format: E.164
Consent Mapping	Custom Field	No		A mapping of mParticle consents to Klaviyo consents. Note that consent removal is not currently supported.
Property Mapping	Custom Field	No		A mapping of mParticle user attributes to Klaviyo reserved customer properties. Note that mapped attributes must also be shared with the connection.