Marketo Restrictions

• •If any of the list ID for List Details 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.
• •When you read data from Marketo, you cannot make more than 100 API calls in a 20-second window.
• •If the mapping in a Data Synchronization task or a Mapping Configuration task contains a large number of source and target fields, the Marketo REST API does not respond. You might encounter an error when the number of fields exceeds 400.
• •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 cannot retrieve the fields that have the date and time value, such as CreatedAt or UpdatedAt, for lead activities and lead changes from Marketo. When you map such fields in Informatica Cloud to retrieve the data, the Secure Agent maps a default value of 01/01/1753 00:00:00 for the CreatedAt and UpdatedAt columns.
• •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.
• •Even though you can configure the data filters in a task, the filters do not work.