- 15 Apr 2022
- 1 Minute to read
Data Destination - Marketo
- Updated on 15 Apr 2022
- 1 Minute to read
Help page for setting up a data transfer to Marketo.
Data Loader: Embulk
- Using the embulk-output-marketo private repository.
- Using the following Marketo gem.
The column name set in trocco must match the field REST API name in Marketo.
Please refer to the following Marketo article for further information regarding REST API names.
Step 1: General Settings
|Marketo Connection Configuration||Yes||-||From the Marketo Connection Configurations created in advance, select the one with the necessary permissions for this transfer.
If you haven’t previously created any Connection Configurations, click the Add Connection Configuration button to set up a new one.
|Target||Yes||-||Specify the target object type at the destination.
Currently the following data types can be set:
|Custom Object Name||Yes||-||You are required to complete this field when custom_object is selected as the object type.
Enter the custom object API name for the data you wish to transfer.
|Action||Yes||-||You are required to complete this field when opportunity, opportiunity_role, or custom_object, is selected as the target object type.
You can select from the following actions:
|lookupField||Yes||email (only for lead)||You can only enter into this field when the data target is set to, opportunity, opportunity_role, or custom_object, and the action is set to updateOnly.
The field specified here will be used as a primary key.
When the target data type is set to lead, email will be used as the default value.
If you enter dedupteFields, it will be specified by the describe call as externalOpportunityId.
If you enter idField, it will be specified by the describe call as marketoGUID.
|Partition Name||No||-||If partitions are used in Marketo, specify the partition name in this field.|