Customer actions on LINE — such as opening or clicking a message, adding your account as a friend, or blocking it — are recorded as events on Klaviyo profiles, so you can use them in Segments, reports, and Flows. Once your Klaviyo integration is in place, these events are recorded automatically, so a good place to start is by telling the agent a goal like "I want to build a Segment in Klaviyo based on LINE reactions."
What Is LINE Event Sync
LINE event sync is a mechanism that records your customers' actions on LINE as events on their Klaviyo profiles.
Actions such as sending, opening, or clicking a LINE message, or adding or blocking your account as a friend, are recorded automatically on the matching ID-linked Klaviyo profile. On the Klaviyo side, you can treat these LINE events just like email opens and clicks, so you can see a customer's behavior across channels within a single profile.
If your integration is already set up, no configuration is needed. Whether the message goes out via a Lumo Message Broadcast, via a Klaviyo Flow, or as an automated Workflow send, LINE actions are recorded automatically each time they occur.
LINE Events Recorded in Klaviyo
A range of actions on LINE are recorded as Klaviyo events (metrics). The recorded event names are as follows.
| Action on LINE | Event name recorded in Klaviyo |
|---|---|
| Message sent | Sent LINE Message |
| Message delivered | Delivered LINE Message |
| Message send failed | Failed LINE Message |
| Message opened | Opened LINE Message |
| Message clicked | Clicked LINE Message |
| Added as friend | Followed LINE Account |
| Blocked | Blocked LINE Account |
| QR Code scanned | Scanned LINE QR Code |
| ID linkage completed | Linked LINE Identity |
You can find these event names in Klaviyo's metrics list and in each profile's activity.
About Open and Click Measurement
Opens (Opened LINE Message) come from Lumo's measurement mechanism and are different from "Read" in the LINE app. Opens and clicks are recorded for messages that include a trackable link or image. For text-only messages with nothing to measure, open and click events may not be recorded.
Check Whether Events Are Arriving
You can check whether events are being recorded from Klaviyo's metrics list.
Open the metrics list in Klaviyo's Analytics and filter the integration type to API, and LINE events such as Sent LINE Message appear. Open each metric to see a graph of counts over time and a list of recently received events (Activity feed). An event name is created automatically on the Klaviyo side when the first event arrives.
Analyze with Custom Reports
With Klaviyo's Custom Reports, you can analyze everything from LINE sends to opens and clicks side by side with your email metrics.
Open Custom Reports from Klaviyo's Analytics and create a report.
- To deep-dive into a single LINE metric, choose "Single metric deep dive"
- For a funnel comparison of Sent, Opened, and Clicked, or a comparison with email metrics, choose "Multi-metric report"
- For the aggregation unit, you can choose "Total" (total event count) or "Unique" (people-based)
- Reports you create can be exported to CSV or sent by email as recurring reports
If you add LINE metric cards to your dashboard, you can track the daily numbers at a glance. And on each customer's profile screen, email and LINE actions appear chronologically in a single timeline.
When you want to review LINE broadcast results within Lumo, ask the agent to "analyze the reactions to my recent broadcasts," and it will use Lumo's reports to give you a recap and suggest next moves. For checking sends, opens, and clicks per broadcast, Lumo's reports are laid out for easy reading.
Using Events to Build Segments
You can build Segments in Klaviyo using LINE events as conditions.
For example, you can create Segments based on LINE events, such as "people who opened a LINE message but did not click" or "people who clicked LINE in the last 30 days." By combining email reactions with LINE reactions — such as "people who did not open the email but clicked on LINE" — you can build more precise Segments, which helps with follow-up outreach and campaign targeting.
The Segments referred to here are Klaviyo Segments. They are different from the Segments you use in Lumo to narrow down the recipients of a Message Broadcast, so please be careful not to confuse the two.
Using Events as Flow Triggers
LINE events can be used as triggers that start a Klaviyo Flow.
For example, you can build automations driven by LINE actions, such as "send a follow-up email the next day when someone clicks a LINE message" or "switch to outreach on another channel when someone blocks you on LINE." You can run an entire scenario that moves back and forth between LINE and email entirely within a Klaviyo Flow.
About Revenue Measurement
Revenue (conversions) is not automatically tied to LINE events in Klaviyo.
Klaviyo's revenue attribution (attributed conversion) is a mechanism designed for email and SMS sent from Klaviyo, so it does not apply to LINE sends from Lumo. When you want to see the revenue impact of your LINE campaigns, combine LINE event counts with other methods, such as adding UTM parameters to the links you send and measuring with web analytics, or analyzing purchases by the Segment that reacted on LINE.
Conditions for Events to Be Recorded
LINE events are recorded only for customers whose IDs are linked.
If a Klaviyo profile and a LINE friend are not ID-linked, there is no way to identify which profile the event should be recorded on, so the event is not recorded. If you want to use LINE actions in Klaviyo, start by setting up ID linkage.
When Things Aren't Working
Common issues with event sync and how to address them are listed below.
| Symptom | What to check |
|---|---|
| Events are not recorded in Klaviyo | Check whether the customer in question is ID-linked. Actions by customers who are not linked are not recorded |
| Clicks and opens are not recorded | Opens and clicks are recorded for messages that include a trackable link or image. They may not be recorded for messages with nothing to measure |
| Open counts do not match "Read" in the LINE app | Opens come from Lumo's measurement mechanism and are a different metric from LINE's "Read" |
| Events are not reflected in a Klaviyo Segment | After an event is recorded, it can take some time for Klaviyo to recalculate the Segment. Please wait a little while and check again |