A few questions about the block field updates feature...

[Chris_Morris1]

We are in the early stages of integrating Marketo with our custom CRM. For the past year and a half, we've used the Spark edition, and the only method of updating a majority of our client detail was via list import.

Now, having upgraded to the Standard version, we are testing integration, and want to temporarily block field updates to our 'Client ID' field via any API function, while we work out other issues.

Before we do this, I have two questions:

1 - If, down the road, we want to activate API updates, the block update field selection works as a toggle switch, correct? I can switch the function on and off via the block updates form pictured below, is that right?

2 - If we do block updates to data in that field via the API, once blocked, it will prevent the API from creating a lead in Marketo and populating that field with 'new' data, is that right? Meaning, we'll have to allow API updates to this field in the future if we intend for Marketo leads to be created via an API function, with that field populated as part of the lead creation process. .

[SanfordWhiteman · Accepted solution]

1 - If, down the road, we want to activate API updates, the block update field selection works as a toggle switch, correct? I can switch the function on and off via the block updates form pictured below, is that right?

Yes.

2 - If we do block updates to data in that field via the API, once blocked, it will prevent the API from creating a lead in Marketo and populating that field with 'new' data, is that right? Meaning, we'll have to allow API updates to this field in the future if we intend for Marketo leads to be created via an API function, with that field populated as part of the lead creation process. .

Not exactly, no.  New data is not an update (which is why you can still set a value on a new lead).

[Chris_Morris1]

Thank you for your help!