Actions

  • Action: mam_manage_favorites

    Action fired when the app reports a favorite-toggle event. Sibling plugins subscribe to persist the change in their own usermeta — mam-geodirectory uses gd_user_favourite_post.

  • Action: mam_main_iap_subscription_has_changed

    Action fired when the in-app purchase subscription state shifts. Sibling plugins (typically mam-inapp-purchase-manager) update entitlements, gate features, or dispatch notifications.

  • Action: mam_user_logged_in

    Action fired after a successful app login. Use for analytics, last-seen updates, post-login data warming. Distinct from WP’s wp_login — fires only for app logins through mam_login_manager.

  • Action: mam_form_manager_send_notifications

    The contract between forms-manager and notifications-manager. Fired after a form submission completes; subscribers fire mam_notification_send_message to dispatch confirmation emails / pushes / SMS. Frozen contract — go through this hook,…

  • Action: mam_notification_send_message

    The primary notification entry point. Action signature: do_action(‘mam_notification_send_message’, $message). Routed by MAM_Notification_Dispatcher to email/SMS/push channels per the type registry. Frozen contract — legacy filter registration retained per SC #175.

Need Support?

Can’t find the answer you’re looking for? Don’t worry we’re here to help!