Partition/workspace question

Highlighted
Level 5

Partition/workspace question

We set up our Marketo instance so that partitions/workspaces were based on geography.  Four years later, one of our technology groups would like their own, based on their technology, not a geography.  Is this even possible without resetting our current instance or buying another Marketo license?

18 REPLIES 18
Highlighted

Re: Partition/workspace question

Hi Karen,

You do not need to reset your instance. You can just set up another Workspace for the Technology group.

Create a New Workspace - Marketo Docs - Product Documentation

You can provide this workspace access to all your lead partitions or any specific lead partition that you require. You may need to define a new lead partition if required, however considering that your initial workspaces was based on region, I am assuming you would also have specific partitions for each region and therefore if you build a new lead partition for the technology group you may have conflicting rules.

Hope this helps

Thanks

Floyd

Highlighted
Level 5

Re: Partition/workspace question

Thank you!  I was thinking to remove my partitions, except for our Default, and create two new ones...one for the current contacts I have, and the other for the new tech group.  That way they have access to only their data.  I would then create a new workspace for them too.

Highlighted
Level 7 - Champion

Re: Partition/workspace question

Just to piggy back on Floyd's comment for emphasis - be aware that there may be conflicts across partitions with this approach. A lead can only exist in one partition at a time; if you have any crossover where you might have customers or leads with a relationship required across both partitions, this could prove to be a problem for you.

Highlighted

Re: Partition/workspace question

Yes! Other key takeaways

- Leads need to be deleted or removed or moved from the partition so that they can be deleted.

- Initial Partition rules have to be changed

- References to the Lead partitions have to be removed

- Anonymous leads are still considered as leads in the partition, you will need to reach out to Marketo Support to delete these leads OR if you can identify them with REST API and set delete.

It might be a better option to create a lead partition specific for the tech group, and use the other workspaces to access all the lead partitions. In that way at least you are not deleting any specific lead partition/workspace.

Thanks

Floyd

Highlighted
Level 10 - Community Moderator

Re: Partition/workspace question

...you will need to reach out to Marketo Support to delete these leads OR if you can identify them with REST API and set delete.

REST API can't help w/this.

Highlighted

Re: Partition/workspace question

Interesting, I thought there was a way. Never tested it though so I thought I would throw the idea out.

Guess Marketo Support it is then.

Thanks,

Floyd

Level 5

Re: Partition/workspace question

Can you elaborate on the types of issues that could occur?  I think one would be when I upload lists, and the contact is already part of a different partition.

Highlighted
Level 7 - Champion

Re: Partition/workspace question

Yeah, if you try to import a list with leads in it that exist already in a different partition, then those leads will fail to import (if you're on the default dedupe rules for email address only). There's a fair bit of discussion on this in community - see one here that generated some interesting ideas for solutions: Lead belongs to a different Lead Partition?

But it poses issues for basically any method through which a lead should be created/matched and requires some very careful and well thought out design + rule structuring throughout workspaces if you consider going with deliberate duplicates.

Highlighted
Level 5

Re: Partition/workspace question

Thank you all for your responses.  Extremely helpful!!!!  I am stuck in between a rock and a hard place, as I don't want them to have access to the full Marketo instance, but there may be contacts in this technology area that are currently in my database.