Double Opt-In Recency

Set re-confirmation requirements for inactive contacts

Double Opt-In Recency

Double opt-in recency is an advanced compliance feature that requires contacts to periodically re-confirm their subscription after a defined period of inactivity. This goes beyond standard double opt-in by ensuring that your consent records stay fresh and that you're not continuing to email contacts based on stale, years-old consent.

Why Recency Matters

Regulators and privacy advocates increasingly question whether consent given years ago is still valid, especially if the contact hasn't engaged with your emails since. Recency requirements help you:

• Maintain compliance: Some interpretations of GDPR suggest consent should be refreshed periodically. Recency automation ensures you stay ahead of evolving standards.
• Improve list quality: Contacts who re-confirm are demonstrably engaged. Those who don't are likely disengaged and may be hurting your deliverability.
• Reduce risk: Stale email addresses can turn into spam traps over time. Re-confirmation catches these before they damage your sender reputation.
• Show accountability: Having recent consent records demonstrates proactive compliance — a strong position if you ever face a regulatory inquiry.

Configuring Recency Settings

1. Navigate to Organization → Compliance Settings.
2. Find the Double Opt-In Recency section.
3. Set the double_optin_recency_days value. This defines the maximum number of days since a contact's last confirmation before they are flagged for re-confirmation. Common values range from 180 to 730 days (6 months to 2 years).
4. Save your changes.

When this feature is enabled, Mailnaptic evaluates each contact's last confirmation date against the recency threshold. Contacts whose confirmation has expired are transitioned to a pending re-confirmation status.

The Re-Confirmation Flow

When a contact's consent expires based on your recency setting:

1. The contact's status changes to pending, automatically excluding them from future campaign sends.
2. If you have a re-confirmation automation set up, it triggers and sends the contact a re-confirmation email.
3. If the contact clicks the confirmation link, their status returns to active and the consent timestamp is refreshed.
4. If the contact does not re-confirm within your specified window, they remain in pending status and are excluded from campaigns.

Setting Up a Re-Confirmation Automation

Create an automation that triggers when a contact's status changes to pending. Design a friendly email explaining that you want to make sure they still want to hear from you, with a prominent confirmation button. Consider sending a follow-up reminder 7 days later if they haven't responded. Use the pre-made automation templates as a starting point if needed.

Graceful Fallback

If the double_optin_recency_days column hasn't been added to your database yet (migration not run), Mailnaptic gracefully ignores this setting and operates normally. No contacts will be affected until the migration is applied and the setting is explicitly configured.

Balancing Compliance and Engagement

Set your recency window thoughtfully. Too short (under 90 days) and you'll annoy active subscribers with frequent re-confirmation requests. Too long (over 2 years) and the feature provides minimal benefit. For most organizations, 365 days strikes a good balance between compliance diligence and subscriber experience.