Marketo V3 Connector > Synchronization Tasks with Marketo > Marketo Targets in Synchronization Tasks

Marketo Targets in Synchronization Tasks

When you run a synchronization task, specify the operation and the source that you want the Secure Agent to write to the target. The Secure Agent inserts, updates, upserts, or deletes source rows that you specify into the target based on the configured operation for the target object.

The task operations depend on the target object that you select. You can configure the target properties when you schedule the synchronization task.

You configure Marketo target properties on the Target page of the Synchronization Task wizard. Provide the name of the target connection and specify the target object to write data to Marketo.

The following table describes the Marketo target properties:

Property	Description
Connection	Name of the target connection.
Target Type	Type of Marketo target objects. Select Single.
Target Object	Name of the target object. You can choose one of the following target objects when you write data to Marketo: - Lead - MergeLead - AssociateLead - AddLeadToList - RemoveLeadFromList - Opportunity - OpportunityRole - SalesPerson - Company - Custom Objects

You need to configure specific advanced properties to use a specific source object in a synchronization task.

Advanced Target Properties

When you configure a synchronization task, you can configure the advanced target properties. The advanced target properties appear on the Schedule page of the Synchronization Task wizard.

The following table describes the Marketo advanced target properties:

Advanced Target Property	Description
Lead - Type of API to be used	The type of Marketo API used to insert leads in the Marketo database. You can select from the following options: - Standard API. Uses the Standard API when you want to create leads in Marketo. - Bulk API. You cannot use Bulk API to insert leads in the Marketo database. Default is Standard API.
Lead - Create Duplicate	Creates a duplicate of the lead when that lead already exists in the Marketo database. The REST API either inserts or upserts data based on the operation you specify. You can choose one of the following values: - Yes. Duplicates an existing lead. - No. Does not duplicate an existing lead. Default is No.
Lead - List ID for Leads	The ID of a list for leads where you want to create the lead.
Lead - Lookup Field	Performs a lookup of the field you specify to determine whether the lead you want to add to the Marketo database is a duplicate lead.
Lead - Partition Name	The partition name where you want to insert, update, or upsert leads in Marketo. If specified, the Secure Agent verifies if the user has access to the partition. If you do not specify a partition, the API operation uses the primary partition of the list workspace.
Custom Obj / Oppty (Role) / Company / Sales Per - Dedupe Fields	The dedupeFields or idField of the custom, opportunity, opportunity role, sales person, or company object in Marketo for which you want to perform an update or delete operation. When you do not specify dedupeFields or idField for an update or delete operation, Marketo considers the dedupeFields of the corresponding custom, opportunity, opportunity role, sales person, or company object as the default. Note: You can specify this field value only to update or delete data in custom, opportunity, opportunity role, sales person, or company objects in Marketo. This field is optional.
Success File Directory	Directory for the success rows files. Specify a directory path that is available on each Secure Agent machine in the runtime environment. By default, Data Integration writes the success rows file to the following directory: <Secure Agent installation directory>/apps/Data_Integration_Server/data/success
Error File Directory	Directory for the error rows files. Specify a directory path that is available on each Secure Agent machine in the runtime environment. By default, Data Integration writes the error rows file to the following directory: <Secure Agent installation directory>/apps/Data_Integration_Server/data/error

Note: The advanced target property field name Dedupe Fields represents properties that you can configure for custom objects, opportunity, opportunity role, sales person, or company.

The following table lists the advanced properties applicable to each target object:

Advanced Target Property	Lead	MergeLead	AssociateLead	AddLeadToList	RemoveLeadToList	Custom Object/Opportunity/Opportunity Role/Company/Sales Person
Lead - Type of API to be used	Required Default is Standard API.	-	-	-	-	-
Lead - Staging Folder for Bulk Load API	Optional when Type of API to be used is set to Bulk API.	-	-	-	-	-
Lead - Create Duplicate	Optional Default is No.	-	-	-	-	-
Lead - List ID for Leads	Optional, if Type of API to be used is set to Bulk API.	-	-	-	-	-
Lead - Lookup Field	Required, if Create Duplicate is set to Yes.	-	-	-	-	-
Lead - Partition Name	Optional, if Type of API to be used is set to Bulk API.	-	-	-	-	-
Custom Obj / Oppty (Role) / Company / Sales Per - Dedupe Fields	-	-	-	-	-	Required for update operation. Default is dedupeFields.

Note: The advanced target property field name Dedupe Fields represents properties that you can configure for custom objects, opportunity, opportunity role, sales person, or company. Cells with - indicate NA for the respective object. Though some of the advanced target properties for an object are optional, you must specify the properties according to your use case.

Marketo Target Synchronization Example

You work in the marketing industry, and business analysts in your enterprise want to add leads from a recent marketing conference into Marketo. You want to track the activity of these leads in Marketo.

Configure a synchronization task to insert data to Marketo. Configure the following objects:

Source: The synchronization task includes a flat file source that contains the new lead details. The source includes fields, such as firstName, salutation, middleName, lastName, email, and phone.
Target: The synchronization task includes a lead target object. The target includes fields, such as firstName, salutation, middleName, lastName, email, and phone.
Mapping: Map the fields of the flat file source to the Marketo target.; The following image shows the mapping of the flat file source with the lead target object in Marketo:

When you run the synchronization task, the Secure Agent reads from the flat file source and writes to Marketo based on the fields you mapped.