Jo_Pitts1

@MineshGo, in addition to what @Chrissy_Nemeth1 has proposed, you'd probably also want to add in a not was sent email filter for the emails you think they might have been sent. Testing that they were sent three emails doesn't mean a 4th (or more) was attempted. It raises a broader question.. THREE m...

@Karen_Black , that's a very broad question so at this point the answer is equally broad: YES!What is it you're looking to achieve?CheersJo

Cool... now we're getting somewhere 🙂 for the one time corrective effort, this is how I'd handle it:Export all the data from Marketo. I'd set up a Marketo view that had the lead ID, email address, unsubscribe, and all your brand preference fields to minimise the number of fields you're exporting.I...

@Guitarrista82, So it sounds like there are two things in play here:A one time corrective action to get all your flags into the right shapeAn ongoing process that keeps things correctly up to date. Does that sound correct?

OK. So If I'm reading this right, you're implementing opt-in flags that work across partitions, but you need a way to synchronise those flags across duplicate records?

@dtavangar , I'm not quite sure what you were responding to here?

@jinawatson,if I'm reading things correctly, inside tags on the page with the form.CheersJo

@SameetShah ,This is pretty commonplace. It's not really about blocking and unblocking however. An easy way to do this is:Turn off the implicit sync between SFDC and Marketo.Include the score and marketing owner in your CSV file that you use for the list import so they get set to the initial values...

@jinawatson,wildly frustrating isn't it when stuff like that happens. What pod are you on? Do you swap between multiple instances within the same browser profile? Have you tried the usual suggestions such as:Clear cookies and cacheTry it in incognitoTry a different browserCheersJo

@Christine_LeBla,yes, you'll need to create new fields. If you're worried about 'clutter' in your Marketo database, give the fields generic names, and use the description to note what they are being used for, and on what date they stop being relevant. That way you'll know when they can be re-used...