How to automate personalized user emails in WordPress

Write down the events that should send messages, such as a new registration, a profile update, a password reset, a membership change or a purchase. Decide who receives each message and whether it is a service notification or marketing email.

Keep each trigger specific. Sending one message every time a profile is saved can create duplicates, especially when another plugin updates user data in the background.

For a small number of notifications, add a small custom plugin rather than placing the code in a parent theme. WordPress provides the user_register action when a user is created and the profile_update action when an existing user is updated. Your callback can load the user, assemble the message and call wp_mail().

Use a condition inside the callback so the email is sent only for the change you want. The manual route is fine for one or two fixed notifications, but it becomes difficult to maintain when you need an editor, reusable templates, translations, logs, delays or several user activity triggers.

Load the recipient with the user ID passed by the hook, then use approved account fields such as the display name, email address and selected user metadata. Replace your own tokens before sending, for example turning {{display_name}} into the user’s display name.

Escape values for the email format you are using, validate the recipient address and never include a password or other secret in an email. If custom profile fields are saved by another plugin, confirm that those fields exist before building the message.

WordPress sends mail through wp_mail(). Its default content type is plain text, so add an HTML content-type header only when your message is properly formatted as HTML. A successful return value means WordPress handed the message to the mailer; it does not prove delivery.

Set a clear subject, a valid From address on your domain and a useful Reply-To address. If you temporarily change the global content type with a filter, reset it after sending so other WordPress emails are not unexpectedly changed.

Configure WordPress to use an SMTP relay or transactional email provider rather than relying on an unconfigured server mail function. WordPress documentation notes that self-managed servers may need a local mail transfer agent or remote SMTP relay, and recommends checking domain authentication such as SPF, DKIM and DMARC for deliverability.

Send tests to several providers and check spam folders, the From address, links, mobile layout and non-ASCII characters. If messages fail, log the error with the wp_mail_failed action; remember that mail can still be accepted by the server and later filtered or rejected by the recipient.

For several activity-based emails, install and configure GeoDirectory Dynamic User Emails. It is designed for GeoDirectory sites and provides activity-triggered templates, dynamic placeholders, user notifications, multilingual support and email logging from the WordPress dashboard.

Create a template for each trigger, insert only the placeholders supported by the plugin, select the recipient and enable the trigger. Send a test before activating the workflow. This is faster than maintaining custom callbacks when you need editable templates or multiple personalised user notifications, while the manual route remains suitable for a small fixed setup.