New Instance Best Practices: Document Your Setup new-instance-best-practices-document-your-setup
Now that you’ve learned the key product areas to set up for a new Marketo Engage instance, the next step is to create documentation for your instance configuration and tech stack. Whether creating it via spreadsheet or a project management application, your documentation will be a great resource to track progress and record details, as well as keep your instance structured and sustainable for future marketers within your organization.
Data data
-
Gather a list of data sources that records will be pulled from to import into Marketo Engage.
-
If you are importing from multiple data sources, consider using Master Lists or creating a custom field on the person record to denote the data source.
- If leveraging the native sync between Marketo Engage and your CRM, carefully consider what fields you want to sync between systems. Not every field needs to be synced, so be strategic about your data flows.
Documentation documentation
-
Document the current users in your instance for safety reasons. The following details should be included at a minimum (and are all visible by going to Admin > Users & Roles):
-
Name
-
Email
-
Login
-
Role
-
Access Expiration Date
-
User Created Date
-
Most Recent Log In Date
NOTE: You can also expand on this to include documentation around roles/permissions.
- As a Marketo Engage Product Admin, develop an internal process to audit and update the Marketo Engage user list at a regular cadency. To make changes to the list of users in ÃÛ¶¹ÊÓƵ Admin Console, consider , such as uploading a .CSV, using the User Management REST API, etc.
- Document the agreed folder structure, standard naming conventions for programs, assets, etc., and the why behind the decisions made. Learn more about the best practices here.
- Create a changelog where you can document what's changing in your instance and the why of the modifications. Learn more about the best practices here.
- Create a User Playbook or Admin Playbook for internal users onboarding to the instance.
-
Align the internal marketing team's expectations of Marketo Engage with Marketo Engage's capabilities.
-
Identify the teams that will be your stakeholders in the Marketo Engage instance and document their goals to achieve using Marketo Engage as a technology.
-
Document how workspaces are defined, and how that relates to database partitions (e.g., a Global workspace that shows everyone vs. business sectors).
-
Import new records to the appropriate partition.
-
Define the value in your CRM that places users in the appropriate partition.