If you use the Marketo integration, understanding when a sync fails is important. Luckily we have an Event Log so that you can spot errors as they happen- and so that they can be quickly resolved! 

Billing Plan: The Marketo integration is available on the Premium, Advanced and Enterprise plans. 

In this article, we'll cover: 

• What to look out for to prevent Marketo errors from happening 
• Common Marketo errors and how to resolve them
• Additional Marketo error codes

What to Look Out For

Before we dive in, there are a few things you will want to consider to prevent errors: 

Have you set up the correct permissions to connect Marketo and Drift? When connecting Marketo to Drift, it's very important to enable the correct permissions so that the integration is fully up and running. For instructions on setting up your permissions, you can find them in How to Integrate Drift with Marketo . 

Have you mapped the correct Marketo activities in Marketo to the correct Marketo activities in Drift? Sometimes, Drift can trigger an Invalid Activity type error when we are unable to map the correct activities in Marketo to the correct activites in Drift. To ensure that activities are set up correctly, it's important to follow the guidelines listed below: 

• Marketo Integration - New Conversation Activity
• Marketo Integration - New CQL Score Activity
• Marketo Integration - New Meeting Activity

Is the Marketo cookie turned on? If you use the Marketo Cookie feature in Drift, we will send API calls to your Marketo instance. If your website receives a lot of traction, this can exceed API limits since we create calls based on site traffic. To prevent exceeded API limit errors from happening, you may want to consider turning off the Cookie feature and leveraging Marketo Smart Lists instead. 

Are you bulk-closing conversations? Similar to the Marketo Cookie, if you bulk close conversations in Drift, this can trigger sync errors related to excessive API calls. Since API calls are often the culprit of Marketo sync errors, it's important to refrain from bulk closing conversations if you don't have to. 

Common Errors

Before dissecting an error, it's helpful to understand its makeup. Marketo errors are comprised of two parts: the code and the message.

Anatomy of an Error: 

"Code": the number indicating the type of error we're hitting 
"Message":  the context we provide that explains the error

For more information on each of the Marketo error types and what they mean, this article covers the basics here: (https://developers.marketo.com/rest-api/error-codes/)

Now, let's get into the nitty gritty! Below you can find common errors that occur between Marketo and Drift:  

Marketo error 606 

Error: Failed to push activity of type Lead Conversation to lead with email johnny@appleseed.com. Network Error: MarketoError{code=606, message=Max rate limit '100' exceeded with in '2' secs}

Meaning: If you bulk-close a lot of conversations at once or if your website has a lot of traffic, this can trigger a 606 error. This means that more than 100 API Calls in 20 Seconds which will throttle your API. Also, if you are currently using Marketo Smart Lists in your playbook targeting, we will be checking those Smart Lists for the Marketo cookie when site visitors interact with Drift (even if the "identify visitors with the Marketo cookie" box is unchecked). Please keep in mind that if you are targeting a Marketo Smart List in playbook targeting, we will still make API calls for that Smart List even if the playbook is turned off.

Solution: To resolve this, you can resync by opening and closing the conversation had with said contact in Drift. To check to see if it the sync went through successfully, you find the event in your Event Log!

Marketo error 607

 

Error: MarketoError{code=607, message=Daily quota '50000' reached}

Meaning: The number of calls in the past 20 seconds was greater than 100

Solution: Your quota can be found in your Admin->Web Services menu.  You can increase your quota through your account manager. https://developers.marketo.com/rest-api/error-codes/. This is not strictly due to Drift, if you have Marketo integrated with multiple other platforms this can happen. You can reach out to Marketo to have this rate increased but it does cost extra.

Marketo error 1003

Error: Failed to push activity of type Lead Conversation to lead with email email@website.net. Network Error: MarketoError{code=1003, message=Invalid activity type id '46}

Meaning: An error code 1003, means that a Marketo activity is not being mapped appropriately in Drift. Marketo activities need to be mapped at a 1:1, meaning that the same activity in Drift needs to be mapped to the same activity in Marketo. 

Solution:  Check the Marketo Synced Data in your Marketo Integration. At the bottom are the Drift Activities. If activities are not matched, you can resolve by readjusting and saving them.

Marketo error 1029

Error:  Failed to start export job due to error from Marketo: [MarketoError{code=1029, message=Export daily quota 500MB exceeded.}]

Meaning: The 1029 error is triggered when we attempt to queue more than 10 jobs in the Bulk Extract APIs.

Solution: Drift is set to retry until it can secure a spot on the queue so this error will not affect functionality of your Marketo syncs. You can decrease the queue or can reach out to Marketo for more information about increasing the Bulk Extract limit.

Additional Error Codes

This article will be periodically updated with other common errors that our customers see. For a full list of Error Codes from Marketo, check out their knowledge base here: Marketo Error Codes