This article explains how to send transactional notifications such as order and shipping confirmations as LINE notification messages, triggered by a Klaviyo Flow. Notifications reach customers by phone number, even before they add your account as a friend.
What is a LINE Notification Message?
LINE notification messages are transaction-only messages certified by LY Corporation that can reach customers by phone number, even if they have not added your account as a friend.
LINE notification messages can reach customers before they add the account as a friend when the phone number and other LINE receiving requirements are met. This article covers the template type. Select a certified template, such as shipping or order confirmation, and merge the relevant order details.
Key points before you start:
- They are strictly for transactional notifications (purchases, shipping, reservations, and so on). Advertising and promotional use is not allowed
- Using them requires an application to and approval from LY Corporation
- Message layouts follow the certified templates. Free-form layouts are not available
What you need to use this feature
You need three things in place: a Klaviyo integration, approval to use LINE notification messages, and customer phone numbers.
This article covers LINE Official Accounts in Japan.
- Your LINE Official Account is approved to use LINE notification messages
- The Klaviyo integration is connected in Lumo
- The target Klaviyo profile has a phone number in international format (for example:
+819012345678)
LINE requires a matching phone number, permission to receive notifications, no block on the sending account, and any required SMS verification. Lumo requires the Enterprise plan. See application and receiving requirements.
Overview of the setup
You create one set of "LINE notification message + auto send message + Klaviyo Flow" for each type of notification.
| Step | What you create or configure | Where |
|---|---|---|
| 1 | Create a LINE notification message (template) | Lumo |
| 2 | Create an auto send message | Lumo |
| 3 | Get the Klaviyo Flow connection details | Lumo |
| 4 | Configure a webhook action in the Flow | Klaviyo |
| 5 | Test and go live | Klaviyo |
To send both order and shipping confirmations, create two of these sets.
Creating a LINE Notification Message
From the side menu, open "Automation" > "LINE Notification Messages" and create one from a certified template that fits your use case.
- Select "Create LINE Notification Message"
- Choose the region and template key. Typical choices are the shipping confirmation template for shipping notices, and the order or purchase confirmation template for order notices
- In the merge items, pick the item keys you want to show (tracking number, product name, total amount, and so on) and enter their display values. Use merge variables for values that change per order
- Choose a CTA button label and set its URL. For example, a "check delivery status" style button for shipping, or an "order history" style button for purchases
- If you use the emphasized item, keep its display text within 15 characters. When variables are used, the limit applies to the text after replacement. Anything beyond it is cut off with "…", so put values that must stay whole, such as tracking numbers, in an item instead
How to write merge variables
In display values and button URLs, use the format {{ data.keyName }} to merge order data passed from Klaviyo. You can also click the variable button ({ }) below the input field and choose from "Order details".
The main variables are listed below. Their values are supplied by Klaviyo through the JSON body you will get later from the Klaviyo Flow connection details.
| Variable | Content | Available triggers |
|---|---|---|
{{ data.orderNumber }} |
Order number | Placed Order / Fulfilled Order |
{{ data.orderDate }} |
Order date | Placed Order / Fulfilled Order |
{{ data.productName }} |
Product name (first item) | Placed Order / Fulfilled Order |
{{ data.totalPrice }} |
Total price | Placed Order / Fulfilled Order |
{{ data.orderStatusUrl }} |
Order status page URL | Placed Order / Fulfilled Order |
{{ data.trackingNumber }} |
Tracking number | Fulfilled Order only |
{{ data.shippedDate }} |
Shipped date | Fulfilled Order only |
{{ data.trackingUrl }} |
Delivery status page URL | Fulfilled Order only |
{{ data.email }} |
Customer's email address (URL-encoded) | Placed Order / Fulfilled Order |
- Write currency symbols in the display value itself (for example:
¥{{ data.totalPrice }}) - Shipping-related variables such as the tracking number have no value in a Placed Order flow. Do not use them in order confirmation templates
-
{{ data.email }}is URL-encoded, so you can use it directly as a parameter in a button URL. It is not suited for on-screen display
Creating an Auto Send Message
Choose "LINE notification message" as the message type and select the template you created.
- From the side menu, open "Automation" > "Auto-Send Messages" and create a new message
- Choose "LINE notification message" as the message type
- Select the LINE notification message you created as the template and save
An auto send message with a LINE notification message can't contain any other message types. One auto send message equals one notification.
Linking IDs when the notification button is tapped
Turn on "Link identity when the button is tapped" on the auto send message, and a customer who taps the notification button is linked to the Klaviyo profile the notification was sent for. You don't need to put an ID linking URL in the button.
What customers and your team see
Customers tap the button, agree on the LINE screen, and go straight to the destination set on the button.
- The customer taps the notification button on a smartphone
- The LINE Login consent screen appears. Customers who aren't friends yet also see the add-friend screen
- The destination set on the button (the delivery status page, for example) opens
Customers who are already friends and have already agreed to LINE Login reach the destination with almost no screens in between. When the ID can't be linked, customers don't see an error, and the destination still opens.
In Lumo and Klaviyo, you'll see the following.
- The friend is linked to the Klaviyo profile the notification was sent for
- The friend's timeline shows a record of the ID link made by "Notification message tap"
- The Klaviyo profile gets the LINE information, such as the LINE User ID
Setup steps
Each auto send message has its own switch, and it's off by default.
- From the side menu, open "Automation" > "Auto-Send Messages", then open the edit screen of the auto send message that uses the LINE notification message
- Turn on "Link identity when the button is tapped"
- Save
You don't need to change anything on the Klaviyo Flow side. The JSON body of the Webhook action and the button URL of the LINE notification message stay as they are. If you use the JSON body copied from "Klaviyo Flow connection details" as is, phoneNumber is the Klaviyo profile's phone number ({{ person.phone_number }}), which meets the phone number condition.
When the ID is linked
Only the first person who taps the button within 72 hours of sending is linked. This works for notification messages sent from a Klaviyo Flow. It also works for notifications sent from a contact-based HubSpot workflow. The conditions for HubSpot are explained in LINE actions in HubSpot workflows. It also works for notifications sent from a Shopify Purchase Completed or Shipment Completed Workflow and from the Public API (Action Types and How to Configure Them, API Integration Overview).
| Item | Condition |
|---|---|
| Time limit | Taps within 72 hours of sending count. Later taps don't link anyone and only open the destination |
| Number of people | Only the first person to tap, per notification |
| Delivery status | Only notifications whose delivery was confirmed as completed |
| Phone number | The ID is linked only when the phone number the notification was sent to is the same as the phone number (phone_number) on the Klaviyo profile it was sent for. When the profile has no phone number, or the notification went to a different number such as the shipping address phone, nothing is linked |
| Already linked | If either the friend or the Klaviyo profile the notification was sent for is already linked to someone else, the link isn't changed. The friend's timeline shows why nothing was linked |
| Friends you unlinked | A friend whose ID link was removed in Lumo isn't linked by a tap |
| Friend add only | Customers who add the account as a friend without tapping the button aren't linked |
| Click tracking | When click tracking is off for the message, tapping the button doesn't link IDs |
| Which notifications | It works for notifications sent after you turn the switch on. For notifications sent before that, tapping the button only opens the destination |
| Device | Taps on a smartphone count. On a PC, only the destination opens |
Things to keep in mind
Point the button to a page related to the content of the notification. The terms of LINE notification messages don't allow links whose only purpose is adding a friend or advertising.
- Require authentication before any page that shows personal information, and confirm the destination when you apply for LINE notification messages
- Customers must add the account as a friend themselves. Customers who don't add it on the add-friend screen still reach the destination
- If a customer forwards the link in the notification to someone else and that person taps it first, that person's LINE account may be linked. When you find a link you didn't intend, remove it from "Unlink identity" under "More actions" on the friend's detail screen. The steps are in Unlinking an identity
The earlier method (putting an ID linking URL in the button)
The earlier method, where the button URL is a custom QR Code's ID linking URL, keeps working as before. For new setups, use the "Link identity when the button is tapped" switch.
With the earlier method, you issue a URL from a custom QR Code with "Klaviyo Linkage" as the link type, end it with ?e={{ data.email }}, and set it as the CTA button URL of the LINE notification message. The steps for creating a custom QR Code are explained in Linking Klaviyo Profiles and LINE Friends by ID.
Don't use the earlier method and the switch on the same button. When the button's destination is a Lumo ID linking URL, linking by tap doesn't work even with the switch on.
Getting the Klaviyo Flow connection details
Open "Klaviyo Flow connection details" on the auto send message's detail page to get everything you need for the Klaviyo webhook action.
- On the detail page of the auto send message you created, select "Klaviyo Flow connection details"
- Choose the LINE Official Account to send from
- Note the Destination URL, the header (Key / Value), and the JSON body. Copy the JSON body with "Copy JSON"
The JSON body already includes the order-data mappings that feed the merge variables, along with a deduplication key (idempotencyKey). In most cases you can paste it as is.
The deduplication key makes sure that even if the same order event arrives repeatedly — because Klaviyo resends a webhook or a Flow fires twice — the notification is sent only once. The same customer never receives the same notification twice. If you are using a JSON body you obtained earlier, get the latest JSON and paste it again to enable this.
Creating the Flow in Klaviyo
Create a Flow triggered by "Placed Order" for order confirmations or "Fulfilled Order" for shipping confirmations, then configure a webhook action with the values you collected.
Choosing the trigger
| Notification | Trigger to choose | When it fires |
|---|---|---|
| Order confirmation | "Placed Order" | When an order is placed |
| Shipping confirmation | "Fulfilled Order" | When the entire order is fulfilled |
Do not choose the similarly named "Ordered Product": it fires once per product in the order, so the same customer would receive multiple notifications.
Configuring the Webhook action
- Add a "Webhook" action to the Flow
- Choose "POST" as the HTTP method and set the Destination URL
- Add a custom header with the Key and Value you noted
- Paste the copied content into the JSON body
If you build both order and shipping Flows, paste each Flow's JSON body from its corresponding auto send message.
Verifying the order data merge
The order-data references in the JSON body can vary by store configuration, so use Klaviyo's Preview Webhook to confirm real values are filled in.
If any field shows up empty or as "None" in the preview, inspect the Klaviyo event data and adjust the corresponding variables starting with event. in the JSON body to match your actual events.
Checking behavior before you go live
Verify the merge and the actual delivery with Preview Webhook and a test profile before publishing.
- Open "Preview Webhook" on the Klaviyo webhook action and confirm each field, such as the order number, is filled with real values
- Trigger a real event with a test profile registered with your own phone number and confirm the notification arrives on LINE
- If everything looks good, set the Flow to Live
- Reopen the Flow after saving and confirm the webhook action has not reverted to Draft. Notifications are not sent while it is in Draft
If the test doesn't arrive, first check that the phone number on the Klaviyo profile matches the number registered to your LINE account.
Test sends from Preview Webhook are not subject to duplicate detection, so you can send the same content as many times as you need. Also, a notification for the same order is treated as a separate send when the destination phone number is different. If you sent a test to the wrong phone number, correct the number and send it again.
Stores with partial fulfillment
If you ship one order in multiple shipments, note that Fulfilled Order only fires when the entire order is fulfilled.
- To notify on each partial shipment, build a separate Flow with the "Fulfilled Partial Order" trigger
- To prevent duplicate notifications, add the trigger filter "HasPartialFulfillments is false" to the Fulfilled Order flow (this is Klaviyo's recommended setup)
- In a Fulfilled Partial Order flow, use Preview Webhook to confirm that the
idempotencyKeyin the JSON body changes with each shipment. If the value doesn't change, the second and later shipment notifications may be treated as duplicates and not sent. In that case, adjust the key to a value that is unique per shipment (such as the tracking number)
Stores that never split shipments don't need this setup.
When things don't work
Common issues with LINE notification messages from Flows and what to check.
| Symptom | What to check |
|---|---|
| The notification doesn't arrive | Check that the phone number on the Klaviyo profile matches the number registered to the customer's LINE account. The international format (for example +819012345678) is the most reliable. Also confirm your account is approved to use LINE notification messages. You can review send results on the auto send message's detail page |
| "--", "None" or blanks appear in the message | Klaviyo could not resolve the variable. In a Flow test send, values are empty when the chosen profile has no triggering event (such as an order), and LINE shows them as "--". Check the event data with Preview Webhook and adjust the variables starting with event. in the JSON body |
| The emphasized item ends with "…" | The text exceeded 15 characters after variable replacement, so the rest was cut off. Use a short value such as the shipping date, or move that value to an item |
| Delivery is slow | Notifications usually arrive within a minute of the event. If delivery is much slower, check whether the Flow includes a Time delay step in Klaviyo. Use Preview Webhook and test sends to verify your setup |
| Authentication errors | Check that the webhook header Key and Value are up to date. If you regenerated the authentication key, update the value on the Klaviyo Flow side as well |
| The Flow doesn't run | Check that the webhook action is Live. It can revert to Draft after saving |
| The same notification arrived twice | Check that the JSON body includes the deduplication key (idempotencyKey). Getting the latest JSON from "Klaviyo Flow connection details" and pasting it again automatically prevents duplicate sends |
| Tapping the button doesn't link the ID | Check that "Link identity when the button is tapped" is on for the auto send message and that click tracking is on. Also check that the phone number the notification was sent to is the same as the phone number on the Klaviyo profile. Taps more than 72 hours after sending, taps by a second person, and notifications sent before you turned the switch on don't link anyone. If the friend or the Klaviyo profile the notification was sent for is already linked to someone else, the friend's timeline shows the reason |
| You want to send a regular LINE message from a Flow | Regular sends to friends (product cards, Rich Messages, and so on) use a different setup. It is explained in Send LINE Messages from a Klaviyo Flow |