How wp_mam_notifications_history records every dispatch, how the in-app notification center reads it, and the opt-out tables (per-user email opt-out, SMS STOP, push permission revocation).

How email, SMS, and push notifications are queued and drained by the mail-cron-manager subsystem. Covers the wp_mam_mail_queue and wp_mam_pn_text_queue tables, the per-tick batch sizes (50 email / 20 PN+SMS), and…

How replacement tokens (e.g., [user_login], [passwordcode], [order_id]) work in notification templates: per-type token list declared in mam_notification_list, supplied at fire time, substituted by the channel sender.

How sibling plugins register notification types via mam_notification_list. Each type declares its slug, replacement tokens, default-on channels, and description. The dispatcher resolves the message_type to one of these entries.

How notifications work in MAM Suite: a single mam_notification_send_message action routed by MAM_Notification_Dispatcher to email/SMS/push channels, driven by a notification-type registry with 68+ subscribers.