QuestionQ42

VerifiedSection 2A: Marketo Data Architecture Design

An Adobe Marketo Engage Architect is auditing an existing Marketo Engage instance. During the review, the Architect finds more than 1,000 fields that exist only in Marketo Engage, each created for a single, one-time purpose — such as collecting information for one specific event or asking one specific question during that event's registration.

What should the Architect recommend to the client regarding best practices for field creation?

Explanation

Program Member Custom Fields (PMCFs) are limited in number (20 per subscription) and are intended to be built as a small set of generic, reusable fields — for example, PMCF String 1, PMCF String 2, PMCF Boolean 1, PMCF Boolean 2 — that can be placed on the local form of any event program needing custom registration questions, instead of creating a new dedicated person field for every event. Because PMCF values are stored on the program-membership record rather than on the person record, that data is lost if a person's membership in the program changes or they are removed from the program. To preserve the collected responses beyond the life of that program membership, the members must be added to a static list, which retains the record of their participation and associated data outside of the program-membership dependency. This approach eliminates the need to keep creating new single-use person fields, resolving the field bloat found during the audit.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!