An Adobe Marketo Engage Architect needs to audit an existing Marketo Engage instance. Upon inspection, more than 1000 fields that only live in Marketo Engage were created for a single use to collect information for a specific event, or ask a specific question during the registration of an event.
What should the Architect recommend to their client regarding field creation best practices?
Creating a set of temporary program member fields and using them on local forms for every event that requires custom questions is a good way to avoid creating too many fields that only live in Marketo Engage. Adding the leads to a static list can help retain the data if needed.
https://experienceleague.adobe.com/docs/marketo/using/home.html
Currently there are no comments in this discussion, be the first to comment!