Skip to content
Integrations

CRM · Ready to build

Klaviyo

Email and SMS engagement, campaign activity, and marketing profile attributes synced with Klaviyo, so every agent works from the same guest context.

Klaviyo

What Casa Layer reads

  • Email and SMS engagement
  • Campaign activity
  • Profile attributes

The connection

Reads via
Klaviyo API
Direction
Casa Layer reads guest data from your Klaviyo. What it can do there is scoped by the credentials you issue, and every connection live today reads only.
Status
Ready to build

What this takes from you

Vendor approval
We confirm this with Klaviyo before any work starts. Some vendors open their API to any customer, others require a signed partner agreement first. We tell you in writing which one applies to you.
Cost to you
Nothing from us. Building and running the connection is part of the platform licence, not a separate integration fee. If Klaviyo charges for API or partner access, that price is theirs to set and we give you the number before anything is built.
Time to first record
About three weeks from your go-ahead, once Klaviyo access is approved. We scope the exact date with you before you commit to anything.
What we do not read
We read guest context and nothing else. Whatever the API exposes, we do not pull:
  • Payment card numbers, CVV codes, or anything else in PCI DSS scope
  • Rate negotiation, contract, and commercial terms
  • Staff, payroll, and HR records
  • Anything outside the read scope you approve before we connect

How it works

Connect Klaviyo, then share a Casa table with a Klaviyo list from the table share menu. When someone joins or leaves the table, Klaviyo list membership stays in sync.

What syncs

Master-profile members as Klaviyo profiles, list membership adds and removes, and email as the join key.

Use cases

Run marketing audiences from the hotel-owned identity instead of a PMS export, so segments stay current as guests move through Casa tables.

See Casa Layer in practice

Klaviyo is not connected for anyone yet, but the API exists and we have the pattern: about three weeks from your go-ahead. A 20-minute demo shows the layer running on a built connection, and we scope Klaviyo against your stack on the same call.

Book a 20-minute demo