Treasure Data can publish user segments into Salesforce Marketing Cloud (ExactTarget), and enable you to send personalized emails to your customers. You can run data-driven email campaigns, by using your first-party data from Web, Mobile, CRM, and other data sources.
This data connector is in Beta. For more information, contact email@example.com.
|Table of Contents|
Basic knowledge of Treasure Data
Basic knowledge of Salesforce Marketing Cloud
Open SSH 7.8 Private Key is supported. The format of the key is detected and the correct library to use is chosen.
Set Up a Secure, Automated Account in Salesforce
Access your Salesforce account to begin set up.
Create an FTP Account
On the SFMC dashboard, in your account, select Administration.
Review your SFTP account information.
Configure for Automatic Mail Delivery
Go back to the SFMC dashboard, and select Email Studio > Email.
Select the template, define the email properties, including name and location, and select Next to provide content. Continue creating the email and save it when you are finished.
Define Specification for Import into Salesforce
Create an Import Interaction in Salesforce
From the Email view, select Interactions.
Provide the import interaction information, including SFTP information and data import location. Save the information.
Specify the Import Trigger
From the Email view, select the SFDC blue cloud icon to view menu options.
Select Active to enable the import trigger.
Select Save and Close.
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.
Open TD Console.
Navigate to Integrations Hub > Catalog.
Search for and select Salesforce Marketing Cloud via SFTP.
Select Create Credentials.
Type the credentials to authenticate.
Type or select values for the parameters:
Type a name for your connection.
Define your Query
Create a job that selects data from within Treasure Data. The specified column name for the mapping must match the column name in the SFMC Exact Target mail. “Email Address” and “Subscriber Key” columns are required. If needed, you can change the mapped column name that is in TD database. You can change the column name from within the TD Console.
You could specify more parameters for the target export file:
Path prefix: the path for the plugin to save your output files in the target server
Rename file after upload finish: select to try to upload the file with .tmp extension first, then rename the file without .tmp when the file is uploaded successfully
Format: Format of the file (would be CSV or TSV)
Compression: choose it whenever you would like to compress the file. We support gzip and bzip2 compression
Header line: choose it if you would like to write the first line as the columns' name
Delimiter: delimiter between values in the target file, would be | or tab or comma
Quote policy: quote between each column, could be MINIMUM, ALL, or NONE
Null string: the value for the null field in the query
End-of-line character: the character to specify for end of the line. Would be Carriage Return Line Feed (CRLF - used in Windows OS file systems) or Line Feed (LF - used in Unix, macOS) or Carriage Return (CR - used in classic macOS)
Encryption column names: list of encryption columns, separated by a comma
Encryption key: specify key needed to perform the encryption algorithm
Encryption iv: specify a number to prevent repetition in data encryption
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.
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.
timezone: UTC _export: td: database: sample_datasets +td-result-into-target: td>: queries/sample.sql result_connection: your_connections_name result_settings: secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx advertiser_id: xxxxxx data_activation_duration: 43200 ....
Verifying the Query Export Job
After the job finishes, you can check the output file on the SFTP server by using the general SFTP command, as shown in the following example: