Klaviyo Integration
Klaviyo Integration
Klaviyo Integration
This section provides everything you need to know to setup your Klaviyo Integration with LTV.ai.
This section provides everything you need to know to setup your Klaviyo Integration with LTV.ai.
This section provides everything you need to know to setup your Klaviyo Integration with LTV.ai.
Overview
The Klaviyo integration establishes a two-way data sync between LTV.ai and Klaviyo.
Data is imported from Klaviyo into LTV.ai's emails for personalization.
Engagement events from LTV.ai are pushed into Klaviyo for reporting and segmentation.
Unsubscribes are synchronized in both directions
The Klaviyo integration establishes a two-way data sync between LTV.ai and Klaviyo.
Data is imported from Klaviyo into LTV.ai's emails for personalization.
Engagement events from LTV.ai are pushed into Klaviyo for reporting and segmentation.
Unsubscribes are synchronized in both directions
The Klaviyo integration establishes a two-way data sync between LTV.ai and Klaviyo.
Data is imported from Klaviyo into LTV.ai's emails for personalization.
Engagement events from LTV.ai are pushed into Klaviyo for reporting and segmentation.
Unsubscribes are synchronized in both directions
Data Usage
Input (from Klaviyo → LTV.ai): profiles, lists, segments, and standard event objects (purchases, names, engagement history).
Processing (inside LTV.ai):
Personally identifiable data (PII) is not stored in LTV.ai.
Data is retrieved from Klaviyo at send time only, inserted directly into the generated 1-1 email.
LTV.ai models use only aggregated, non-PII data to construct 1-1 messages and personalization logic.
Example: the model knows “{{brand}} customer in Chicago purchased shoes last week” but does not persist that user’s email, name, or address.
Output (from LTV.ai → Klaviyo): engagement events (opens, clicks, replies) and zero-party data captured during conversations.
Input (from Klaviyo → LTV.ai): profiles, lists, segments, and standard event objects (purchases, names, engagement history).
Processing (inside LTV.ai):
Personally identifiable data (PII) is not stored in LTV.ai.
Data is retrieved from Klaviyo at send time only, inserted directly into the generated 1-1 email.
LTV.ai models use only aggregated, non-PII data to construct 1-1 messages and personalization logic.
Example: the model knows “{{brand}} customer in Chicago purchased shoes last week” but does not persist that user’s email, name, or address.
Output (from LTV.ai → Klaviyo): engagement events (opens, clicks, replies) and zero-party data captured during conversations.
Input (from Klaviyo → LTV.ai): profiles, lists, segments, and standard event objects (purchases, names, engagement history).
Processing (inside LTV.ai):
Personally identifiable data (PII) is not stored in LTV.ai.
Data is retrieved from Klaviyo at send time only, inserted directly into the generated 1-1 email.
LTV.ai models use only aggregated, non-PII data to construct 1-1 messages and personalization logic.
Example: the model knows “{{brand}} customer in Chicago purchased shoes last week” but does not persist that user’s email, name, or address.
Output (from LTV.ai → Klaviyo): engagement events (opens, clicks, replies) and zero-party data captured during conversations.
Setup
Requirements:
Klaviyo Public API Key (Site ID)
Klaviyo Private API Key with read and write permissions
Procedure:
Log into Klaviyo.
Navigate to Account → Settings → API Keys.
Copy the Public API Key (Site ID)
Requirements:
Klaviyo Public API Key (Site ID)
Klaviyo Private API Key with read and write permissions
Procedure:
Log into Klaviyo.
Navigate to Account → Settings → API Keys.
Copy the Public API Key (Site ID)
Requirements:
Klaviyo Public API Key (Site ID)
Klaviyo Private API Key with read and write permissions
Procedure:
Log into Klaviyo.
Navigate to Account → Settings → API Keys.
Copy the Public API Key (Site ID)
Generate a new Private API Key.
Assign both read and write scopes.
Copy the value immediately; it cannot be retrieved later.
Provide both values (Site ID + Private API Key) to your assigned LTV.ai CSM.
At this point, the integration is active. No further configuration is required.
Reference: Klaviyo API Key Documentation ↗
Generate a new Private API Key.
Assign both read and write scopes.
Copy the value immediately; it cannot be retrieved later.
Provide both values (Site ID + Private API Key) to your assigned LTV.ai CSM.
At this point, the integration is active. No further configuration is required.
Reference: Klaviyo API Key Documentation ↗
Generate a new Private API Key.
Assign both read and write scopes.
Copy the value immediately; it cannot be retrieved later.
Provide both values (Site ID + Private API Key) to your assigned LTV.ai CSM.
At this point, the integration is active. No further configuration is required.
Reference: Klaviyo API Key Documentation ↗
Cancelation
Notify your LTV.ai CSM to disable the integration.
Optionally, revoke the private API key in Klaviyo under Account → Settings → API Keys.
Once disabled, no further data is transferred. Previously synced data remains unless explicit deletion is requested.
Notify your LTV.ai CSM to disable the integration.
Optionally, revoke the private API key in Klaviyo under Account → Settings → API Keys.
Once disabled, no further data is transferred. Previously synced data remains unless explicit deletion is requested.
Notify your LTV.ai CSM to disable the integration.
Optionally, revoke the private API key in Klaviyo under Account → Settings → API Keys.
Once disabled, no further data is transferred. Previously synced data remains unless explicit deletion is requested.
©2025 LTV.ai
©2025 LTV.ai
©2025 LTV.ai
©2025 LTV.ai