Pinterest is a visual discovery engine for finding ideas, such as recipes, home and style inspiration, and more. It provides features for data organization and configuration of access controls for your audience and customer list.
This TD export integration lets you write job results directly from Treasure Data to Pinterest.
- Add or remove users from an audience.
- Auto-create a new audience if the audience does not exist.
- Clear all users from an audience.
- Auto-detect and hash the user id (email, idfa, or maid) if the value is not hashed.
- Specify an option to skip or stop invalid values.
- Basic knowledge of Treasure Data, including the TD Toolbelt.
- The default export format is SHA256; all data should be hashed or unhashed using SHA256 format.
- The query from TD should select only one column with the name: email, maid, or idfa in String format.
- For email, it could be hash or unhashed.
- For maid and idfa, they should be hashed before.
- It takes up to 24-48 hours to update the Audience and Audience size
You must create and configure the data connection in Treasure Data before running your query. As part of the data connection, you provide authentication to access the integration.
- Open TD Console.
- Navigate to Integrations Hub > Catalog.
- Search for Pinterest and select Output.
Select Create Authentication.
Connect to your Pinterest account.
You are redirected back to the Integrations Hub > Catalog. Repeat the step to connect to a new account to choose your new OAuth connection.
Type a name for your connection.
Select Done.
- Navigate to Data Workbench > Queries.
- Select a query for which you would like to export data and run the query to validate the result set.
- SelectExport Results.
- Select an existing integration authentication.
5. 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 complete.
6. Select Done. 7. Run your query 8. Validate that your data moved to the destination you specified.
| Parameter | Data Type | Required? | Description |
|---|---|---|---|
| Ad Account ID | String | Yes | Pinterest Ad account id |
| Audience Type | String | Yes | Audience type. Support values:
|
| Action | String | Yes | Audience action. Support values:
|
| Audience ID | String | Audience ID. Required only if the action is:
| |
| Audience Name | String | Audience Name. Required only if the action is:
| |
| Audience Description | String | Audience Description | |
Limit Records Per Request | Integer | The number of records sent in each batch Default value: | |
| Ignore Invalid Records | Boolean | If this check box is selected when the time data is sent to Pinterest, incorrect records or errors are skipped, and the remaining rows of data continue sending. If this checkbox is not selected, an exception is thrown when inaccurate records or errors are encountered. | |
| Max Retries | Integer | Maximum retry times for each API request | |
| Initial retry time wait in millis | Integer | Wait time for the first retry (in milliseconds) | |
| Max retry wait in millis | Integer | Maximum wait time for an API call before it gives up | |
| HTTP Connect Timeout in seconds | Integer | The amount of time before the connection times out when making API calls | |
| HTTP Read Timeout | Integer | The amount of time waiting to read data into the request | |
| HTTP Write Timeout | Integer | The amount of time waiting to write data into the request |
If the integration is configured in Create mode and scheduled to run recurrently, the second execution will fail because the target Audience already exists. To avoid this, after the first successful execution, change the setting to Update mode.
You 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.
You can specify using this data connector to export data within Treasure Workflow.
Learn more at Exporting Data with Parameters.
| Name | Type | Required | Description |
|---|---|---|---|
type | String | Yes | pinterest |
client_id | String | Yes | |
client_secret | String | Yes | |
refresh_token | String | Yes | |
ad_account_id | String | Yes | |
audience_type | String | Yes | customer_list |
action | String | Yes | Value could be:
|
audience_id_replace | String | Required if action is replace_current_audience | |
audience_id_delete | String | Required if action is delete_current_audience | |
audience_id_add_people | String | Required if action is add_people_to_current_audience | |
audience_id_remove_people | String | Required if action is remove_people_to_current_audience | |
audience_name | String | Required if action is create_new_audience | |
audience_description | String | ||
limit_records_per_request | int | ||
ignore_error | boolean | ||
retry_count | int | ||
retry_initial_wait_millis | int | ||
max_retry_wait_millis | int | ||
connection_timeout_secs | int | ||
write_timeout_secs | int | ||
read_timeout_secs | int |
_export:
td:
database: td.database
+test_export_task:
td>: export_pinterest_test.sql
database: ${td.database}
result_connection: pinterest_conn
result_settings:
type: pinterest
client_id: xxx
client_secret: xxx
refresh_token: xxx
ad_account_id: xxx
audience_type: customer_list
action: ADD_PEOPLE_TO_CURRENT_AUDIENCE
audience_id_add_people: xxx
audience_name: xxx
audience_description: xxx
limit_records_per_request: 10000
ignore_invalid_records: true
retry_count: 7
retry_initial_wait_millis: 500
max_retry_wait_millis: 300000
connection_timeout_secs: 180
write_timeout_secs: 60
read_timeout_secs: 180