Treasure Data allows you to retarget your mobile audience using nend retargeting platform provided by F@N Communications, Inc. You can write job results directly to nend.
For sample workflows of nend, view Treasure Boxes.
Continue to the following topics:
Prerequisites
Basic knowledge of Treasure Data, including the TD Toolbelt.
Data imported into Treasure Data, that you wish to export into nend.
Working knowledge of SQL, Hive, or Presto.
A nend account.
Use the TD Console to Create Your Connection
Create a New Connection
In Treasure Data, you must create and configure the data connection prior to running your query. As part of the data connection, you provide authentication to access the integration.
1. Open TD Console.
2. Navigate to Integrations Hub > Catalog.
3. Search for and select nend.
4. Select Create Authentication.
5. Type the credentials to authenticate.
6. Type a name for your connection.
7. Select Done.
Define your Query
You have to set the result column name "uid". |
After you execute your query, the Treasure Data query result is automatically imported into nend.
- Complete the instructions in Creating a Destination Integration.
Navigate to Data Workbench > Queries.
Select a query for which you would like to export data.
Run the query to validate the result set.
Select Export Results.
- Select an existing integration authentication.
- Define any additional Export Results details. In your export integration content review the integration parameters.
For example, your Export Results screen might be different, or you might not have additional details to fill out:
Select Done.
Run your query.
Validate that your data moved to the destination you specified.
Integration Parameters for nend
| Parameter | Values | Description |
|---|---|---|
| Destination type |
| An identifier for Advertisers (IDFA) is a random device identifier assigned by Apple to a user's device Google advertising ID uuencoding is a form of binary-to-text encoding that originated in the Unix programs uuencode and uudecode written by Mary Ann Horton |
| Destination name | ||
| Initial retry delay | 5 | Initial retry interval per API call in milliseconds |
| Retry limit | 4 | The number of retries before the system gives up. |
| Mode | replace append | Output modes are ways to modify the data as the data is placed in Treasure Data.
|
Optionally Schedule the Query Export Jobs
You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.
1. Navigate to Data Workbench > Queries.
2. Create a new query or select an existing query.
3. Next to Schedule, select None.
4. 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. |
Custom cron... Details
Cron Value | Description |
|---|---|
| Run once an hour. |
| Run once a day at midnight. |
| 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 | ‘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. |
| 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. |
| 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. |
5. (Optional) You can delay the start time of a query by enabling the Delay execution.
Execute the Query
Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically imported to the specified container destination.
Scheduled jobs that continuously fail due to configuration errors may be disabled on the system side after several notifications.
Optionally Configure Export Results in Workflow
Within Treasure Workflow, you can specify the use of this data connector to export data.
Learn more at Using Workflows to Export Data with the TD Toolbelt.