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.
