1 Reply Latest reply on Oct 15, 2013 9:33 AM by 14684

    Advice on lead partitions and workspaces, please?

    Kristen Skunza
      I have a situation where a manufacturer and multiple resellers will need to share a single Marketo instance, and I am trying to figure out the most efficient way to manage lead data and campaigns across all of these channels. A few complications include:

      The manufacturer and the resellers will have some leads that are the same (same email address) between their databases. The manufacturer wants to keep this lead and market to them accordingly, while the reseller will also want to keep this lead to market to.

      We will need to be able to clone assets from the manufacturer’s campaigns in to the resellers’ campaigns.
      I am somewhat familiar with data partitioning and workspace capabilities, but I don’t know if this will work since leads can’t be shared between partitions.

      Has anyone ever encountered a situation like the one explained above? If so, how did you handle it? Did you have success with lead partitions and workspaces? What other options are available?

      Thanks for the help!
        • Re: Advice on lead partitions and workspaces, please?
          This is complicated and will come down to some business rules and rules of engagement.

          You can create a partition for each reseller that is dedicated to them - you can also create a corresponding workspace for them to build their campaigns in. This will allow them to do their one to one communications with the leads that are "theirs".

          The manufacturer would have a workspace that includes the reseller partitions and the default partition - so they get maximum impact. Assumption is resellers are ok with sharing this information in exchange for the service or other negotiated value.

          The trick will be for future new adds to DB - only one reseller gets it and that would be first to submit unless you intervene.

          Another consideration is which audience is the end-user opting in to communications with - will need to be spelled out clearly.

          As for sharing - You would either need to have a master admin that can clone and move across workspaces or consider building in a separate sandbox instance and allowing importing of programs into the various workspaces.