Klaviyo

Authentication Type: API Key
Description: Track customer events and behaviors for email marketing and customer engagement.

Authentication

To authenticate, you'll need a Klaviyo API key. Learn how to create one in the Klaviyo Help Center.

Events

Track customer events and behaviors in Klaviyo.

Track Event

Track a customer event in Klaviyo for marketing automation. Requires at least email or phone in the profile.

Operation Type: Mutation (Write)

Parameters:

• event string (required): Name of the event to track (e.g. "Purchased Product", "Viewed Page")
• profile object (required): Customer profile information - at least one field must be non-empty
  • email string (nullable): Customer email address (leave empty if not available)
  • phone string (nullable): Customer phone number (leave empty if not available)
  • external_id string (nullable): External customer ID (leave empty if not available)
• properties array of objects (required): Additional event properties and metadata as key-value pairs
  • key string: Property name
  • value string: Property value
• time string (nullable): ISO 8601 timestamp of when the event occurred (leave empty to use current time)

Returns:

• eventId string: Unique identifier for the tracked event
• success boolean: Whether the event was successfully tracked

Example Usage:

{
  "event": "Purchased Product",
  "profile": {
    "email": "customer@example.com",
    "phone": "+1-555-123-4567",
    "external_id": "user_12345"
  },
  "properties": [
    {
      "key": "product_name",
      "value": "Premium Wireless Headphones"
    },
    {
      "key": "purchase_amount",
      "value": "299.99"
    },
    {
      "key": "currency",
      "value": "USD"
    },
    {
      "key": "category",
      "value": "Electronics"
    },
    {
      "key": "brand",
      "value": "AudioTech"
    }
  ],
  "time": "2024-01-15T14:30:00Z"
}

List Events

Query events from Klaviyo with optional filters for metric, profile, time range, and pagination.

Operation Type: Query (Read)

Parameters:

• eventId string (nullable): Fetch a single event by its Klaviyo event ID. When set, all other filters are ignored.
• metricName string (nullable): Exact metric (event type) name to filter by, e.g. "Zaymo Form Response - Completed Form". Resolved to a metric ID automatically.
• metricId string (nullable): Klaviyo metric ID to filter by. Takes precedence over metricName.
• profileId string (nullable): Klaviyo profile ID to filter by.
• email string (nullable): Profile email to filter by. Resolved to a profile ID; ignored if profileId is set.
• since string (nullable): ISO 8601 timestamp; only return events strictly after this time.
• limit number (nullable): Page size (default 50, max 1000).
• cursor string (nullable): Pagination cursor from a previous response.

Returns:

• events array of objects: Events, newest first.
  • id string: Stable Klaviyo event ID, suitable for deduplication.
  • uuid string (nullable): Event UUID.
  • datetime string (nullable): ISO 8601 timestamp of when the event occurred.
  • metricId string (nullable): Klaviyo metric ID for this event.
  • metricName string (nullable): Human-readable metric name.
  • profileId string (nullable): Klaviyo profile ID associated with the event.
  • email string (nullable): Profile email address.
  • properties object: Raw event properties exactly as stored in Klaviyo.
• nextCursor string (nullable): Cursor for the next page, or null if there are no more results.

Notes:

• Events are returned newest first.
• Default page size is 50; maximum is 1000.
• metricId takes precedence over metricName when both are provided.
• metricName is resolved by exact match; if no metric with that name exists, the tool errors with a bad request.
• email is resolved to a profile ID; if no profile matches, an empty list is returned.
• eventId fetches a single event and ignores all other filters.
• since must be a valid ISO 8601 timestamp; invalid values error. Only events strictly after the given time are returned.
• Event IDs are stable and suitable for deduplication.

Example Usage:

{
  "metricName": "Zaymo Form Response - Completed Form",
  "since": "2026-01-01T00:00:00Z",
  "limit": 50,
  "cursor": null
}

Common Use Cases

E-commerce Marketing Automation:

• Track purchase events with product details, amounts, and customer information for targeted follow-up campaigns
• Monitor cart abandonment and checkout behaviors to trigger recovery email sequences
• Record product views and browsing patterns to personalize product recommendations and marketing content

Customer Engagement Tracking:

• Track website interactions like page views, content downloads, and form submissions for lead scoring
• Monitor customer support interactions and satisfaction surveys to trigger appropriate follow-up communications
• Record subscription and preference changes to maintain accurate customer profiles for segmentation

Event-Driven Campaigns:

• Trigger welcome email series when customers complete registration or first purchase events
• Send personalized offers based on specific product categories or purchase amounts from tracked events
• Create behavioral segments using event properties like purchase frequency, average order value, and product preferences

Customer Journey Analytics:

• Track multi-touchpoint customer journeys from initial website visit through purchase completion
• Monitor customer lifecycle events like birthdays, anniversaries, and subscription renewals for targeted campaigns
• Analyze customer behavior patterns using event properties to optimize marketing timing and messaging