Klaviyo platform core features
This domain tests the Klaviyo data model and the platform features you use before building flows or campaigns: account structure, integrations, profiles, events, catalogs, deliverability setup, and analytics.
Core rules
- A profile is the central record for a person, keyed by email or phone. Profile properties (first name, city, birthday, custom properties) describe the person.
- Events, called metrics in Klaviyo, record actions such as Placed Order, Started Checkout, or Viewed Product. Each event has a metric name, timestamp, unique ID, and event properties (for example, $value and items).
- Lists are static membership collections built by sign-up, import, or API. Segments are dynamic: they recalculate as profiles and events change.
- Integrations sync commerce data. A Shopify or similar integration creates profiles, events, and catalog items; the catalog powers product blocks and price-drop/back-in-stock triggers.
- Account setup includes roles/permissions, sending domains, and authentication (SPF, DKIM, DMARC). Sending-domain reputation affects inbox placement.
- Analytics and benchmarks aggregate revenue, opens, clicks, and flow performance; predictive properties such as CLV and churn risk are computed from history.
Worked example
A candidate sees an event named Placed Order with event property $value = 120 and profile property VIP = true. To build a segment of high-value buyers, use the event condition Placed Order $value greater than 100, not the profile property VIP. The $value belongs to the event; VIP belongs to the profile. If you need 'ever spent over $100,' Klaviyo can use a segment condition on the event's $value or a profile property if your integration maintains one. The reasoning: conditions must reference the object where the data lives.
Traps
Mixing profile and event properties; assuming a list updates automatically; treating metrics as profile fields; ignoring consent state when counting an audience.