# Salesforce Export Integration

Salesforce (SFDC) is a leading customer relationship management (CRM) platform. It provides CRM software and applications focused on sales, customer service, marketing automation, e-commerce, analytics, and application development. Over 150,000 companies, both big and small, are growing their businesses with Salesforce.

This TD export integration allows you to write job results from Treasure Data directly to version 2 of SFDC.

## Prerequisites

- A [Salesforce.com](https://salesforce.com) username, password, and security token for API integration
- The “API Enabled” permission is enabled.
- A target [Salesforce.com](https://salesforce.com) object should exist, and you should have permissions to read and write to it.
- The "Hard delete" permission is enabled for your user profile


## Static IP Address of Treasure Data Integration

If your security policy requires IP whitelisting, you must add Treasure Data's IP addresses to your allowlist to ensure a successful connection.

Please find the complete list of static IP addresses, organized by region, at the following link:
[https://api-docs.treasuredata.com/en/overview/ip-addresses-integrations-result-workers/](https://api-docs.treasuredata.com/en/overview/ip-addresses-integrations-result-workers/)

## Supported Authentication Methods

SFDC V2 output supports these authentication types:

- Credentials
- OAuth
- Session ID


## Use the TD Console to Create a Connection

### Create a New Authentication

1. Open TD Console.
2. Navigate to Integrations Hub > Catalog.
3. Search for salesforce and select salesforce.
4. Select **Create Authentication**.


![](/assets/sfdcv2.de86ac7d6430b8aaca6d24f4875cee42be960b53f7a489ab846fb8b3cf5ec874.9253be9a.png)

1. Type the credentials to authenticate:


| Parameter | Description |
|  --- | --- |
| Login URL | The Salesforce login url, e.g., [https://login.salesforce.com.](https://login.salesforce.com.) When authentication method is Session ID, the value must be Salesforce instance URL |
| Authentication method | Support 3 types of authentication:   - Credentials - OAuth - Session ID |
| OAuth connection |  |
| Username | The Salesforce login username and required if authentication method is credentials |
| Password | The Salesforce login password and required if authentication method is credentials |
| Client ID | The Salesforce app's client id. It's required for input connector only |
| Client secret | The Salesforce app's client secret. It's required for input connector only |
| Security token | This field can be omit if it's appended in the password field |
| Session ID | The session ID of Salesforce |
| Initial retry delay | The first time we fail to connect, wait this many seconds before retrying (with exponential backoff) |
| Retry limit | Maximum number of retry |


1. Select Continue.
2. Type a name for your connection.
3. Select Done


### Define your Query

To avoid any issues with result export, define column aliases in your query such that resulting column names from the query match the Salesforce field names for default fields and API names (usually ending with __c) for custom fields.

1. Navigate to **Data Workbench > Queries**.
2. Select **New Query**.
3. Run the query to validate the result set. For example, a query could look something like this:


![](/assets/sfdcv2query.eb1160a22c37b2a4876919165e47c0267e873f6e401d771bc8114d768d752753.9253be9a.png)

### Specify the Result Export Target

1. Select Export Results.


![](/assets/sfdcv2queryexport.526b07ce994cc9331e8745f4aba3e2397c737a0edbc62d74563c815fbe3f0e6d.9253be9a.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.9253be9a.png)

**Create New Integration:** For plugins that support OAuth, we can not use this option.  It will force the user to back to the catalog and create a connection there

![](/assets/screen-shot-2023-08-24-at-14.30.24.9b962884faf1d0561bff81304019302bb5c5b92767954282c74e52a3683c6965.9253be9a.png)

For **Use Existing Integration**

![](/assets/screenshot-2023-08-25-at-12.28.55.928889ea6142488f706572795e8ed380f32e29c35a5d2113ff62b8062159a0d0.9253be9a.png)

| Parameter  | Description |
|  --- | --- |
| Mode | - **APPEND**: Append mode is the default that is used when no mode option is provided in the URL. In this mode, the query results are appended to the object.
- **TRUNCATE**—With truncate mode, the system first truncates the existing records in the Salesforce and then inserts the query results.
  - If the **Hard delete?** checkbox is checked, the Object will be permanently removed from Salesforce  and then the query results will be inserted. This action requires hard delete permissions to be enabled in Salesforce.
  - If the **Hard delete?** checkbox is unchecked, the Object will be moved to the **Trashbin** and then query results will be inserted.
- **UPDATE**—The "unique" parameter is required with this mode and it must be defined as an external key in Salesforce.
  - If the **Upsert new records?** checkbox is checked, the unique must be the externalId field in Salesforce
    - If the unique parameter exists in Salesforce, the current row will be updated. Otherwise it will be inserted into Salesforce.
  - If the **Upsert new records?** checkbox is unchecked:
    - If the unique parameter is an ID and it exists in a row and in Salesforce, then the current row will be updated.
    - If the unique parameter is not an ID, then the query Id from Salesforce will be used as the unique field in the update in Salesforce.

 |
| Object | [Salesforce.com](https://salesforce.com) Object |
| Upsert new records? | This option is available when mode is update. |
| Key | This option is available when mode is update.  If **Upsert new records?** checkbox is checked, this field must be the externalId field in Salesforce.  The externalId field can only set for a custom field. System fields—such as Id, CreatedDate, LastModifiedDate, CreatedByID, etc.—are not custom fields. |
| Hard delete? | This option is available when mode is truncate. |
| Concurrency mode | The concurrency_mode option controls how the data is uploaded to the [Salesforce.com](https://salesforce.com) organization. The default mode is parallel.   With the parallel method, data is uploaded in parallel. This is the most reliable and effective method for most situations.   if you see an error message that says "UNABLE_TO_LOCK_ROW," try concurrency_mode=serial instead. |
| Batch size | By default, this splits the records in the result of a query into chunks of 10000 records and bulk uploads one chunk at a time. |
| API version | The Salesforce API version. Default is 32.0. |
| Initial retry delay | If the initial attempt to connect fails, wait this many seconds before retrying (with exponential backoff). |
| Retry limit | This option sets the number of attempts that should be made to write the result to the configured [Salesforce.com](https://salesforce.com) destination if errors occur. If the export fails more than the set number of retries, the query fails. |


1. After you have entered the required information in the fields, select Done.


### (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).