Knowledgebase

Sort by:
Issue Description When I navigate to Admin>munchkin, I see option to select workspace. Why is that? Issue Resolution People generally use workspsce either because of their companies geographical location or Business Unit. In each case, the separation is because the marketing assets are completely different.  With that said, If you're using Workspaces in your Marketo account, you probably also have separate web presences that correspond to your workspaces. In that case, you can use the Munchkin tracking Javascript to assign your anonymous people to the correct workspace and partition. This is used to differentiate appropriate leads within workspace with the help of appropriate tracking.     If you don't use the special workspace Munchkin code, the people will be assigned to the default partition that was created when your account was set up. It's named "Default" initially, but you might have changed that in your own Marketo account.   You can only use one Munchkin tracking script for a single partition and workspace on a page. Do not include tracking scripts for multiple partitions/workspaces on your website. I would also like to mention that Landing pages created in Marketo automatically contain tracking code, so you don’t need to put this code on them. Who This Solution Applies To People who use Workspaces and Person Partitions Is this article helpful ? YesNo
View full article
Issue Description Lead was created but does not appear in Workspace A in the Lead Database. Issue Resolution Check if there are any assignment rules that the lead may have qualified for a lead partition associated to another Workspace (e.g. Workspace B) https://docs.marketo.com/display/public/DOCS/Assigning+Person+Partitions+with+Assignment+Rules Check the lead's activity log to see if the lead's partition was changed after it was created to another partition associated to another Workspace (i.e. single flow action or via a smart campaign) Is this article helpful ? YesNo
View full article
Issue Description Is it possible to add Lead partition/Workspace information in a custom Revenue Explorer reporting?   Issue Resolution RCE does not have the ability to segment reports by Lead Partition or Workspace. One possible workaround for leads is to create a custom field on a lead's record and populate it with the partition name.  There is no such option, however, for assets in different workspaces.     Who This Solution Applies To Customers use RCE/RCA Is this article helpful ? YesNo
View full article
Issue Description You have workspaces, and want to reference one workspace's program membership (or reference other assets) within another workspace.   Issue Resolution The solution to referencing across workspaces is to build a Smart List in the target workspace, share the Smart List to the destination workspace, and then reference that Smart List for cross marketing.   For example, let's say that there is particular program membership that you want to access in another workspace. In that workspace, create a Smart List within a folder, and then share that folder to the destination workspace. Sharing the Smart List will allow the List to be targeted within the cross marketing campaign. Who This Solution Applies To Instances with workspaces Is this article helpful ? YesNo
View full article
Issue Description The difference between Workspaces and Partitions and where they are displayed inside the Marketo instance   Issue Resolution The main difference between Workspaces and Partitions is that Workspaces separate assets into different areas and Partitions separate leads. When you look at the navigation tree in Marketing Activities, Design Studio, and Lead Database, you will see the Workspaces displayed, not the Partitions. This is because the Lead Database section is actually showing assets, smart lists and static lists, and not the leads themselves.    To see the Partitions, you would need to go into Admin > Workspaces & Partitions > Partitions. Partitions do not need to have a one-to-one relationship with the Workspaces.  You may have multiple Workspaces and only one Partitions, and you may have multiple Partitions accessible to one Workspace.   Who This Solution Applies To Instances with Workspaces and Partitions enabled. Is this article helpful ? YesNo
View full article
Issue Description User cannot add a field organizer when the user does not have access to all workspaces.   Issue Resolution Unless the user has access to all workspaces, they cannot create a field organizer because field organizers are available in all workspaces.   However, the user still can access and even delete the field organizers that are created by others.   Who This Solution Applies To Instances with workspaces Is this article helpful ? YesNo
View full article
Issue Description You want to know if it's possible to have the same file in both the Default workspace and another workspace. Issue Resolution You cannot have the same file name in different worksapces. For example, if you have a folder in your Default workspace named "Test" and then you try to create another folder called "test" in different workspace, this will not work. The same thing will happen if you try to clone a program to a different workspace and you use the exact same file name. When you are creating new folders or cloning programs, you must use a unique name.
View full article
Issue Description You have Workspaces and Partitions in your instance, and a static list that used to contain certain leads is now missing those leads.  The leads still exist in the database and there is no "Remove from List" activity in the Activity History for the affected leads.   Issue Resolution This can happen when the workspace that contains the static list no longer has visibility to the partition that the lead record is located in.  The lead may have been moved to a different partition, or the partitions that are accessible to the workspace may have been changed.   To confirm whether this is the case, do the following Go to Admin > Workspaces & Partitions and locate the workspace that contains the static list Confirm which partitions are accessible to that workspace Go to the lead record of one of the leads that was in the static list before but is not now. See which partition the lead is in currently. If the lead's partition is not accessible to the static lists's workspace, the lead will not show up in the static list. Is this article helpful ? YesNo
View full article
Issue Description A lead/person completes an action that should trigger a Smart Campaign, but the campaign does not trigger. Issue Resolution If you have Workspaces and Partitions set up on your instance, some leads may not be available to some campaigns, due to workspace and partition restrictions. When a workspace only has access to certain lead partitions, leads in other partitions are unable to trigger campaigns in that workspace. So if Workspace 1 has access to Partitions A and B, leads in Partition C cannot be included in any campaigns for Workspace 1. To resolve this issue, you would need to change the restrictions that are preventing the leads from being able to trigger campaigns in a particular workspace. These can be changed by going to Admin > Workspaces & Partitions > Edit Workspace (with the appropriate workspace selected). Who This Solution Applies To Customers who have Workspaces and Partitions set up in their instance.
View full article
Included in this article Overview Lead Partitions are used to put leads into different groups or "buckets". You can set up the lead partitions however you like, but sometimes you'll need to move a lead from one partition to another. The Product Doc here shows how to move the lead to the other partition, but what if the other partition doesn't show up as able to be selected? Why This Happens When setting up the workspace, you can assign lead partitions to those workspaces to limit which partitions are accessible. You'll need a campaign flow step to move the lead to the new partition, but if the campaign is being run from within a workspace that doesn't have permission to access that partition, then it can't "see" the partition at all and it won't show up as being able to be chosen. How to Fix it To fix this, you'll need to assign the lead partitions to the workspace. This will allow the workspace to "see" that lead partition. 1. Under Admin , click on Workspaces & Partitions . 2. Select your Workspace and click Edit Workspace. 3. Edit the workspace to add the partitions and choose the lead partition you want to move the leads to. Then click the save button. You should now see the lead partition in the selection field to move the leads. You can find more information about Workspaces and Partitions here Understanding Workspaces and Lead Partitions - Marketo Docs - Product Docs
View full article
Included in this article Overview If you have multiple workspaces in your Marketo Instance, your campaigns and smart lists may not pull the leads you would expect. If a lead partition is not visible to the workspace you are working in, there's no way for the smart list to "see" those leads in that partition. For more information about Workspaces and Partitions, check out Understanding Workspaces and Lead Partitions - Marketo Docs - Product Docs Troubleshooting Steps To resolve this, you need to enable access for the specific lead partition to the workspace you are working in. This makes sure the workspace can "see" the leads and get them into your smart list or campaign results. 1. Under Admin , click on Workspaces & Partitions . 2. Select your Workspace and click Edit Workspace . 3. Edit the workspace and add check marks for all partitions that this workspace should be able to access. 4. Click the Save button. Your campaigns should now be able t o access the leads in that partition and reflect the leads expected.
View full article