Klaviyo Technical Customization

This technical documentation provides a detailed breakdown of the data exchange and customization patterns for the TRIFFT + Klaviyo integration.

Document Details

Integration	TRIFFT + Klaviyo
Audience	Technical implementer / Solutions engineer / Marketing ops
Goal	Document data exchange, endpoints, webhooks, and customization patterns

Architecture

TRIFFT acts as the primary loyalty engine, capturing member state changes (points, tiers, and rewards) and emitting real-time events. These events and property updates are pushed to Klaviyo profiles, where they serve as triggers for automated lifecycle flows. Klaviyo-delivered messages (Email/SMS) then utilize deep links to drive members back to specific TRIFFT actions or touchpoints within the mobile app or web portal.

Identifiers and Consent

Primary identifier: The Email address is used as the common key to map members between TRIFFT and Klaviyo.
Consent mapping: TRIFFT tracks legal and loyalty-specific consents, while Klaviyo typically serves as the source of truth for marketing permissions (Email/SMS/Push).
Data ownership: TRIFFT is authoritative for all loyalty-related fields (points, tiers, coupons), while Klaviyo is authoritative for communication engagement metrics and marketing subscription status.

Data Mapping Table

Concept	TRIFFT	Klaviyo	Notes
Customer identifier	`email`	`$email`	Primary sync key.
Tier	`tier_name`	`trifft_tier_name`	Updated in real-time upon tier change.
Points balance	`points_balance`	`trifft_points_balance`	Synced as an integer property.
Coupon state	`member_coupon_id`	`trifft_active_coupon`	Tracks available or redeemed states.
Recommendation	N/A	`recommended_items`	Delivered via Klaviyo templates.

Standard Patterns

TRIFFT → Klaviyo: Syncing member properties and loyalty events (e.g., Points Earned, Voucher Claimed) to power dynamic segmentation and trigger automated flows.
Klaviyo → TRIFFT: Utilizing deep links within Klaviyo templates to trigger specific loyalty actions, such as opening a reward redemption screen or a news article in the app.
Personalization: Klaviyo pulls the latest loyalty context from TRIFFT property tags to render personalized "You have X points" or "You are Y points away from Gold" content.

Webhook/API Checklist

Security: API keys and private secrets must be stored securely within the TRIFFT Cockpit; ensure all endpoints use HTTPS.
Reliability: Webhook listeners should be configured with retry logic to manage transient network failures and maintain data parity.
Observability: Implementers should regularly monitor the integration logs in the TRIFFT Cockpit to track event delivery and error alerts.
Testing: Use staging payloads to verify event triggers before rolling out flows to the full production audience.

Customization Examples

Dynamic Perks: Trigger a Tier Upgraded message that dynamically lists specific perks (e.g., "Free Shipping") based on the member's new tier level.
Hyper-Local Offers: Use a member's favorite_location property in TRIFFT to filter and send personalized store-specific deals via Klaviyo SMS.
Abandoned Reward Reminders: Inject a list of a member's currently active but unredeemed coupon codes directly into a Klaviyo "Don't forget your discount" template.

Updated 4 days ago

Did this page help you?