# Pushcode Export Integration

![](/assets/fc6435db26e28e5d9619f4da4a190599.91b8c4c9f3220bf2f733043630ae743d437c5a957d08dee858ff5e146c24d1e8.7afc6741.png)

You can create a PUSHCODE list from data stored in Treasure Data. Use cases include:

1. *Personalization through Segmentation*: Capture user behaviors from websites or mobile apps, collecting all user events into Treasure Data. Then, write personalization logic in SQL, and export the segmented mailing list to PUSHCODE for targeted campaigns.
2. *Customer Retention*: For SaaS and subscription e-commerce businesses, customer retention can drive growth. Identify“at-risk” users with user events stored in Treasure Data and pushed to PUSHCODE. Send targeted promotions to the at-risk users to re-engage them.


Integration with PUSHCODE through Google Cloud Storage allows you to upload a list of target user ids to PUSHCODE for a personalized push notification.

## What can you do with this Integration?

- **Export a list of PUSHCODE user ids based on a specific condition**. This information can help you build precise customer segments that enhance the user experience for your campaigns.


## Prerequisites

- Basic Knowledge of Treasure Data.
- Basic knowledge of PUSHCODE


## Requirements and Limitations

- You can only use User IDs that are ingested by the [PUSHCODE Import Integration](/int/pushcode-import-integration)
- When a file is exported to GCS, the list is immediately applied to your PUSHCODE account


## Use the TD Console to Create a 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.

### Create a New Authentication

The PUSHCODE integration uses Google Cloud Storage integration. Follows steps in the [Google Cloud Storage Export Integration](/int/google-cloud-storage-export-integration) to create an authentication using a JSON key file.

### Define your Query

1. Navigate to **Data Workbench > Queries**.
2. Select **New Query**.
3. Run the query to validate the result set.


![](/assets/image2021-9-7_15-1-38.a0ef34a3cfb6035eb6a53a758a755062decbb29fac046d1b24440a76d0662c7a.7afc6741.png)

### Specify the Result Export Target

1. Select **Export Results**.


![](/assets/image2021-9-7_15-10-56.ee7ed43caab64adefafcc22595462fd8068c974c4f47b5959a7babd7d99972b8.7afc6741.png)

1. You can select an existing authentication or create a new authentication for the external service to be used for output. Choose one of the following:


**Use Existing Integration**

![](/assets/image2021-9-7_15-28-30.d271866c7c3cea4dab234b61bea815a69b186746c80435855b4b86d1f77cc30e.7afc6741.png)

### Integration Parameters for PUSHCODE

The Export Results interface opens. Edit the parameters.

![](/assets/image2021-3-30_12-28-31.01cb9d5bd8a747601e7c3a96f5227ffc54b70f1220028a2c0057632f96a7a266.7afc6741.png)

| Parameter | Data | Description |
|  --- | --- | --- |
| Bucket | Bucket Name is found in the PUSHCODE console | Target GCS Bucket |
| Path Prefix | userid_list/YYYYMMDDHHMM_A_B.csv.gz | - YYYYMMDDHHMM: Input your expected export timestamp - A_B: <list_id>_<list_name>. If A is blank, a new list with name B is created. |
| Format | CSV | - Choose CSV |
| Compression | gz | - Choose GZ |
| Header Line | unchecked |  |
| Delimiter | default |  |
| Null String | default |  |
| End of Line Character | CRLF |  |
| Application Name |  | Arbitrary client name associated with API requests. For example, Treasure Data GCS Output. |


### Example Query

Specific only user_id for exported result. For example,


```sql
SELECT user_id as user_id FROM subscriber_list
```

### (Optional) Schedule Query Export Jobs

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.

#### Scheduling your Job Using TD Console

1. Navigate to **Data Workbench > Queries**
2. Create a new query or select an existing query.
3. Next to **Schedule**, select None.
![](/assets/image2021-1-15_17-28-51.f1b242f6ecc7666a0097fdf37edd1682786ec11ef80eff68c66f091bc405c371.0f87d8d4.png)
4. In the drop-down, select one of the following schedule options:
![](/assets/image2021-1-15_17-29-47.45289a1c99256f125f4d887e501e204ed61f02223fde0927af5f425a89ace0c0.0f87d8d4.png)
| Drop-down Value | Description |
|  --- | --- |
| Custom cron... | Review [Custom cron... details](#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

![](/assets/image2021-1-15_17-30-23.0f94a8aa5f75ea03e3fec0c25b0640cd59ee48d1804a83701e5f2372deae466c.0f87d8d4.png)

| **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. |


1. (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 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.

## Activate a Segment in Audience Studio

You can also send segment data to the target platform by creating an activation in the Audience Studio.

1. Navigate to **Audience Studio**.
2. Select a parent segment.
3. Open the target segment, right-mouse click, and then select **Create Activation.**
4. In the **Details** panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
5. Customize the activation output in the **Output Mapping** panel.


![](/assets/ouput.b2c7f1d909c4f98ed10f5300df858a4b19f71a3b0834df952f5fb24018a5ea78.8ebdf569.png)

- 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 Columns**to 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.


1. Set a **Schedule**.


![](/assets/snippet-output-connector-on-audience-studio-2024-08-28.a99525173709da1eb537f839019fa7876ffae95045154c8f2941b030022f792c.8ebdf569.png)

- Select the values to define your schedule and optionally include email notifications.


1. Select **Create**.


If you need to create an activation for a batch journey, review [Creating a Batch Journey Activation](/products/customer-data-platform/journey-orchestration/batch/creating-a-batch-journey-activation).