Purpose

Fires after mam_user_roles_manager finishes creating a user via the mam-main registration flow. Use it for post-registration cleanup — persist app-user metadata, queue welcome flows, sync with external systems.

Distinct from WP’s native user_register action: this fires only when the user was created through mam-main (not through wp-admin → Users → Add New, for example).

Signature

$user_id = apply_filters(
    'mam_user_roles_after_create_user',
    int   $user_id,
    array $registration_data
);

Returns: int — the user id (typically unchanged).

Example: persist a custom app-user metadata key

add_filter( 'mam_user_roles_after_create_user',
    function ( int $user_id, array $registration_data ): int {

        // Persist an app-user-only flag.
        update_user_meta( $user_id, 'my_plugin_signup_source', $registration_data['source'] ?? 'app' );

        // Trigger a downstream side effect.
        do_action( 'mam_notification_send_message', array(
            'message_type' => 'mam-my-plugin-welcome_email',
            'recipient_id' => $user_id,
        ) );

        return $user_id;
    },
    10, 2
);

Related identity-lifecycle hooks

Gotchas

• Fires only for mam-main registrations. WP-admin user creation doesn’t fire this. If you need to handle every user creation, hook WP’s user_register instead.
• $user_id is the canonical return. Don’t return anything else — downstream subscribers expect an int.
• $registration_data shape varies by registration path (email signup, social, magic-link, phone-code). Defensively check keys.
• The bundled welcome email fires from the registration flow itself via mam-user-roles-welcome_email. Don’t double-send by firing the same notification from this filter.

Related articles

• Recipe: Customize onboarding
• Hook: mam_user_logged_in
• Hook: mam_add_fields_to_user_profile
• Hook: mam_user_roles_save_addl_user_profilefield{key}
• Hook: mam_notification_send_message

Metadata