Klaviyo sync brief

Klaviyo is best treated as a campaign and lifecycle system. Perkamo should remain the rules layer for points, levels and perks, while Klaviyo receives campaign traits or triggers after Perkamo computes customer state.

Planned native scope

• Sync selected Perkamo customer traits to Klaviyo profiles.
• Trigger campaigns when levels, perks or rewards change.
• Keep customer id and email mapping explicit.
• Show last sync status and last error in Console.
• Allow customers to choose which Perkamo effects are sent to Klaviyo.

This connector is under consideration because Klaviyo use cases vary widely by commerce stack, customer identity model and campaign process.

Available now

Use webhooks or backend jobs to sync campaign-ready data to Klaviyo.

• Use Webhooks for Perkamo effects.
• Read current customer state with GET /v1/customer/{user_id}.
• Review Security and keys before syncing customer data.

Design partner fit

This connector is a good fit when Perkamo state should drive lifecycle campaigns, VIP messaging or winback flows. Perkamo can help customers define which traits belong in Klaviyo and which reward logic should stay in Perkamo.