MailPoet bridge - Animam Documentation

The MailPoet bridge lets the agent subscribe a visitor to one of the tenant’s lists. Only lists explicitly whitelisted in Settings → Animam → MailPoet bridge are visible to the agent — the agent cannot subscribe a visitor to anything the tenant hasn’t approved.

How it works

The agent calls wp_list_newsletter_lists and only sees the whitelisted lists.
After the visitor opts in (e.g. “I’d like your monthly newsletter”), the agent calls wp_subscribe_newsletter with email + first name.
MailPoet runs its standard pipeline: double opt-in stays on, the confirmation email goes out, and the subscriber lands in the list.

Why this stays compliant

	Animam-owned list	MailPoet bridge
Double opt-in	re-implement	✅ stays on (MailPoet default)
Unsubscribe link	re-implement	✅ standard MailPoet footer
GDPR consent record	parallel store	✅ MailPoet-managed
Welcome / drip emails	re-implement	✅ existing automations fire
Deliverability config	parallel SMTP	✅ existing MailPoet sending method

Whitelisting lists

In Settings → Animam → MailPoet bridge, check the lists the agent is allowed to subscribe visitors to. Anything unchecked is invisible — the agent literally cannot see it via wp_list_newsletter_lists. Common pattern: keep your transactional and internal lists unchecked, whitelist only the public newsletter / marketing lists.

Plan

Bridges require the Visitors plan (€19/month) or higher — the bridges capability. See WordPress pricing.