LINE Ads
Upload custom audiences to LINE Ads for targeted advertising on the LINE platform. Reach users across Japan, Thailand, Taiwan, and Indonesia through LINE’s advertising network.
Prerequisites
- A LINE Ads account with API access enabled
- Your LINE Ads Ad Account ID
- API access key and secret key from your LINE Ads group settings
- Data provider or ad tech partner API access approval from LINE
Authentication
LINE Ads uses API key authentication with a JWS (JSON Web Signature) signing mechanism.
- Log in to your LINE Ads Manager at ads.line.me
- Navigate to Group Settings in the sidebar
- Locate or generate your API Access Key and Secret Key
- In Zeotap, enter the access key and secret key in the credentials fields
Zeotap automatically handles the JWS signature calculation for each API request using your credentials.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Ad Account ID | Text | Yes | Your LINE Ads ad account identifier (numeric). Find this in your LINE Ads Manager account settings. |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Audience Name | Text | Yes | Name for the custom audience to create or update |
| Audience ID | Text | No | Existing custom audience ID to update. Leave blank to create a new audience. |
| Identifier Type | Select | Yes | Type of user identifiers to upload: Email (SHA256 hashed), Phone (SHA256 hashed), or IFA (IDFA/AAID) |
Supported Operations
Audience Sync Modes: Add, Mirror
| Mode | Behavior |
|---|---|
| Add | Appends new members to the custom audience |
| Mirror | Replaces the entire audience membership with the current sync data |
Features
- Field Mapping: No
- Schema Introspection: No
How It Works
- Audience creation — If no Audience ID is provided, Zeotap creates a new custom audience with the specified name
- Data normalization — Email and phone identifiers are normalized (lowercased, trimmed) and SHA256-hashed before upload. IFA identifiers are sent as-is.
- Batch upload — Identifiers are uploaded in batches of up to 500,000 records per request
- Async processing — LINE Ads processes uploads asynchronously (HTTP 202). Audience matching may take several hours to complete.
Rate Limits
- API rate limit: 10 requests per second
- Upload file size: Up to ~60 MB per upload request (~1.5 million IFA records or ~900,000 hashed email/phone records)
- Concurrent REPLACE operations: Limited to 3 simultaneous requests per ad account
Best Practices
- Use Email or Phone identifier types for the highest match rates in LINE’s user base
- Each custom audience can only use one identifier type — choose the type that best matches your data
- Allow up to 24 hours for LINE to process and populate newly uploaded audiences
- For large audiences (>500k records), Zeotap automatically splits uploads into multiple batches
- Use Mirror mode for complete audience refreshes; use Add mode for incremental updates
Troubleshooting
Authentication failed: invalid access key or secret key
Verify your API credentials in LINE Ads Manager under Group Settings. Ensure you are using the correct access key and secret key pair. Credentials may be rotated — check if new keys were issued.
Ad Account ID not found
Confirm your Ad Account ID in LINE Ads Manager. The ID is numeric and can be found in your account settings. Ensure your API credentials have permission to access this ad account.
Audience not populating after sync
LINE Ads processes audience uploads asynchronously. Allow up to 24 hours for the audience to fully populate. If the audience remains empty, verify that your identifiers match LINE’s user base (strongest coverage in Japan, Thailand, Taiwan, and Indonesia).
Upload returned HTTP 429
You have exceeded the API rate limit of 10 requests per second. Reduce the sync frequency or wait before retrying. Contact LINE support if you need a higher rate limit quota.
No valid identifiers found in batch
Ensure your data contains the correct column for the selected identifier type. For Email, map a column named email. For Phone, map a column named phone. For IFA, map a column named ifa, idfa, gaid, or advertising_id.
REPLACE operation failed with concurrent request error
LINE limits REPLACE operations to 3 simultaneous requests per ad account. Wait for existing uploads to complete before starting a new mirror sync. Avoid running multiple mirror syncs to the same ad account simultaneously.