Marketo Engage Core Concepts and Administration
Domain 1 tests how a Marketo Engage instance is structured and governed: workspaces, lead partitions, users and roles, channels, tags, program hierarchy, and administrative settings. Expect questions about who can see which leads and assets, how channel statuses drive reporting, and why changing a field can break downstream processes.
Workspaces vs. lead partitions
A workspace is an asset container for programs, emails, and landing pages. A lead partition is a data container for people. Users receive workspace-specific roles, and lead partition access is granted separately. A user can work in Brand A's workspace but still see Brand B's people if partition access is misconfigured.
Channels and tags
Every program needs a channel. The channel defines available program statuses and which status counts as success; Revenue Cycle Analytics and program performance reporting depend on it. Tags such as region, product, and initiative support filtering and reporting, but they do not control behavior.
Program hierarchy
Programs contain smart campaigns, which contain smart lists and flow steps. Local assets belong to one program; Design Studio assets can be shared. Admin controls fields, CRM sync, landing page domains, communication limits, and the audit trail.
Worked example: A company runs two brands and Brand A users must not see Brand B leads. Create two lead partitions, two workspaces, and roles scoped to each workspace with access to only the matching partition. Assign each program to the correct workspace and channel. Reasoning: a workspace role alone is insufficient; partition access is the data boundary.
Traps: confusing workspace visibility with partition visibility; deleting a channel that programs still use; changing a field type after data exists; assuming a system admin role automatically includes every partition; ignoring communication limits during testing.