Skip navigation
All Places > Champion Program > Blog > Authors Jenn DiMaria

Champion Program

2 Posts authored by: Jenn DiMaria Champion

Hey, #MKTGnation!

 

Summer's (kind of?) over, the PSLs are flowing, and the gang got back together to answer the top questions we hear every day on the job. I may or may not have ranted just a little.

 

Some of my personal favorites include:

  • Why is Marketo broken? (ie: the one that makes my eye twitch)
  • How mature is my Marketo instance?
  • Why does it take so long to change a template? (spoiler: we have different definitions of "templates")
  • Do I actually know how to troubleshoot? (Okay, this one isn't a real question but we cover why it's crucial to understand troubleshooting in our jobs)

 

 

What are the most common questions YOU receive about Marketo (or your job)? Are there common ones you've been able to stop from popping up time and time again? Any pet peeve questions?

 

Sydney Mulligan Enrico Deleon Juli James

Click here to watch!

 

So it seems like all the cool kids are using (or at least know about) workspaces and partitions, but there’s not a whole lot of information to help out those of us who are in dire need of seeing them in practice. And as we all know with Marketo, there are about a billion different ways to go about doing something and still get it done correctly. Today, we’re hoping to get into at least a little bit more use-case detail about both workspaces and partitions, when it’s best to use on or the other (or both), and hopefully get into more detailed Q&A.

 

Some questions we asked included:

 

  1. What are workspaces and how do they differ from lead partitions?
  2. What’s a use case (ie: why would you want a lead partition)?
  3. Can anything be shared across partitions?
  4. So let’s say a lead exists in two partitions and proceeds to fill out a form. Does their information get updated in both partitions?
  5. Can partitions sync to multiple SFDC instances?
  6. How do you deal with shared data?
  7. How do companies standardize on naming, program statuses, etc considering the other division might be around the world operating as different businesses?

 

Important Reading: