Sprint Birthdays
Sprint Birthdays reads a birth date already stored in a WordPress user profile and automatically sends a personalized birthday email. It can use an existing user meta key or a detected ACF date field.
Birthday source and recipients
- Select an existing user meta key or a detected ACF date field.
- Support for common date formats and automatic format detection.
- Filter recipients by WordPress user role.
- Let an individual user opt out from birthday emails in their profile.
- Choose how February 29 birthdays are handled outside leap years.
Emails and notifications
- Send on the birthday or a configurable number of days beforehand.
- Customize the subject, message, signature, logo, colors, button, and footer.
- Use standard variables and custom user meta variables such as
{user_meta:my_key}. - Preview the rendered email and send test messages.
- Optionally inform selected responsible roles before the birthday.
- Optionally send a separate notification to responsible roles after delivery.
- Use Cc or Bcc for grouped responsible-role notifications.
Reliability and administration
- Daily WP-Cron processing with configurable batch size and delay.
- Catch-up processing after missed scheduled tasks.
- Annual duplicate protection for automatic deliveries.
- Delivery history, manual retry, diagnostics, and configurable log retention.
- Administrator alerts when processing fails or the configuration is unusable.
- Integration with WordPress personal-data export and erasure tools.
- Optional detection by Sprint Club without sharing birth-date data.
Sprint Birthdays does not use an external service, add open tracking, or collect telemetry. Email delivery uses the mail system configured for the WordPress site.
Personal data
Depending on the configuration, birthday emails may contain the member’s name, email address, birthday, age, and selected custom user metadata.
The technical log stores only the information required to monitor delivery: the WordPress user ID, destination address, event type, status, timestamps, and an optional error message. The complete birth date is not stored in the log.
The plugin registers a personal-data exporter and eraser. The source birth-date field is not deleted by Sprint Birthdays because it may belong to WordPress, ACF, or another plugin that owns that profile field.