Frequently asked questions
Can OMailer replace wp_mail() for transactional WordPress and WooCommerce emails?
Yes. OM_Email_Controls hooks phpmailer_init to route every wp_mail() call through your configured SMTP connection. OM_Transactional separately replaces specific email types (password reset, new user, WooCommerce order emails) with OMailer-branded HTML templates.
How do I send a campaign to only part of my list?
Use a segment, not a list. Segments are saved dynamic filters defined by JSON conditions in om_segments (status, tags, custom fields, engagement score, opened/clicked specific campaigns). Conditions within a group are ANDed; groups are ORed. Set list_id to a segment ID when sending.
Are subscriber passwords or API keys stored encrypted?
SMTP passwords are encrypted via OM_SMTP::encrypt_password() using the WordPress auth key. API keys for outbound webhooks and bounce webhooks are also encrypted at rest. OMailer's own API keys for the REST API are hashed.
What happens if my SMTP host goes down during a send?
If you have a backup connection configured, OM_Smart_Routing switches to it on the first wp_mail_failed hook and finishes the current batch. The primary is reinstated for the next batch. Failed individual sends are retried up to 3 times by the queue processor before being marked failed in the email log.
Can I sync subscribers with an external CRM?
Yes, two ways: (1) Outbound webhooks (OM_Webhooks::create()) fire HTTP POST to your endpoint on events like subscriber.created, subscriber.tagged, campaign.opened. (2) The REST API at /wp-json/omailer/v1/ covers subscribers, lists, campaigns, tags, segments. Authenticate with WP Application Passwords or an OMailer API key (X-OMailer-Key header).
Does OMailer handle GDPR consent and erasure requests?
Yes. OM_GDPR registers with WordPress's privacy tools so Tools -> Export Personal Data and Tools -> Erase Personal Data include subscriber records, consent log, campaign history, and custom fields. Every subscribe action logs IP, user agent, consent text, and timestamp to om_consent_log.