Handle custom fields and fixed typos: automated rules and exceptions

understanding the "mf fixed" field when our automated system corrects a typo in an email address, the corrected email address is labeled with a custom field called "mf fixed" if auto update custom fields is set as the action option, and this will be set to "true " this field is your key to identifying which email addresses have been successfully corrected handling unsubscriptions with automated rules to maintain control over your email list and ensure that email addresses are handled appropriately, you may have automated rules set up to unsubscribe addresses that have failed our verification processes to address cases marked as "mf fixed = true," you can create an exception in your automated rules creating an exception rule log in to your esp access your email service provider's dashboard navigate to automation or rules find the section in your esp where you manage automated rules edit or create a rule depending on your esp, you may need to edit an existing rule or create a new one set conditions define the conditions that trigger the rule in this case, you're looking for email addresses where "mf fixed = true " specify action determine the action you want to take for these addresses since they have been successfully corrected, you can add an exception by excluding them from the unsubscription process save the rule be sure to save the rule to apply it to your email list we are using drip for this screenshot, but the process is similar for all esps why create this exception rule? by creating an exception rule for "mf fixed = true," you ensure that email addresses successfully corrected by our system are not mistakenly unsubscribed this helps you maintain a clean and accurate email list while preventing the loss of valuable subscribers due to typos