Data Connector for Marketo

Table of Contents

Prerequisites

  • Basic knowledge of Treasure Data

GUI: Web console

You can import Marketo data from GUI console.

1. Go to Connections from left menu and select Marketo by clicking create button.



2. Input required information. The parameters like endpoint, wsdl, user_id, encryption_key are available at "Admin" > "Web Services" page in Marketo.



3. Save and name connection name.



4. Click ‘New Transfer’ from my connections.



5. Select ‘Leads’ or ‘Activity Log’ and specify period of data source (short period 1day or so are recommended at first).



6. Check the preview of table and data to be imported.



7. Input target Database and Table to be imported. Select ‘Append’ or ‘Replace’. Select ‘processed_time’ as time-key for ‘Lead’ (Select ‘activity_date_time’ for ‘Activity Log’).



8. Set schedule if you like. Import starts when schedule time comes or immediately if you chose ‘Once now’.



9. Confirm JOB is running from Jobs page.



CLI: Step 0: Install ‘td’ command v0.11.9 or later

Install the newest Treasure Data Toolbelt.

$ td --version
0.11.10

Set up config for Marketo activity log

Step 1: Create Seed Config File (seed.yml)

First, please prepare seed.yml as below for Marketo Activity log. The parameters like endpoint, wsdl, user_id, encryption_key are available at "Admin" > "Web Services" page in Marketo. You will use replace mode:

If needed, you can find more detailed information on getting access to your credential’s in Marketo’s documentation: http://developers.marketo.com/blog/quick-start-guide-for-marketo-rest-api/

in:
  type: marketo/activity_log
  endpoint: https://XXXXXXXX.mktoapi.com/soap/mktows/YYYY
  wsdl: https://XXXXXXXX.mktoapi.com/soap/mktows/YYYY?WSDL
  user_id: XXXXXXXXXX_YYYYYYYYYYYYYYY
  encryption_key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  from_datetime: "2016-06-01"
out:
  mode: replace

Or you could use the following seed.yml for the Marketo Activity Log.

in:
  type: marketo/activity_log
  endpoint: https://XXXXXXXX.mktoapi.com/soap/mktows/YYYY
  wsdl: https://XXXXXXXX.mktoapi.com/soap/mktows/YYYY?WSDL
  user_id: XXXXXXXXXX_YYYYYYYYYYYYYYY
  encryption_key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  from_datetime: "2016-06-01"
out:
  mode: append

The detailed list of options are available here.

For more details on available out modes, see Appendix.

Step 2: Guess Fields (Generate load.yml)

Second, please use connector:guess. This command automatically reads the target file and intelligently guesses the file format.

$ td connector:guess seed.yml -o load.yml

If you open up load.yml, you’ll see guessed file format definitions including, in some cases, file formats, encodings, column names, and types.

in:
  type: marketo/activity_log
  endpoint: https://XXXXXXXX.mktoapi.com/soap/mktows/YYYY
  wsdl: https://XXXXXXXX.mktoapi.com/soap/mktows/YYYY?WSDL
  user_id: XXXXXXXXXX_YYYYYYYYYYYYYYY
  encryption_key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  from_datetime: "2016-06-01"
out:
  mode: replace

Then you can preview how the system will parse the file by using preview command.

$ td connector:preview load.yml

If the system detects your column name or type unexpectedly, please modify load.yml directly and preview again.

Untitled-3
Currently, the Data Connector supports parsing of "boolean", "long", "double", "string", and "timestamp" types.

Step 3: Execute Load Job

Finally, submit the load job. It may take a couple of hours depending on the data size. Users need to specify the database and table where their data is stored.

$ td connector:issue load.yml \
    --database td_sample_db \
    --table td_sample_table \
    --time-column activity_date_time

The above 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, 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:

$ td connector:issue load.yml \
    --database td_sample_db \
    --table td_sample_table \
    --time-column activity_date_time \
    --auto-create-table
Untitled-3
You can assign Time Format column to the "Partitioning Key" by "--time-column" option.

Set up config for Marketo leads

Step 1: Create Seed Config File (seed.yml)

You can use the same config as for activity logs, but you should specify type: marketo/lead instead of type: marketo/activity_log.

in:
  type: marketo/lead
  endpoint: https://XXXXXXXX.mktoapi.com/soap/mktows/YYYY
  wsdl: https://XXXXXXXX.mktoapi.com/soap/mktows/YYYY?WSDL
  user_id: XXXXXXXXXX_YYYYYYYYYYYYYYY
  encryption_key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  from_datetime: "2016-06-01"
out:
  mode: replace

Step 2: Guess Fields (Generate load.yml)

You can run the same process as with marketo activity logs.

$ td connector:guess seed.yml -o load.yml

Then you can preview how the system will parse the file by using preview command.

$ td connector:preview load.yml

If the system detects your column name or type unexpectedly, please modify load.yml directly and preview again.

Step 3: Execute Load Job

You can run the same process as with marketo activity logs.

$ td connector:issue load.yml \
    --database td_sample_db \
    --table td_sample_table \
    --time-column processed_time

Scheduled execution

You can schedule periodic Data Connector execution for periodic Marketo activity log import. We take great care in distributing and operating our scheduler in order to achieve high availability. By using this feature, you no longer need a cron daemon on your local data center.

For the scheduled import, Data Connector for Marketo activity log imports all records.

Untitled-3
Only supported Lead Activity log. Lead does not.

Create the schedule

A new schedule can be created by using the td connector:create command. The name of the schedule, cron-style schedule, the database and table where their data will be stored, and the Data Connector configuration file are required.

$ td connector:create \
    daily_marketo_activity_log_import \
    "10 0 * * *" \
    td_sample_db \
    td_sample_table \
    load.yml
Untitled-3
The `cron` parameter also accepts three special options: `@hourly`, `@daily` and `@monthly`. For more detail on Scheduled Jobs
Untitled-3
By default, schedule is setup in UTC timezone. You can set the schedule in a timezone using -t or --timezone option. Please note that `--timezone` option only supports extended timezone formats like 'Asia/Tokyo', 'America/Los_Angeles' etc. Timezone abbreviations like PST, CST are *not* supported and may lead to unexpected schedules.

List the Schedules

You can see the list of currently scheduled entries by td connector:list.

$ td connector:list
+-----------------------------------+---------------+----------+-------+-----------------+----------------------+
| Name                              | Cron          | Timezone | Delay | Database        | Table                |
+-----------------------------------+---------------+----------+-------+-----------------+----------------------+
| daily_marketo_activity_log_import | 10 0 * * *    | UTC      | 0     | td_sample_table | sample_table         |
+-----------------------------------+---------------+----------+-------+-----------------+----------------------+

Show the Setting and History of Schedules

td connector:show shows the execution setting of a schedule entry.

% td connector:show daily_marketo_activity_log_import
Name     : daily_marketo_activity_log_import
Cron     : 10 0 * * *
Timezone : UTC
Delay    : 0
Database : td_sample_db
Table    : td_sample_table

td connector:history shows the execution history of a schedule entry. To investigate the results of each individual execution, please use td job <jobid>.

% td connector:history daily_marketo_activity_log_import
+--------+---------+---------+--------------+-----------------+----------+---------------------------+----------+
| JobID  | Status  | Records | Database     | Table           | Priority | Started                   | Duration |
+--------+---------+---------+--------------+-----------------+----------+---------------------------+----------+
| 578066 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-18 00:10:05 +0000 | 160      |
| 577968 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-17 00:10:07 +0000 | 161      |
| 577914 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-16 00:10:03 +0000 | 152      |
| 577872 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-15 00:10:04 +0000 | 163      |
| 577810 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-14 00:10:04 +0000 | 164      |
| 577766 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-13 00:10:04 +0000 | 155      |
| 577710 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-12 00:10:05 +0000 | 156      |
| 577610 | success | 10000   | td_sample_db | td_sample_table | 0        | 2015-04-11 00:10:04 +0000 | 157      |
+--------+---------+---------+--------------+-----------------+----------+---------------------------+----------+
8 rows in set

Delete the Schedule

td connector:delete will remove the schedule.

$ td connector:delete daily_marketo_activity_log_import

Appendix

A) Modes for out plugin

You can specify file import mode in out section of seed.yml.

append (default)

This is the default mode and records are appended to the target table.

in:
  ...
out:
  mode: append

replace (In td 0.11.10 and later)

This mode replaces data in the target table. Please note that any manual schema changes made to the target table will remain intact with this mode.

in:
  ...
out:
  mode: replace

Last modified: Oct 14 2016 06:20:24 UTC

If this article is incorrect or outdated, or omits critical information, please let us know. For all other issues, please see our support channels.