What are the custom fields and tags that mailfloss updates and which ESPs support them?

mailfloss will update custom fields or tags for our supported esps unless otherwise stated, esp tags and custom fields are created for you automatically unless otherwise stated, esps utilize custom fields for updates rather than tags for tag updates, we support infusionsoft, gist, and sendlane the custom fields properties and tags we sync to your esp are name "mf validation passed", label "mailfloss validation passed", description "false, if the email failed mailfloss validation " name "mf reason", label "mailfloss reason", description "the reason mailfloss failed this email " name "mf mode", label "mailfloss mode", description "normal, aggressive, or custom floss mode " name "mf flossed on", label "mailfloss flossed on", description "the date mailfloss validated this email " name "mf status", label "mailfloss status", description "the status of this email it can be 'undeliverable', 'risky', or 'unknown' " name "mf fixed", label "mailfloss fixed", description "set to true if the email address typo was fixed successfully " name "mf suggestion", label "mailfloss suggestion", description "a potential suggested email address, if one exists " now you can use this data to sync your esp with your other crm systems by looking up the contact and looking for the mf validation passed property any marked false by mailfloss you can now update in your other crms, run automations and create reports note that mailfloss only updates a contact with custom fields if the contact failed mailfloss validation here are the tags we use for ghost and gohighlevel infusionsoft, gist, and sendlane used these tags prior to switching to custom fields "mf failed invalid", "mf failed spam", "mf failed role", "mf failed banned", "mf failed disposable", "mf failed illegitimate", "mf failed available", "mf failed unverified", "mf failed blacklisted", "mf failed bounced", "mf failed complained", "mf failed accept all", "mf failed nonexistent", "mf failed deactivated", "mf failed inbox full", "mf status undeliverable", "mf status risky", "mf status unknown", "mf fixed true", "mf suggestion true" please note we plan on migrating to custom fields with these providers in the future