The Klaviyo integration syncs specific data types in defined directions between Klaviyo and Lumo — and you can review and adjust each field under "Sync Data".
How sync works
In the Klaviyo integration, Klaviyo profiles and your Lumo friend information are synced on the basis of ID matching.
When a Klaviyo profile and a LINE friend are linked using an email address, phone number, or LINE User ID, the data on both sides is updated according to your integration settings. The basic sync runs automatically after the integration is set up, so as an operator you can simply start using the required fields as they are. If you want to adjust which fields are synced or in which direction, you can change each one individually under "Sync Data".
Data synced from Lumo to Klaviyo
From Lumo to Klaviyo, your LINE information is written as dedicated custom properties.
The custom properties created automatically inside Klaviyo profiles at integration time are as follows. On the Klaviyo side, you can use these properties to build conditions for Segments and Flows.
| Display in Lumo | Klaviyo property name | Description |
|---|---|---|
| LINE User ID | LINE User ID | The LINE identifier. It serves as the key for ID matching |
| LINE Display Name | LINE Display Name | The LINE display name |
| LINE Follow Status | LINE Follow Status | Indicates whether the user has added you as a friend or has blocked you |
| LINE Consent | LINE Consent | Indicates whether the user has consented to broadcasts |
| LINE Consent Updated At | LINE Consent Updated At | The date and time the broadcast consent was updated |
| LINE Consent Source | LINE Consent Source | Indicates which channel was used to update the broadcast consent |
| LINE traffic source | LINE Traffic Source | How the person became a friend. If they came via a QR code or a friend-add CTA, its name is recorded; otherwise a common value such as "LINE QR - Login" is used. Recorded only the first time |
| LINE Identity Linked At | LINE Identity Linked At | The date and time the ID linkage was completed |
| LINE Identity Link Source | LINE Identity Link Source | Indicates which route completed the ID linkage (QR code, Klaviyo form, Shopify customer account, and so on) |
| LINE Identity Link Page | LINE Identity Link Page | The URL of the page where the ID linkage started (without the query string) |
| LINE Acquisition Route | LINE Acquisition Route | The route through which the person first became a friend (QR Code, friend-add CTA, Klaviyo form, Shopify customer account, etc.). Once recorded, the value is never rewritten |
| LINE Acquisition Page | LINE Acquisition Page | The URL of the page where the first friend add started (without the query string) |
If you have connected multiple LINE Official Accounts to a single Klaviyo account, a number is appended to the end of each property name (for example, LINE User ID _ 2) to distinguish between accounts.
The three ID-linkage properties are recorded when a customer links through a QR code, a form, the customer account page, or a similar route. They are not recorded for links created by CSV import or automatic matching.
The values of LINE Acquisition Route are the route keys qr_code, web_cta, klaviyo_form, shopify_account, follow, message, and import. When the route can't be determined, unknown is recorded. Use these values as they are in Klaviyo Segment and Flow conditions.
Data synced from Klaviyo to Lumo
By default, profile fields from Klaviyo aren't shown in your Lumo friend information.
Once ID linkage is established, Lumo keeps the Klaviyo email address and phone number in encrypted form so it can match the profile and the friend as the same person. By default, these values aren't used to display friend information or as broadcast variables. If you want to bring profile fields such as email address, phone number, first name, and last name into your friend information, add the target Klaviyo properties under "Sync Data" and set their sync rule to "Klaviyo → Lumo". Klaviyo custom properties used in Segment conditions can be referenced regardless of the Sync Data settings.
Choosing the data to sync
You manage which fields are synced and in which direction under "Sync Data".
On this screen, you can review the list of properties synced between Klaviyo and Lumo, along with the sync rule for each one.
Reviewing sync rules
Each property has a sync rule that indicates the direction in which data flows.
| Sync rule | Description |
|---|---|
| "Klaviyo → Lumo" | Brings Klaviyo data into Lumo |
| "Lumo → Klaviyo" | Writes Lumo data to Klaviyo |
Switching between required and optional fields
Properties are divided into required fields, which are always synced, and optional fields, for which you can turn syncing on or off.
- Required: Fields related to ID matching and broadcast consent. They are always synced and can't be toggled on or off
- Optional: All other fields. You can toggle "Sync" on or off for each field
Adding a property
If you want to bring a Klaviyo property into Lumo, you can add it as a sync target.
Click "Add Klaviyo property", then select and add the target property. The sync rule for the added property will be "Klaviyo → Lumo". Once you have changed your settings, click "Save settings".
Updating the LINE consent status
The broadcast consent status (LINE Consent) is updated according to the LINE friend status.
When a customer adds you as a friend, this is reflected as broadcast consent granted in the LINE Consent of the linked Klaviyo profile; when they block you, it is reflected as consent withdrawn. This lets you extract Segments and branch Flow conditions in Klaviyo based on the latest consent status. Note that this only keeps the consent status on the Klaviyo side up to date; it doesn't change the actual LINE follow status (adding or blocking a friend) itself.
The LINE friend status is re-fetched periodically and reflected automatically in the broadcast consent status of your Klaviyo profiles. No manual update is needed.
Checking the sync status
You can check the integration's sync status on the "Dashboard".
| Display item | Description |
|---|---|
| "Integration status" | Shows whether the integration is healthy and whether the latest data has been synced |
| "Connected account" | Shows the Klaviyo ID, the property used for ID matching, and the connection date and time |
| "Sync history" | Lets you review the date and time, status, number of Profiles, and number of failures for each sync |
Clicking "Resync Data" re-fetches profiles from Klaviyo and runs the sync again. Depending on the volume of data, this may take a few minutes to complete.
When things don't work
Common data sync issues and how to address them are listed below.
- Sync has stopped: Check the sync history on the Dashboard for any errors. If the integration's authentication has expired, you may need to reconnect the integration
- A Klaviyo field doesn't appear in Lumo: Fields such as first name, last name, and email address are not synced by default. Add the target property under "Sync Data" and set its sync rule to "Klaviyo → Lumo"
- The broadcast consent status isn't updating: Check whether the target profile has completed ID matching. Profiles that aren't linked are not eligible for updates