Amy_Goldfine

Did the batch campaign improvements get implemented?

I have stopped using "tradeshow" and "roadshow because it didn't really encompass all the types of events we are doing. At my current company, our channels are- Event - Sponsored: tradeshows, conferences, partner-hosted events, etc.- Event - Hosted: everything from dinners to more traditional roadsh...

I think having a visual is really helpful for everyone. You should definitely be modeling everything out before implementing. I like to use LucidChart, and I color-code which systems are doing what—purple for Marketo, blue for SFDC.

No, no, and no.You can probably reach out to them via LinkedIn because they signed their TOS.HOWEVER, I am not a lawyer, I am not your lawyer, and your company's legal counsel should be helping you develop policies and practices around privacy compliance.

Yes, I have seen this from basically every data vendor. Ultimately, if they sign a DPA with you, they're the ones who are going to take the fall legally. But I completely agree that this is a willful misinterpretation of legitimate interest.

also very expensive if you don't have w/p already!

Oooh yes, look up Universal Tokens, they're great.

Yes, document, document, document. We also have a "changelog" where you have to log every time you change an operational program or database smart list, including why you made the change. Saved me quite a few times.

100% agree with Grace on naming conventions. They will keep your instance clean and make it much easier to scale. For example, we just added scoring for nurture emails only, and I am confident that all nurture emails start with "LN" so I can score on "clicks link in email, email starts with LN".We a...

Our SFDC Admin sometimes renames the friendly label of a field, and then it has a different name in Marketo, which can be really confusing. They changed "Lead Status Reason" to "Closed Status Reason" and I have to think about which is the "real" (SFDC) name when talking to people or writing document...