Sync LINE Broadcast Results to Klaviyo and Put Them to Use

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.

You can find these event names in Klaviyo's metrics list and in each profile's activity. The LINE notification message events are recorded when you send LINE notification messages from a Klaviyo Flow. Rich Menu taps (Clicked LINE Rich Menu) are recorded when Rich Menu click tracking is enabled, along with the tapped menu name, button position, and link.

The coupon events are recorded when you distribute coupons with the Shopify integration's coupon campaigns. The campaign name and code are recorded too, so you can follow the response to your coupon campaigns on the Klaviyo side as well.

Converted via LINE records the outcomes measured by web conversion tracking that were judged as coming via LINE, together with the outcome's name and amount (value). Orders from the Shopify integration are recorded as LINE Attributed Order, so the same order is never counted twice. If you use the Send Custom Event action in a Workflow, the event name you set is recorded as a metric as is (see the "How to Use the Send Custom Event Action" article for details).

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.

Checking 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.

Analyzing 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)
• To see revenue via LINE, aggregate the "Value" (sum of order amounts) of LINE Attributed Order. Group by message_name or delivery_source to split it by campaign or by channel
• 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.

The Linked LINE Identity event records the linkage route (linkSource) and the URL of the page where the linkage started (pageUrl). Use them in the Flow trigger filter to branch, for example, to thank only customers who linked from the Shopify customer account, or to send a dedicated coupon to customers who linked from a specific landing page. The Unlinked LINE Identity event also records the URL of the page where the unlinking happened (pageUrl).

The Followed LINE Account event records the friend-add route (linkSource), the QR code or CTA placement (qrCodeId, qrCodeName), and the URL of the page where the friend add started (pageUrl). Use them for branching driven by the acquisition route, such as splitting your welcome Flow to target only customers added through the website friend-add CTA.

Checking revenue via LINE in Klaviyo

Orders via LINE are recorded on the Klaviyo profile as a LINE Attributed Order event with the order amount. Aggregate this event in Klaviyo's Metrics, Custom Reports, or dashboards, and you'll see revenue via LINE side by side with your email revenue inside Klaviyo.

How an order is judged as via LINE

When a Shopify order is placed within 5 days of a click on a link in a LINE message, the order is attributed to the last message clicked (last click). The scope and prerequisites are as follows.

• Orders in scope: orders imported through the Shopify integration. Outcomes outside Shopify are recorded by web conversion tracking as Converted via LINE
• Clicks in scope: link clicks in Broadcasts, sends via Klaviyo Flows, Workflows, and Auto Send Messages. Opens and Rich Menu taps don't count
• Prerequisites: the Shopify integration and Klaviyo ID linkage (the profile linked to the LINE account) are set up
• Timing: the event is recorded once the attribution is final, so it appears 3–4 days after the order date. Cancelled orders aren't recorded

Properties recorded

The event carries the order amount and properties that show which send produced the order. You can group and filter by these properties in Klaviyo reports.

Where to see it in Klaviyo

• Metrics: open LINE Attributed Order under Analytics > Metrics to see a chart of the amount (Value) over time. Filter by message_name or delivery_source to narrow it down by campaign or channel
• Custom Reports: in "Single metric deep dive", group the Value of LINE Attributed Order by message_name or delivery_source to get revenue via LINE per campaign. In "Multi-metric report", put it next to Placed Order to compare it with email-attributed revenue in one view
• Dashboards: with a custom card under Analytics > Dashboards, you can keep the Value of LINE Attributed Order as a line or bar chart, right next to your email revenue cards
• Profiles: each customer's profile activity shows every order and its amount

Notes when reading the numbers

• This is a separate calculation from Klaviyo's standard revenue attribution (based on email and SMS opens and clicks). Revenue via LINE isn't included in the Conversion value of the Flows performance report
• Email attribution counts orders within 5 days of an open or click, while LINE attribution counts orders within 5 days of a click, so the same order can appear under both email and LINE
• To see ROI, set the revenue from this event against your LINE messaging fees and subscription costs. Klaviyo holds cost data for SMS only

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 don't work

Common issues with event sync and how to address them are listed below.