Partition/workspace question | Adobe Higher Education
Skip to main content
K
KARENBL
Level 5
November 26, 2018
Question

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?

Ce sujet a été fermé aux réponses.

3 commentaires

F
Adobe Employee
falvaresAdobe Employee
Adobe Employee
November 26, 2018

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

    K
    KARENBLAuteur
    Level 5
    November 26, 2018

    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.

    Grace_Brebner3
    Grace_Brebner3
    Level 10
    November 26, 2018

    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.

    K
    KARENBLAuteur
    Level 5
    November 26, 2018

    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.

    Kevin_Weisenber
    Kevin_Weisenber
    Level 4
    November 27, 2018

    Hi karen,

    You will find overtime that the standard marketo partition assignment rules can be somewhat limiting.  @Grégoire Michel​ mentions this in a number of areas but using smart campaigns instead in your operations/default partiton/workspace will provide you with much greater flexibility than the inbuilt feature. Simply identify the audience in the smart list and use the flow action of move partition to get your audience to where you need it including the overlapping members.

    Frank_Carpenter
    Frank_Carpenter
    Level 2
    November 29, 2018

    What your team is asking for is doable. However, it's a bad precedent to set. It will open the food gate to other technology team asking for the same thing. I think the best bet is to create a segmenatation to target the technology, especially with the CASL and GDPR requirements that are in place today. IMHO - Resist making a tech work space at all costs.

    Frank CarpenterSr. Marketing Automation ManagerFive9 Inc.(M) 631-561-8837
    K
    KARENBLAuteur
    Level 5
    December 6, 2018

    Sorry for not responding to this sooner.  The technology in question is separate from our current offerings.  The reason we want to do this is so that they cannot access our current partitions/workspaces.  Do you think it is still a bad idea?

    Frank_Carpenter
    Frank_Carpenter
    Level 2
    December 6, 2018

    Hi Karen,

    I still think a segmentation is the best Idea so you can comply with email regulations regionally.

    Frank Carpenter

    Marketing Automation Manager

    Five9, Inc.

    631 561 8837

    Frank CarpenterSr. Marketing Automation ManagerFive9 Inc.(M) 631-561-8837
    Conditions d'utilisationAccessibility statement

    Loading footer...