Use the Klaviyo Track API by POSTing to https://a.klaviyo.com/api/events/ (v3) with Authorization: Klaviyo-API-Key header and a payload containing data.type (event), data.attributes.metric.name, data.attributes.profile (with email or phone), and data.attributes.properties for event metadata
Track standard commerce events such as 'Placed Order', 'Ordered Product', 'Fulfilled Order', and 'Refunded Order' using Klaviyo's expected property schema so built-in flow templates and reports work without remapping
Track custom behavioral events (e.g., 'Viewed Size Guide', 'Used Coupon', 'Submitted Review') with arbitrary property dictionaries to power segmentation and personalization flows
Create profiles or update profile properties via POST /api/profiles/ or PATCH /api/profiles/{profile_id} to set custom attributes like loyalty_tier, total_spend, or preferred_category used for flow branching
Build Klaviyo flows in the dashboard triggered by your custom metric names, adding conditional splits based on event properties or profile attributes to personalize the messaging
Use the Klaviyo identify call alongside track calls to ensure events are tied to the correct profile, especially in server-side contexts where the cookie-based identity is unavailable
Known gotchas
Event property keys are case-sensitive and inconsistent naming (e.g., 'OrderValue' vs 'order_value') creates duplicate metrics that fragment reporting and flow logic
Server-side event tracking bypasses browser-based consent mechanisms; ensure you only track profiles that have consented to marketing in your CMP and privacy policy
Klaviyo rate limits the Track endpoint; high-order-volume periods (flash sales, Black Friday) can cause event ingestion delays — use a queue to buffer and retry on 429 responses
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp