Testing LINE Campaigns

Before launching a LINE campaign to your full audience, Engage Studio provides tools to preview message content, send test messages, and validate your setup. This guide covers the available testing methods and pre-launch checklist.

Each message object in the Campaign Content editor includes an inline preview that shows how the message will appear to LINE users on a smartphone screen.

• Text messages: Renders the text with line breaks as they will appear in the LINE chat
• Imagemap messages: Displays the image with tap area outlines overlaid, showing the action mapped to each region

Test Send lets you deliver the campaign's message bundle to a specific LINE User ID before the campaign is launched.

1. In the Campaign Content tab, ensure the campaign content is saved.
2. Click Test Send.
3. Enter the LINE User ID of the test recipient (for example, your own LINE account's user ID as registered in the LINE OA's follower list).
4. Click Send.

The test message is sent immediately to the specified LINE User ID. The message bundle is sent exactly as configured, including all message objects in their configured order.

Before launching your LINE campaign to the full audience, verify the following:

• LINE Sender Account is correctly configured in Configurations > LINE OA Configurations with a valid Integration Hub authentication
• Channel Access Token in Integration Hub is valid and not expired
• LINE Sender Account is assigned to the campaign's workspace
• TD Write-only API Key is valid and associated with the correct delivery log database

• Target segment is selected and returns an expected number of profiles
• Segment has been checked for LINE User ID coverage — profiles without a LINE User ID will be excluded from delivery
• Review the percentage of segment members without a LINE User ID to estimate effective reach

• All messages have been previewed in the editor
• Test Send has been completed and the messages appeared correctly in LINE
• Imagemap tap areas are correctly positioned and link to the intended URLs
• All URLs are reachable and load correctly
• UTM parameters are configured correctly

• Delivery schedule (immediate or scheduled time) is correct
• Time zone for scheduled delivery is set as intended

Symptom: Test send fails with an authentication error, or all deliveries fail with auth_error in the delivery log.

Resolution:

1. Go to Integration Hub and verify the LINE OA Authentication credential is active.
2. Check the Channel Access Token in the LINE Developers Console — it may have expired.
3. Issue a new Channel Access Token and update the Integration Hub credential.
4. If the LINE Sender Account references the credential by name, verify the name matches exactly.

Symptom: Test send fails with "Invalid recipient" error, or individual deliveries fail with invalid_recipient.

Resolution:

• Confirm the LINE User ID is correct and belongs to a user who has followed (not blocked) the LINE Official Account.
• For bulk delivery errors, verify that LINE User IDs in your CDP profiles were obtained correctly (via LIFF, LINE Login API, or authorized import).
• Users who have blocked your LINE OA cannot receive messages and will appear as delivery failures.

Symptom: Deliveries fail with rate_limit_exceeded errors in the delivery log.

Resolution:

• LINE Messaging API enforces rate limits on message send volume. For large audiences, delivery is automatically paced by the Streaming Egress Connector.
• If rate limit errors persist, contact your customer success representative to review your LINE OA plan limits.

Symptom: Individual delivery failures with message_too_long error in the delivery log.

Resolution:

• The Liquid-expanded text for the affected profile exceeded LINE's 5,000-character limit.
• Identify which profiles triggered the error by querying the delivery log.
• Shorten the message template or add a character-limit safeguard using Liquid:
  {{ profile.custom_message | truncate: 200 }}

To investigate test or production delivery results:

1. Query the delivery log database: delivery_line_{system_identifier} (find this in the LINE Sender Account configuration).
2. Filter by campaign_id and time range.
3. Check status, error_code, and message_type columns for error details.

For the Streaming Egress Connector raw logs (line_out connector logs), contact your Treasure Data support representative or refer to the Integration Hub log viewer.

• LINE Official Account Setup
• Create a One-off LINE Campaign
• LINE Message Types
• Click Tracking
• LINE Campaign Reporting