Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


This Data Connector is in Beta and requires signing an addendum for access. For more information, contact


Table of Contents


  • Basic knowledge of Treasure Data, including the toolbelt Toolbelt and JavaScript SDK

  • S3 credential with access key id and secret access key.

  • Client name from Salesforce DMP


If your data doesn’t have a time column, you can add the column by using the add_time filter option. See details at add_time filter plugin.

td connector:issue assumes you have already created a database (sample_db) and a table (sample_table). If the database or the table do not exist in TD, td connector:issue will fail. Therefore, you must create the database and table manually or use --auto-create-table with td connector:issue to automatically create the database and table.


  • incremental This configuration is used to control the load mode, which governs how the data connector fetches data from Salesforce DMP based on one of the native timestamp fields associated with each object.

  • columns This configuration is used to define a custom schema for data to be imported into Treasure Data. You can define only columns that you are interested in here but make sure they exist in the object that you are fetching. Otherwise, these columns aren’t available in the result.

  • last_record This configuration is used to control the last record from the previous load job. It requires the object include a key for the column name and a value for the column’s value. The key needs to match the Salesforce DMP Data column name.

See Appendix How Incremental Loading works for details and examples.