SPRINT BIRTHDAYS
Sprint Birthdays compatibility with REEID Translate
Sprint Birthdays compatibility with REEID Translate is being reviewed using official plugin documentation. Automatically sends personalized birthday emails to WordPress users using a configured birth-date source from existing user meta or a detected ACF date field. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Sprint Birthdays does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Sprint Birthdays is documented in the Other category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Sprint Birthdays compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Automatically sends personalized birthday emails to WordPress users using a configured birth-date source from existing user meta or a detected ACF date field.
- Supports selecting recipients by WordPress user role and allows individual users to opt out of birthday emails via their profile.
- Sends emails either on the birthday or a configurable number of days beforehand, with configurable handling for February 29 birthdays outside leap years.
- Provides email template customization (subject/message/signature/logo/colors/button/footer) and supports standard variables plus custom user meta variables such as `{user_meta:my_key}`; includes email preview and test sending.
- Uses daily WP-Cron processing with configurable batch size and delay, including catch-up processing after missed scheduled tasks.
- Implements delivery reliability features including annual duplicate protection for automatic deliveries, delivery history, manual retry, diagnostics, and configurable log retention.
- Integrates with WordPress personal-data export and erasure tools, and registers a personal-data exporter/eraser; does not store the complete birth date in its delivery log.
TRANSLATION BOUNDARY
Sprint Birthdays capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Sprint Birthdays and REEID Translate FAQ.
What does Sprint Birthdays do?
Sprint Birthdays has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Sprint Birthdays have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Sprint Birthdays?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Sprint Birthdays in a multilingual WordPress workflow.
REEID documents Sprint Birthdays functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.