Klaviyo setup

Overview

Klaviyo ingests ecommerce and lifecycle events for segmentation and flows. TrackLayer forwards hashed identifiers, suppresses records without email/SMS consent, and maps catalog fields to Klaviyo’s expected payloads.

Steps

1. Create a private API key in Klaviyo with Profiles and Events scopes.
2. Add the TrackLayer Klaviyo destination; paste the key and choose your account region (US vs EU).
3. Map Purchase, FulfilledOrder, and Lead as starting events—add Unsubscribe once compliance hooks exist.

{
  "profile": {
    "email": "traits.email_sha256",
    "phone": "traits.phone_e164"
  },
  "metric": "Ordered Product",
  "properties": {
    "ItemName": "properties.product_name"
  }
}

4. Use Klaviyo’s Metrics activity view alongside TrackLayer delivery receipts to confirm latency under two minutes.

Troubleshooting

• Missing profiles: confirm identify merges happen before transactional events.
• Duplicate metrics: dedupe with event_id at TrackLayer—Klaviyo honors external ids when supplied.
• EU accounts must target the EU host; flip the region toggle instead of changing keys manually.