This document provides an overview of the recent service issue that impacted Marketo customers beginning on July 28, 2020, or July 31, 2020, depending on the data center they are located in. If you are unsure if your instance was impacted, please contact Marketo Engage Support at https://support.marketo.com.
A bug introduced in the 2020 Q3 release inadvertently caused duplicate externalCompanyIds to be created in customers’ Marketo Engage instances. When a lead was reparented to a different company via externalCompanyId, the losing company would have also been updated with the same externalCompanyId. This would have caused two companies in Marketo to have the same externalCompanyId. This behavior violates the uniqueness of such value.
Below are two scenarios that should help depict how your data may have been affected by this issue.
Scenario 1
A lead may not have been initially associated with a company with externalCompanyId.
Payload of create/update lead
{
"lookupField":"email",
"input":[
{
"email":"testmarketo@adobe.com",
"externalCompanyId":"ABCDEFG"
}
]
}
Below is an outline of what the data would look like in the Marketo Engage database.
Initial Dataset
Mkto Org Id |
Name |
City |
External Company Id |
Lead Id |
Lead Email Address |
1 |
Adobe |
San Mateo |
ABCDEFG |
1 |
|
2 |
NULL |
NULL |
NULL |
2 |
Final Incorrect Dataset caused by the bug (after Step 5)
Mkto Org Id |
Name |
City |
External Company Id |
Lead Id |
Lead Email Address |
1 |
Adobe |
San Mateo |
ABCDEFG |
2 |
|
2 |
NULL |
San Jose |
ABCDEFG |
1 |
What would have been the correct behavior?
Mkto Org Id |
Name |
City |
External Company Id |
Lead Id |
Lead Email Address |
1 |
Adobe |
San Jose |
ABCDEFG |
1 |
|
|
|
|
|
2 |
Scenario 2
A lead might have been reassigned from one company to another due to job change. As an example, let’s say the following data is in your system.
Mkto Org Id |
Name |
External CompanyId |
Lead Id |
Lead Email Address |
1 |
Company A |
123 |
1 |
|
|
|
|
2 |
|
2 |
Company B |
234 |
3 |
Assume Lead Id=2 now works for Company B and the lead was updated to be associated to company/organization with externalCompanyId=234 and a new email address. The lead would have been reparented successfully. However, Company A would have their externalCompanyId updated to 234 as well, which would have resulted in the following.
Mkto Org Id |
Name |
External CompanyId |
Lead Id |
Lead Email Address |
1 |
Company A |
234 (Wrong Value) |
1 |
|
2 |
Company B |
234 |
2 |
|
|
|
|
3 |
How to possibly fix the data discrepancy?
As indicated in the examples above, it is not possible for Marketo to determine an appropriate data fix since the correct externalCompanyId is no longer available. In addition, it’s difficult to say which leads should be associated with a certain company or create a formula to determine the winning company. Your company’s CRM system should be the source of truth for this information.
While we can’t fix this data ourselves, we can provide the list of affected leads, companies, and Change Data Value activities for the field Contact Company. This list can be obtained by submitting a case to Marketo Engage Support.
There are three files that will be provided to you.
In order to perform the data fix on your own, you will first need to determine which company should be the winner of the duplicates and reparent leads to the correct company/organization, if needed. This can be done using a combination of Marketo Leads and Companies API.
In cases where the loser organization shouldn’t have an externalCompanyId, the data fix could follow the steps below.
In cases where the loser organization’s externalCompanyId was updated to have the same value as the winner organization, the loser organization is an actual company that should be retained in the system.
If you have any additional questions, please Contact Marketo Engage Support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.