Klaviyo wiring guide
Connect Arcanum Engine and Hollow Reserve playbooks to Klaviyo customer flows without replacing Klaviyo as your ESP.
Arcanum apps send trigger events to Klaviyo. You build flows, segments, and campaigns in Klaviyo — apps do not replace your ESP or email clients directly. Engine alerts your team and optionally emits lifecycle events; Klaviyo sends shopper or client email when your flows are live.
How it works
- Connect Klaviyo in app Settings with Events write (and Profiles write for profile property updates).
- Enable Send Klaviyo event on a Growth playbook install, or enable Hollow Reserve journey sync (Professional+).
- Trigger a real event (test checkout, order, booking, or fulfillment delay).
- In Klaviyo, create a flow triggered by the metric name below.
- Use event properties in email templates — for example recoveryUrl or startsAt.
Arcanum Engine metrics (Growth)
| Playbook | Default metric | Profile properties (optional) |
|---|---|---|
| Winback Engine (abandoned checkout) | Arcanum Engine - Abandoned Checkout | arcanum_last_abandon_at, arcanum_abandon_cart_total, arcanum_customer_tag |
| VIP Recovery | Arcanum Engine - VIP Order | arcanum_vip, arcanum_last_vip_order_at, arcanum_vip_threshold |
| Review Accelerator | Arcanum Engine - Review Request | arcanum_review_due_at, arcanum_review_delay_hours, arcanum_review_order_id |
Lists vs segments — what condition to set
When saving VIP shoppers (or similar) for future campaigns, use a Klaviyo List or Segment — not both unless you intend to.
| Approach | Klaviyo object | Condition to set | How people enter |
|---|---|---|---|
| Flow-fed audience (recommended for VIP) | List | None — lists have no segment rules | Flow action Add to list after the thank-you email |
| Engine profile property | Segment | Properties about someone → arcanum_vip → equals → true | Engine Update Klaviyo profile properties ON on VIP Recovery |
| Dormant win-back | Segment | Placed Order zero times in last 90 days (and at least one order ever) | Klaviyo evaluates order history — not a flow Add to list |
Winback Engine — abandoned checkout flow
Trigger: Arcanum Engine - Abandoned Checkout. Event properties include recoveryUrl, cartTotal, checkoutKey, and customerTag. Requires Protected customer data approval for live checkout email.
- Install Winback Engine on Growth, connect Klaviyo, enable Send Klaviyo event.
- In Klaviyo, create a flow triggered by Arcanum Engine - Abandoned Checkout.
- Add a 1–4 hour wait so shoppers can complete checkout naturally.
- Email 1: Reminder with cart link from event property recoveryUrl.
- Email 2 (+24h): Social proof or incentive if still no order.
- Email 3 (+48h): Final nudge or alternate offer.
VIP Recovery flow
Trigger: Arcanum Engine - VIP Order. Event properties include orderId, orderTotal, customerTag, and ltvThreshold.
- Install VIP Recovery, enable Send Klaviyo event on paid orders above your threshold.
- Create a flow triggered by Arcanum Engine - VIP Order.
- Optional: Wait 15–30 minutes if your team Slack alert fires first.
- Email 1: VIP thank-you with order confirmation tone.
- Save VIP shoppers for later campaigns — pick one: (A) Create a List named VIP customers with no conditions, then Add to list in the flow; or (B) Create a Segment with Properties about someone → arcanum_vip equals true (requires Update Klaviyo profile properties ON).
Review Accelerator flow
Trigger: Arcanum Engine - Review Request. Fires after your configured delay hours post-fulfillment — not on the initial fulfillment webhook. Event properties include orderId and delayHours.
- Install Review Accelerator and set delay hours to match your shipping window.
- Enable Send Klaviyo event.
- Create a flow triggered by Arcanum Engine - Review Request.
- Email 1: Friendly review request with product context.
- Email 2 (+3d): Reminder if no review submitted.
Dormant Customer Winback — Klaviyo segment (not an Engine metric)
Dormant Customer Winback alerts your team weekly — it does not emit per-customer Klaviyo events. For client win-back email, build a Klaviyo segment (for example customers with no order in 90+ days) and run a scheduled campaign or segment-triggered flow. Use the Engine playbook as an ops nudge to review segment size.
Hollow Reserve journey metrics
Appointment-led brands use Hollow Reserve for booking lifecycle events — Appointment Booked, Deposit Paid, Completed, Cancelled, No-Show, and Journey Completed. Professional+ required. Engine commerce metrics and Reserve journey metrics are separate triggers.
Verify events
- Engine: abandon a test checkout, place a VIP order, or wait for review delay — check Results in Engine.
- Reserve: book a test appointment — check the client profile in Klaviyo.
- Confirm the exact metric name matches your flow trigger (copy from install wizard or opportunity card).
With Hollow Sentinel
When Hollow Sentinel is installed on the same store, one Klaviyo API key saved in any Arcanum app works for all — Engine sends commerce events; Reserve sends journey events; Sentinel monitors Placed Order volume and metric health.
Was this page helpful?