Zalera works where your team already works.
Connect your Braze or Klaviyo account in minutes. No data warehouse required. No migration. No new flows to build.
All integrations
Braze
Native two-way sync
Read campaign performance, user attributes, and custom events. Write variant decisions back as Braze custom attributes for dynamic content filtering.
Klaviyo
Native two-way sync
Read profile data, flow performance, and event history. Attach decision properties to profiles before flow triggers for conditional content splits.
Segment
Customer event streams
Stream behavioral events into Zalera for richer per-person context beyond what the CRM alone captures.
Amplitude
Behavioral analytics
Pull product-usage signals to enhance lifecycle decision scoring with engagement data from inside your product.
Shopify
Purchase history
Feed order history, product category affinity, and purchase frequency into the decision model for DTC lifecycle flows.
Stripe
Subscription data
Incorporate billing lifecycle stage (trial, active, at-risk) as a behavioral signal for SaaS lifecycle decisions.
Braze integration
Zalera connects to Braze via the REST API and the Connected Content framework. It reads campaign performance data, user attribute history, and the custom events your team has already instrumented.
What Zalera reads from Braze: email click and open rates, push notification response rates, custom events (purchase, cart_abandon, page_view), user attributes, last-seen timestamps.
What Zalera writes back to Braze: a single custom attribute per user, zlr_variant_decision, containing the selected variant identifier. Your Braze content blocks filter on this attribute to render the correct message copy.
Use cases
- Dynamic content blocks in campaign emails, selected per recipient at send time
- Send-time variant optimization for promotional campaigns with 3 or more variants
- Dormant user re-engagement flows with per-person messaging tailored to lapse depth
- Post-purchase upsell flows with variant selected based on purchase category history
Klaviyo integration
Zalera integrates with Klaviyo through the Profiles and Events API. It reads behavioral history stored on each Klaviyo profile and attaches the variant decision as a profile property before your flows trigger.
What Zalera reads from Klaviyo: profile properties, event history (Placed Order, Viewed Product, Clicked Email), flow engagement metrics, segment membership history.
What Zalera writes back: a profile property zlr_variant set before the flow fires. Your Klaviyo flow adds one conditional split branch on this property. No new flows required, just one extra branch in an existing flow.
Use cases
- Abandoned cart flows with variant subject line selected by purchase-recency signal
- Win-back flows with message depth (gentle vs direct) driven by lapse duration model
- Welcome series variant routing based on acquisition channel and first-session behavior
- Replenishment flows with timing variant tuned by prior purchase cycle frequency
One integration point. No new infrastructure.
Zalera sits between your customer data and your send step, handling the decision so your CRM handles the delivery.
Connect your first integration in under 10 minutes.
No engineering required. A lifecycle marketer can complete the setup.