Klaviyo integration with Amperity

Q: How does Amperity integrate with Klaviyo?

Amperity sends email-keyed audience lists and optional profile attributes through the Klaviyo REST API. A separate source connector imports engagement metrics and list membership. Configure each direction for the data and schedule your workflow needs.

Q: Which customer fields can Amperity send to Klaviyo?

Supported mappings include standard profile attributes, location fields, and custom properties. For example, amperity_id can be aliased to external_id. Columns with NULL values explicitly clear the corresponding field, so validate your query before activation.

Q: Can Amperity import Klaviyo email engagement?

Yes. The source imports email metrics and list membership, with documented engagement types including opens, clicks, bounces, opt-ins, and unsubscribes. These are inbound records, distinct from the outbound list and profile update workflow.

Q: Does updating a Klaviyo list subscribe or delete customers?

List membership is distinct from consent and profile deletion. Klaviyo documents that removing a profile from a list does not change subscription status. Do not use audience membership changes as a substitute for consent management or a profile-deletion workflow.

Q: Is the Klaviyo integration real time?

The documented workflows run orchestrations and scheduled source couriers. Profile updates are subject to Klaviyo endpoint rate limits. Choose schedules and estimate completion time for your audience size; the connector documentation does not promise real-time delivery.

Send Amperity audiences and customer attributes to Klaviyo through its REST API to personalize outreach. Separately, import Klaviyo engagement and list membership into Amperity to inform customer understanding and future audience decisions.

Get a demo See the Klaviyo docs

Audience list sync • Profile attributes • Engagement import

Reach customers using purchase and relationship context available in Amperity.

Personalize Klaviyo outreach with selected customer profile attributes.

Refresh audience membership as your Amperity query results change.

Inform future audiences with imported Klaviyo engagement history.

How Amperity and Klaviyo connect

Authorize the destination. Connect Amperity to Klaviyo using a private API key or OAuth.
Choose the audience and attributes. Build an Amperity query with email as the audience primary key and add optional customer fields.
Update the Klaviyo list. Run an orchestration to send query results through the Klaviyo REST API; list membership is updated to match the query.
Import engagement separately. Configure the Klaviyo source courier to pull email metrics and list membership into Amperity on its own schedule.

Outbound list and profile updates and inbound engagement imports use separate configurations and schedules.

What the Klaviyo integration supports

Capability	Supported behavior
Direction and method	Outbound: Klaviyo REST API. Inbound: separately configured source courier using the events API.
Outbound data and identity	Audience lists keyed by email; optional profile attributes via Update Profile. Existing or new list name supported.
Inbound data	Klaviyo_Email_Metrics and Klaviyo_List_Membership tables; eventUuid and id are their respective primary keys.
Authentication	Private API key or OAuth; separate read scopes for source and write scopes for destination.
Refresh and limits	Run orchestrations and schedule source courier groups. Current Update Profile limits: 75 requests/second burst, 750/minute steady; not an end-to-end throughput guarantee.

How Klaviyo profile fields map

Query column names determine the outbound mapping. Enable profile updates when sending attributes alongside list membership.

Object	Mapping
Profile	email → attributes.email; given_name AS first_name → attributes.first_name; amperity_id AS external_id → attributes.external_id.
Location	address1, city, region, and zip → attributes.location fields.
Custom properties	Other query columns → attributes.properties. NULL columns → meta.patch_properties.unset to clear fields.
Audience list	Email-keyed query results → membership in the named Klaviyo list. Membership changes are separate from consent.

Amperity field mapping • Klaviyo profile API • Klaviyo lists API

Put customer context to work in Klaviyo

Follow up with store shoppers using purchase context

Build an audience of customers whose store purchases qualify them for a relevant follow-up, using transaction data already available in Amperity. Send their email addresses with selected attributes, such as product or most recent purchase date, to Klaviyo. Your team can use those properties to tailor messaging in Klaviyo, bringing offline purchase context into the next interaction. Check current consent in Klaviyo before sending.

Build a win-back audience with purchase and engagement history

Import Klaviyo email metrics and combine them with available purchase history in Amperity to distinguish recent buyers from customers who may need a different message. Build a query for the audience your team chooses to re-engage, then update its Klaviyo list. Use the imported engagement records to inform that decision rather than treating an email open as a purchase. Configure the source and destination independently, with schedules appropriate to your workflow.

Set up and validate the Klaviyo connection

An Amperity operator configures the destination and credentials. A private key needs lists:write and profiles:write scopes; OAuth is also supported. Test a sample audience in a sandbox, verify membership and profile fields in Klaviyo, and promote the configuration after validation.

For inbound data, configure a separate source courier with Email Metrics and List Membership selected. Private-key scopes are events:read, lists:read, metrics:read, profiles:read, and segments:read; the source also supports OAuth. Set its courier group schedule independently.

Filter audiences using available consent data in Amperity, then verify current consent in Klaviyo immediately before sending. Amperity is not the source of truth for email consent. Review endpoint limits before planning a large profile update.

Configure the source Configure destination

Klaviyo integration FAQs

How does Amperity integrate with Klaviyo?

Which customer fields can Amperity send to Klaviyo?

Can Amperity import Klaviyo email engagement?

Does updating a Klaviyo list subscribe or delete customers?

Is the Klaviyo integration real time?

Make your next Klaviyo audience more relevant

See how Amperity can help your team use customer history to choose who to reach and what context to send to Klaviyo.

Get a demo