Intelligent Handshake®
Developer centerAPI keys

Klaviyo Egress

Intelligent Handshake® can egress real-time customer activity events directly into your Klaviyo account. Each time a tracked customer interaction occurs—a web visit, phone call, form submission, or other action— a Klaviyo event is posted with the associated customer profile and activity data.

To provision your Klaviyo egress, provide us with the items listed below.

Required

Private API Key

The Private API Key authorizes Intelligent Handshake® to post events to your Klaviyo account on your behalf. It is a string beginning with pk_.

  1. Log in to your Klaviyo account.
  2. Click your account name in the lower-left corner and select Settings.
  3. Open the API Keys tab.
  4. Under Private API Keys, click Create Private API Key.
  5. Give the key a name (e.g., Intelligent Handshake).
  6. Under Scopes, grant Full Access to Events, List, and Profiles, then click Create.
  7. Copy the key—it begins with pk_—and send it to your Intelligent Handshake® account manager.
Store this key securely. Klaviyo will not display the full key again after you navigate away from the creation screen.

The Private API Key must be scoped with Full Access to the following:

  • Events
  • List
  • Profiles

Data Shared with Klaviyo

Events are posted to the Klaviyo Events API. Each event carries profile data (who the customer is) and event properties (what the customer did).

Profile Fields

Klaviyo Field Source Notes
email Customer email address Primary profile identifier
phone_number Mobile or voice number (E.164 format) Used when available; mobile takes precedence over voice
external_id Intelligent Handshake® Person ID Enables cross-platform identity resolution
first_name / last_name Customer name Split automatically from full name
Location (city, region, country, zip, address) Customer home address Populated when address data is available

Event Properties

Depending on your licensed Intelligent Handshake® features, events may also include:

  • Page URL, page title, and referrer
  • UTM campaign tracking fields (Source, Medium, Campaign, Content, Term)
  • IP address and geolocation (latitude, longitude)
  • Device UID and user agent
  • Hashed email (MD5, SHA-1, SHA-256, SHA-512) for ad network matching
  • Segment code, index, and value
  • Place and product context

See Also