New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Email marketing for WordPress with hosted and native signup forms, subscriber tools, RSS newsletters, and signed integrations. | You have to log in to add a translation. | Details |
Original untranslated
Email marketing for WordPress with hosted and native signup forms, subscriber tools, RSS newsletters, and signed integrations.
You have to log in to edit this translation. |
|||
| ↑ | Maildroppa | You have to log in to add a translation. | Details |
Original untranslated |
|||
| Update signup sources to register WPForms for future website signup attribution. The connected backend must support the WPFORMS integration type. | You have to log in to add a translation. | Details | |
Original untranslated
Update signup sources to register WPForms for future website signup attribution. The connected backend must support the WPFORMS integration type.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| Delivery uses the same authenticated WordPress signup PUT endpoint, central double opt-in, retry schedule, 24-hour expiry, eight-attempt limit and 30-day failed-record retention as Contact Form 7. WP-Cron is required. Changes to account, form, mapping or consent and deactivation of WPForms stop queued requests. Failed signups cannot be restarted without new consent. Account reset and opted-in uninstall remove Maildroppa metadata without deleting WPForms forms. | You have to log in to add a translation. | Details | |
Original untranslated
Delivery uses the same authenticated WordPress signup PUT endpoint, central double opt-in, retry schedule, 24-hour expiry, eight-attempt limit and 30-day failed-record retention as Contact Form 7. WP-Cron is required. Changes to account, form, mapping or consent and deactivation of WPForms stop queued requests. Failed signups cannot be restarted without new consent. Account reset and opted-in uninstall remove Maildroppa metadata without deleting WPForms forms.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| The plugin adds an optional, initially unchecked newsletter checkbox before the submit button. JavaScript generates a random submission request ID before enabling it. Only successfully processed, non-spam submissions with consent queue the mapped signup fields, selected topics, displayed consent, source URL and form ID, and submission time. Name fields mapped to first name send the first-name component. Message fields and attachments are excluded. Contact form processing and WPForms notifications remain independent of newsletter consent. | You have to log in to add a translation. | Details | |
Original untranslated
The plugin adds an optional, initially unchecked newsletter checkbox before the submit button. JavaScript generates a random submission request ID before enabling it. Only successfully processed, non-spam submissions with consent queue the mapped signup fields, selected topics, displayed consent, source URL and form ID, and submission time. Name fields mapped to first name send the first-name component. Message fields and attachments are excluded. Contact form processing and WPForms notifications remain independent of newsletter consent.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| Requires WPForms Lite or Pro and a connected Maildroppa service with the WordPress signup API. An administrator configures each form under Settings > Maildroppa in the WPForms builder. Available fields, topics and signup API availability are requested from the configured Maildroppa API, using the API key. Maildroppa stores the field mapping, topic IDs and labels, consent text, and account/API/site binding in separate WordPress metadata. This configuration is not included in WPForms exports or duplicated forms. | You have to log in to add a translation. | Details | |
Original untranslated
Requires WPForms Lite or Pro and a connected Maildroppa service with the WordPress signup API. An administrator configures each form under Settings > Maildroppa in the WPForms builder. Available fields, topics and signup API availability are requested from the configured Maildroppa API, using the API key. Maildroppa stores the field mapping, topic IDs and labels, consent text, and account/API/site binding in separate WordPress metadata. This configuration is not included in WPForms exports or duplicated forms.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| Is the plugin source available? | You have to log in to add a translation. | Details | |
Original untranslated
Is the plugin source available?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Does Maildroppa log personal data? | You have to log in to add a translation. | Details | |
Original untranslated
Does Maildroppa log personal data?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| How does WPForms newsletter signup use the Maildroppa API? | You have to log in to add a translation. | Details | |
Original untranslated
How does WPForms newsletter signup use the Maildroppa API?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| WPForms uses the same signup API and delivery queue as Contact Form 7. Only successful submissions with newsletter consent are forwarded. See the WPForms FAQ below for setup, transmitted data, retention and website attribution. | You have to log in to add a translation. | Details | |
Original untranslated
WPForms uses the same signup API and delivery queue as Contact Form 7. Only successful submissions with newsletter consent are forwarded. See the WPForms FAQ below for setup, transmitted data, retention and website attribution.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| Yes. The plugin records completion after all listeners of the corresponding WordPress action return successfully. If a later listener fails or the request terminates, Maildroppa can retry the event and an earlier successful listener can run again. Each listener must use the stable event ID in its second action argument to prevent duplicate business effects. Replay protection after completion is not an exactly-once guarantee for custom listeners. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. The plugin records completion after all listeners of the corresponding WordPress action return successfully. If a later listener fails or the request terminates, Maildroppa can retry the event and an earlier successful listener can run again. Each listener must use the stable event ID in its second action argument to prevent duplicate business effects. Replay protection after completion is not an exactly-once guarantee for custom listeners.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Local data is preserved by default. Complete local cleanup must first be explicitly enabled under <strong>Maildroppa > Settings > Data & uninstall</strong> and is blocked while webhook subscriptions or reconciliation work remain. Remote Maildroppa data is never deleted by uninstall. | You have to log in to add a translation. | Details | |
Original untranslated
Local data is preserved by default. Complete local cleanup must first be explicitly enabled under <strong>Maildroppa > Settings > Data & uninstall</strong> and is blocked while webhook subscriptions or reconciliation work remain. Remote Maildroppa data is never deleted by uninstall.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The plugin retries delivery at bounded intervals. Pending events expire after 30 days and cannot be sent or retried afterwards. Failed records can be diagnosed or deleted under <strong>Maildroppa > Settings > WordPress users</strong>, including when the API connection is unavailable. Retrying requires the original account and an event younger than 30 days. Failed records are eligible for deletion 30 days after failure, so an expired event can remain locally for about 60 days after creation. Daily cleanup depends on WP-Cron running while the plugin is active; missed cron runs delay deletion. The WordPress personal-data tools include these records. | You have to log in to add a translation. | Details | |
Original untranslated
The plugin retries delivery at bounded intervals. Pending events expire after 30 days and cannot be sent or retried afterwards. Failed records can be diagnosed or deleted under <strong>Maildroppa > Settings > WordPress users</strong>, including when the API connection is unavailable. Retrying requires the original account and an event younger than 30 days. Failed records are eligible for deletion 30 days after failure, so an expired event can remain locally for about 60 days after creation. Daily cleanup depends on WP-Cron running while the plugin is active; missed cron runs delay deletion. The WordPress personal-data tools include these records.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. Active inline Maildroppa forms can also be placed in a classic WordPress widget area. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. Active inline Maildroppa forms can also be placed in a classic WordPress widget area.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Yes. Active inline hosted forms and configured theme-styled forms each have a dedicated Maildroppa block. | You have to log in to add a translation. | Details | |
Original untranslated
Yes. Active inline hosted forms and configured theme-styled forms each have a dedicated Maildroppa block.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.