This page explains what user interaction data is available from LINE, the technical constraints of LINE's Webhook API, and how Engage Studio combines multiple data sources to provide campaign reporting.
LINE's Messaging API Webhook delivers events to Treasure Data via the Streaming Ingress Connector (LINE Messaging API Webhook). However, LINE does not include per-user open or click events in Webhook payloads by design.
The following events are delivered in real time and can be stored in Treasure Data CDP:
| Event Type | Description |
|---|---|
follow | User followed the LINE Official Account |
unfollow | User unfollowed or blocked the LINE Official Account |
message | User sent a message to the LINE Official Account |
postback | User tapped a postback action button (Flex or Template messages) |
videoViewingComplete | User finished watching a video message (1-on-1 only) |
beacon | User entered a beacon-equipped physical location |
accountLink | User linked their account via the account link feature |
LINE does not expose the following events through its Webhook or Messaging API:
- Message opens — Whether an individual user opened a delivered message
- Link clicks — Whether an individual user clicked a URL in a Text or Imagemap message
- Read receipts — Per-user read status
These limitations are by design in LINE's platform. Per-user engagement data of this type is not provided through any LINE API endpoint.
While per-user open and click events are unavailable, LINE provides aggregate statistics per broadcast (total opens, total clicks, etc.) through its Insights API. Use the LINE OA Insights Import Integration to import these aggregate metrics into Treasure Data. See LINE Campaign Reporting for details.
Despite the limitations above, you can measure link-level engagement by appending UTM parameters to all URLs in your LINE messages. When recipients tap a link and load the destination page, the UTM parameters are captured by your web analytics platform (e.g., Google Analytics), giving you URL-level traffic attribution per campaign.
UTM parameters configured on the UTM Tracking tab are automatically appended to every URL in the campaign messages at delivery time.
Default UTM parameters for LINE campaigns:
| Parameter | Default Value |
|---|---|
utm_source | line |
utm_medium | social |
utm_campaign | Campaign name |
utm_content | (optional, configurable per campaign) |
utm_term | (optional, configurable per campaign) |
When a URL already contains query parameters, UTM parameters are appended without overwriting existing values unless the same key already exists, in which case the campaign-level value takes precedence.
Example:
Original URL in Imagemap tap area:
https://example.com/product?ref=bannerDelivered URL after UTM injection:
https://example.com/product?ref=banner&utm_source=line&utm_medium=social&utm_campaign=spring_sale_2026| Message Type | UTM Applied To |
|---|---|
| Text (v2) | All URLs in the text body |
| Imagemap | uri action URLs in tap areas |
| Flex Message (future) | All action button URLs |
Delivery and error events are written at send time to the delivery_line_{system_identifier} database. This log records per-profile delivery outcomes (success or failure) but does not include open or click events, as these are not available from LINE.
| Column | Description |
|---|---|
event | delivery or error |
time | Unix timestamp of the event |
channel_type | LINE |
campaign_id | Engage Studio campaign ID |
line_channel_name | LINE Sender Account name |
line_user_id | Recipient LINE User ID (hashed) |
message_type | Message object type: textV2, imagemap |
status | success or failed |
error_code | LINE API error code (error events only) |
If you use a URL shortener or intermediate redirect:
- UTM parameters are appended to the URL before delivery.
- If the redirect strips query parameters, UTM data will not reach your analytics platform. Verify your redirect configuration preserves query parameters.
LINE's platform design intentionally restricts per-user behavioral data (opens, clicks) from being accessible to LINE Official Account operators. This applies regardless of account tier or API plan.
In addition, LINE's development guidelines explicitly prohibit the following:
- Do not attempt to identify the attributes of specific users by their user ID.
- Do not use the audience management API or send narrowcast messages for the purpose of identifying user attributes.
Refer to the LINE Messaging API development guidelines for current policies.