LINE is in Asia what Facebook Messaging and Instagram are to US mobile users -- a fast and easy way to communicate with friends and discover new promotions about your favorite products and services. LINE is the #1 mobile messaging platform in Japan, Thailand, Taiwan. It is also one of the largest Ads delivery platforms.
- As a marketer, I want to add my Ad Account ID to Treasure Data Ad Group to use Treasure Data as a Data Provider to push my audience to LINE and vice versa, remove Ads Account ID out of TD Ad group if needed.
- As a marketer, I want to export the custom audiences from TD to LINE for target marketing using IFA, Email, and Phone Number (auto-hashed Email and Phone Number).
- Basic Knowledge of Treasure Data.
- Basic knowledge of LINE Ads API.
- Basic knowledge of the LINE Business Manager platform.
- Users must have the necessary LINE Ads ID for this integration. Before pushing TD segments to LINE Ads, users will have to link the Ad ID you provide to our Treasure Data Ad Group. After the connection is made, an approval request email will be sent to you via LINE Ads.
You must enable notifications to receive an approval request email. With the LINE connector, Treasure Data is the data provider. If you want to use this connector to push audience segments out to the LINE Ads platform to advertise, you must use TD as a data provider. TD will use the data provider API to access the your LINE Ads account, which allows you to push segments to LINE.
- Open LINE Ads Business Manager and approve the linked request.
- The audience file upload size is limited to 62914560 bytes per upload (~ 1.5 million records for IFA and ~0.9 million records for hashed mobile numbers and emails). If it exceeds that in one process, the connector internally splits the record.
- When Audience Name are duplicated (multiple Audience with the same name on LINE), an exception will be thrown.
- When creating a new audience (when the specified audience name does not exist in the customer's LINE Ads account) and when record splitting is required because of the number of records, a new audience is created after the first upload in the loop, but from the second upload in the loop onwards, the data is written to the same audience once.
- Login to the LINE Ads Manager.
- Select Log in with business account and log in.
- Select Ad accounts to find the Ad account ID.
To integrate Treasure Data with LINE Ads, you must use Treasure Data as the data provider. Therefore, it is necessary to link to Treasure Data's AD group. This is a two-step process.
- Open TD Console.
- Open Integrations Hub.
- Select Catalog.
- Search for LINE Ads connector, and then select Create Authentication.
- Provide your LINE Ads Account ID, select Done.
- Navigate to Data Workbench> Queries.
- Create new Query.
- In the Query, input "Select 1".
- Select Export Result and select your LINE Ads authentication.
- Choose Add Ad Account to Ad Group.
- Click Save and Run.
- Go to your LINE Ads Manager and approve the linked request.
SELECT ifa AS id FROM ...SELECT email AS id FROM ...SELECT phone_number AS id FROM ...- Go to Data Workbench, create new Queries.
- Output results must include a column named id according to ID type.
- Select Export Result and select your LINE Ads authentication.
- Choose Push Audience to LINE Ads as Action parameter.
- Configure your integration parameter.
| Parameter | Description |
|---|---|
| Use existing LINE Audience ID to push audience? | Use the existing LINE Audience ID instead of Audience Name. |
| Audience Name | Enter the audience name to upload or replace IDs. If you want to replace IDs, the audience with the provided name must exist. |
| Audience Action | Select the action type. Supported types: Add, Replace |
| ID Type | Select the ID type of data to upload. Supported types: IFA, Phone Number, Emails |
- Click Save and Run.
| Parameter | Values | Description |
|---|---|---|
| account_id | string | Required. Your Ad Account ID |
| use_audience_id | boolean | Use Audience ID instead of Audience Name |
| audience_name | string | Audience name to upload or replace audiences |
| audience_id | string | Required when use_audience_id is true. An existing Audience ID |
| audience_action | string | ADD or REPLACE |
| id_type | string | Supported types: IFA, PHONE_NUMBER, or EMAIL |
| max_retry | integer | Maximum retry times for each API call when an error occurred (Default 8) |
| initial_retry_wait | integer | Wait time for the first retry. Default 15 seconds |
| max_retry_wait | integer | Maximum time between retries. Default 1 hour |
| connection_timeout | integer | HTTP connection time out |
SELECT email AS idFROM tableYou can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.
Treasure Data's scheduler feature supports periodic query execution to achieve high availability.
When two specifications provide conflicting schedule specifications, the specification requesting to execute more often is followed while the other schedule specification is ignored.
For example, if the cron schedule is '0 0 1 * 1', then the 'day of month' specification and 'day of week' are discordant because the former specification requires it to run every first day of each month at midnight (00:00), while the latter specification requires it to run every Monday at midnight (00:00). The latter specification is followed.
Navigate to Data Workbench > Queries
Create a new query or select an existing query.
Next to Schedule, select None.
In the drop-down, select one of the following schedule options:
Drop-down Value Description Custom cron... Review Custom cron... details. @daily (midnight) Run once a day at midnight (00:00 am) in the specified time zone. @hourly (:00) Run every hour at 00 minutes. None No schedule.
| Cron Value | Description |
|---|---|
0 * * * * | Run once an hour. |
0 0 * * * | Run once a day at midnight. |
0 0 1 * * | Run once a month at midnight on the morning of the first day of the month. |
| "" | Create a job that has no scheduled run time. |
* * * * *
- - - - -
| | | | |
| | | | +----- day of week (0 - 6) (Sunday=0)
| | | +---------- month (1 - 12)
| | +--------------- day of month (1 - 31)
| +-------------------- hour (0 - 23)
+------------------------- min (0 - 59)The following named entries can be used:
- Day of Week: sun, mon, tue, wed, thu, fri, sat.
- Month: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec.
A single space is required between each field. The values for each field can be composed of:
| Field Value | Example | Example Description |
|---|---|---|
| A single value, within the limits displayed above for each field. | ||
A wildcard '*' to indicate no restriction based on the field. | '0 0 1 * *' | Configures the schedule to run at midnight (00:00) on the first day of each month. |
A range '2-5', indicating the range of accepted values for the field. | '0 0 1-10 * *' | Configures the schedule to run at midnight (00:00) on the first 10 days of each month. |
A list of comma-separated values '2,3,4,5', indicating the list of accepted values for the field. | 0 0 1,11,21 * *' | Configures the schedule to run at midnight (00:00) every 1st, 11th, and 21st day of each month. |
A periodicity indicator '*/5' to express how often based on the field's valid range of values a schedule is allowed to run. | '30 */2 1 * *' | Configures the schedule to run on the 1st of every month, every 2 hours starting at 00:30. '0 0 */5 * *' configures the schedule to run at midnight (00:00) every 5 days starting on the 5th of each month. |
A comma-separated list of any of the above except the '*' wildcard is also supported '2,*/5,8-10'. | '0 0 5,*/10,25 * *' | Configures the schedule to run at midnight (00:00) every 5th, 10th, 20th, and 25th day of each month. |
- (Optional) You can delay the start time of a query by enabling the Delay execution.
Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically exported to the specified destination.
Scheduled jobs that continuously fail due to configuration errors may be disabled on the system side after several notifications.
(Optional) You can delay the start time of a query by enabling the Delay execution.
You can also send segment data to the target platform by creating an activation in the Audience Studio.
- Navigate to Audience Studio.
- Select a parent segment.
- Open the target segment, right-mouse click, and then select Create Activation.
- In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
- Customize the activation output in the Output Mapping panel.
- Attribute Columns
- Select Export All Columns to export all columns without making any changes.
- Select + Add Columns to add specific columns for the export. The Output Column Name pre-populates with the same Source column name. You can update the Output Column Name. Continue to select + Add Columnsto add new columns for your activation output.
- String Builder
- + Add string to create strings for export. Select from the following values:
- String: Choose any value; use text to create a custom value.
- Timestamp: The date and time of the export.
- Segment Id: The segment ID number.
- Segment Name: The segment name.
- Audience Id: The parent segment number.
- + Add string to create strings for export. Select from the following values:
- Set a Schedule.
- Select the values to define your schedule and optionally include email notifications.
- Select Create.
If you need to create an activation for a batch journey, review Creating a Batch Journey Activation.
Within Treasure Workflow, you can specify the use of a data connector to export data.
Learn more at Using Workflows to Export Data with the TD Toolbelt.
_export:
td:
database: target_database
+line_export_task:
td>: export_emails.sql
database: ${td.database}
result_connection: my_line_ads
result_settings:
action: PUSH_AUDIENCE
audience_action: ADD
audience_name: my_test_audience
id_type: emailIf you no longer need to export data from TD, you can remove Ad Account from Ad Group.
- Navigate to Data Workbench > Queries.
- In the query, input "Select 1".
- Select Export Result and select your LINE Ads authentication.
- Choose Remove Ad Account from Ad Group.
- Click Save and Run.