How to Analyze and Push Events Data Back to Klaviyo

Overview

View performance for a configured automation and push delivery/conversion events back into Klaviyo for segmentation and reporting.

Learning Objectives

• View analytics for a configured automation in Klaviyo

• Enable event pushback from KwikEngage to Klaviyo

• Create a private API key in Klaviyo

• Build a segment in Klaviyo using returned events

Prerequisites

• A live automation/flow in Klaviyo

• Admin access in Klaviyo

• Access to KwikEngage configuration

Step-by-Step Guide

1) View Automation Analytics (KwikEngage)

1. In Klaviyo, open Analytics → Klaviyo Automations (or Flows depending on your UI).

2. Locate your automation by name.

2) Enable Delivery Response Webhook (KwikEngage)

1. In KwikEngage → Configurations → Klaviyo Integration, toggle Delivery Response Webhook: ON.

2. You’ll need a Klaviyo private API key (next step) so KwikEngage can write events back to Klaviyo.

3) Create a Private API Key (Klaviyo)

1. Go to Klaviyo → Settings → Account → API Keys.

2. Create Private API Key with custom scope: read/write for Events (avoid full access).

3. Copy the key and paste it into the Klaviyo Integration settings in KwikEngage.

4) Create a Segment Using Returned Events (Klaviyo)

1. In Klaviyo → Lists & Segments → Create Segment.

2. Add filters that reference the specific KwikEngage events or flow name you pushed back.

   • Example segment name: “WhatsApp – Read”

   • Example filter: people who performed event(s) from “KwikEngage – ABC Cart” flow.

5) Validate

• Trigger a test send → confirm events appear on the Profile → Activity Feed and in your segment preview.

• Recheck the automation dashboard to ensure metrics line up with returned events.

Technical Details

• Webhook origin: KwikEngage (Delivery Response Webhook)

• Destination: Klaviyo Events API (via your Private API Key)

• Minimum scopes: Events read/write (use custom access rather than full access)

• Usage: Returned events power segments, flows/branches, and analytics

Troubleshooting

• No events in Klaviyo:

  • Verify Delivery Response Webhook = ON in KwikEngage.

  • Confirm the private key is valid and has events write permissions.

  • Check for typos in flow/event names used in filters.

• Analytics panel empty:

  • Ensure you selected the correct automation name.

  • Confirm the automation is live and has recent traffic.

• Segments not populating:

  • Make sure your filters reference the exact event name/property.

  • Confirm incoming events are attached to the correct profile (email/phone ID match).

Best Practices

• Least privilege: Use custom-scoped API keys (events read/write only). Rotate keys periodically.

• Consistent naming: Keep event and flow names consistent across KwikEngage and Klaviyo.

• Auditability: Where possible, include timestamp/source metadata in returned events.

• Test first: Use a small test profile/segment before scaling.

Key Takeaways

Turn on the Delivery Response Webhook in KwikEngage, authenticate with a custom-scoped Klaviyo private API key, verify events in Klaviyo, and build segments and reports on those events to close the analytics loop.