Marketo Restrictions

• •If any of the List - List ID value specified in the list source properties is not found in Marketo, the REST API returns only that data that matches the configured properties. The API does not return an error for incorrect list IDs that are not found in Marketo.
• •Ensure that all the fields of the lead data is valid when writing data to Marketo. If any of the lead fields are not valid, the REST API does not create the lead. The Secure Agent does not write the error rows to the error file directory.
• •When you configure a task to create duplicate leads in Marketo, you must use the standard API. When you use the bulk API, the Marketo REST API updates the existing leads in Marketo.
• •You might observe latency when you use the dedupe fields to update the Lead Link Field, such as email address, for a custom object in Marketo.
• •When you use Marketo Connector, you cannot preview lead, lead activity, and custom object records.
• •When you configure a task to retrieve campaigns, you cannot retrieve leads associated with campaigns. You also cannot create, update, or delete campaigns.
• •You can include a maximum of only 10 ActivityType IDs in a single task.
• •Do not exceed a maximum number of 300 characters for any of the fields when you configure the advanced properties of a Marketo source or target.
• •When you configure the value of concurrent threads, do not exceed a maximum number of 10 threads for Marketo tasks to process concurrently at a given time.
• •When you configure a task to read data from a Marketo instance that does not support the opportunity, opportunity role, sales person, and company objects, an error occurs when you preview the data. These objects are not enabled for CRM-enabled subscriptions in Marketo.
• •The Marketo API does not return an error if any of the records for the company, sales person, opportunity, or opportunity role source objects are not found in Marketo, even though you specify the required advanced properties in the task.
• •You can retrieve the metadata of only the default fields of email, program, tag, channel, list, and campaign objects in Marketo.
• •When you specify multiple IDs for retrieving the program and email data, the Marketo API does not support additional API call requests, which causes an overhead as Informatica Cloud sends multiple API requests.
• •The program, list, and activityType objects have pre-defined fields because of a restriction from the Marketo APIs. When you use the program, list, or activityType objects, you can retrieve data only from these pre-defined fields.
• •The metadata of objects other than lead, company, opportunity, role, sales person, and custom objects has pre-defined fields because of a restriction from the Marketo APIs. When you use these objects, you can retrieve data only for these pre-defined fields.
• •When you configure a task to read data from a folder in Marketo, you cannot specify the root parameter required for browsing folders in Marketo.
• •When you configure a task to read data from Marketo for objects other than lead and custom objects, the number of records to read must not exceed 300. The task fails if the number of records exceeds 300.