...
Scroll to the CHANNELS section and select the Read checkbox on Email
Scroll to the CONTACT section and select the Read checkbox on Audiences and List and Subscribers
Scroll to the DATA section and select the Read and Write checkbox on Data Extensions, Read for Tracking Events
Scroll to HUB section and and select the Read checkbox on Campaign
...
On the Installed Packages screen, scroll down to Components panel, then take note of the Client Id and Client Secret. You use the information to write the data from Treasure Data to Salesforce Marketing Cloud.
...
On the Choose Your Integration Type screen, select Server-to-Server then click Next.
...
On the Set Server-to-Server Properties screen:
Scroll to the CHANNELS section and select the Read checkbox on Email
Scroll to CONTACT section and select the Read checkbox on Audiences and List and Subscribers
Scroll to DATA section and select the Read and Write checkbox on Data Extensions, Read for Tracking Events
Scroll to HUB section and select the Read checkbox on Campaign
...
On the Installed Packages screen, scroll down to Components panel, then take note of the Client Id, Client Secret and Authentication Base URI. You will use the information to write the data from Treasure Data to Salesforce Marketing Cloud.
...
client_id: Salesforce Marketing Cloud client id.client_secret: Salesforce Marketing Cloud client secret.target: Salesforce Marketing Cloud entity object to be imported.
For more details on available out modes, see the Appendix A.
(optional): Preview data to import
...
It is recommended to specify --time-column option, since Treasure Data’s storage is partitioned by time (see also data partitioning). If the option is not given, the data connector selects the first long or timestamp column as the partitioning time. The type of the column specified by --time-column must be either of long and timestamp type.
If your data doesn’t have a time column you can add it using add_time filter option. More details at add_time filter plugin
| Code Block |
|---|
$ td connector:issue load.yml --database td_sample_db --table td_sample_table --time-column modifieddate |
The preceding command assumes you have already created database(td_sample_db) and table(td_sample_table). If the database or the table do not exist in TD this command will not succeed. Therefore, so create the database and table manually or use --auto-create-table option with td connector:issue command to auto create the database and table:
...