explanation
-
The notification dispatcher: how one action fans out to channels
Why MAM Suite routes every email, SMS, and push through one mam_notification_send_message action, and how the dispatcher fans it out across channels.
-
Notifications explained: channels, queue, cron, and template tokens
How channels, the dispatch queue, cron, and bracketed replacement tokens work together to turn one fired message into delivered email, SMS, and push notifications.
-
Login and authentication concepts: email, magic link, social, phone code
How your MAM app checks who’s signing in — across email, magic link, social, and phone-code methods — how that login maps to a WordPress role, and what ‘require login’…
-
The MAM app lifecycle: enroll, build, brand, preview, publish, maintain
A map of the whole MAM journey from site enrollment to a live app, and which MAM tool owns each stage so you always know where you are.
-
How sibling plugins extend your app: the filter-driven architecture
Every MAM feature plugin injects into the app through WordPress hooks instead of importing core classes, and filter priority decides the order they run in.
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
