You can import Media Campaign, Paid Search Campaign, Site Campaign, User Audience Segment Map, Segment Mapping File or Dissent Lists from Salesforce DMP (Krux) into Treasure Data.
Table of Contents | ||
---|---|---|
|
Prerequisites
Basic knowledge of Treasure Data, including the Toolbelt and JavaScript SDK
S3 credential with access key id and secret access key.
Client name from Salesforce DMP
...
Start Date: Import data that has been created since this date.
End Date: Import data that has been created up to this date.
Incremental Loading: When importing data based on a schedule, the time window of the fetched data automatically shifts forward on each run. For example, if you specify the initial start date as January 1 and end date as January 10, the first run fetches data from January 1 to January 10, the second run fetches from January 11 to January 20, and so on.
Preview
Excerpt Include |
---|
Preview
You’ll see a preview of your data. To make changes, select Advanced Settings, otherwise select Next.
|
Advanced Settings
You can specify the following parameters:
...
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 to include akey
for the column name and avalue
for the column’s value. Thekey
needs to match the Salesforce DMP Data column name.
See How Incremental Loading works for details and examples.
...
Code Block | ||
---|---|---|
| ||
$ td connector:delete daily_import |
...
Modes for the out plugin
You can specify file import mode in the out section of the load.yml file.
The out: section controls how data is imported into a Treasure Data table.
For example, you may choose to append data or replace data in an existing table in Treasure Data.
Output modes are ways to modify the data as the data is placed in Treasure Data.
Append (default): Records are appended to the target table.
Replace (available In td 0.11.10 and later): Replaces data in the target table. Any manual schema changes made to the target table remain intact.
Examples:
Code Block | ||
---|---|---|
| ||
in:
...
out:
mode: append
|
...
linenumbers | true |
---|
...
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
How Incremental Loading works
Incremental loading uses the last imported date of files to load records monotonically, inserting or updating files after the most recent execution.
...