Jo_Pitts1

@Katja_Keesom ,Sadly this isn't yet available in all regions. Those running of the Sydney pod don't yet have it (or even a timeline for it).CheersJo

@KAllen2205 ,have you considered turning bot detection on in Admin > Email > Bot ActivityIf you are considering logging, then this might make for interesting readinghttps://nation.marketo.com/t5/product-blogs/bot-detection-in-logging-mode-unexpectedly-impacts-open-rates/ba-p/331995CheersJo

@Chelsea_Stinnet ,I have edited your post to remove references to the agency that you work for. Self promotion is not allowed.CheersJo

@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