Goal

Activate mam-gravity-forms-manager and confirm that Gravity Forms is correctly wired into the MAM Suite form pipeline. After this recipe, every active Gravity Form on the site will be available in MAM dropdowns that list form sources, and app-submitted forms routed through the MAM pipeline will create real Gravity Forms entries.

Prerequisites

• WordPress admin access
• Gravity Forms installed and active (any license tier)
• MAM Suite installed with mam-main 1.9.1 or later
• A MAM Suite plugin entitlement that includes mam-gravity-forms-manager

If Gravity Forms is not active, the plugin loads without error but does nothing — see Common gotchas.

How activation actually works

mam-gravity-forms-manager does not have an admin page of its own. It registers all of its hooks inside its constructor only after passing two checks:

1. The MAM Suite entitlement filter (mam_plugin_entitlement) must return a non-blocked state for the slug mam-gravity-forms-manager.
2. The constructor’s GF API calls inside individual handlers are guarded with class_exists( 'GFAPI' ) — so GF must be loaded for any work to happen.

Activation is therefore a two-part check: entitlement (managed by MAM Suite) and presence (Gravity Forms loaded).

Steps

1. Confirm Gravity Forms is active

Go to Plugins → Installed Plugins and confirm Gravity Forms is Active. If it isn’t, activate it before proceeding. The MAM Suite plugin will not throw an error if GF is missing — but no GF forms will appear and no entries will be created.

2. Activate the plugin in MAM Suite

Go to Mobile App Manager → Software. Find MAM Gravity Forms Manager in the list and click Activate. The plugin’s entitlement state will be checked against your MAM Suite license; if it’s not included in your entitlement, contact Tiny Screen Labs.

You’ll see no confirmation banner — there is no admin page to land on. The activation is silent.

3. Confirm GF forms appear in MAM dropdowns

The fastest end-to-end check is to open any MAM screen that asks “which Gravity Form?” and confirm the form list is populated.

Go to Mobile App Manager → App Settings, pick a role, and look for any Gravity Form dropdown — for example under General Settings if any feature plugin has registered one (Special Offers, Edit Listing, User Profile, etc.). The dropdown should list every active Gravity Form on the site.

If the dropdown is empty:

• Check that you have at least one form under Forms → Forms in Gravity Forms.
• Check that the form is not in the trash and has not been deactivated within Gravity Forms.

4. (Optional) Confirm the version compatibility check passes

mam-gravity-forms-manager checks the running mam-main version on every admin_init. If mam-main is below 1.9.1, an admin alert is logged via mamdebug. Visit Mobile App Manager → Debug (if your install exposes debug output) to confirm there are no MAM Forms requires version 1.9.1 or higher entries.

Verification

To confirm the full pipeline is wired, submit a test entry from any feature that uses the plugin (e.g. an app-side Special Offers form, or a Contact Us form on the GF path):

1. Submit the form from the mobile app or from the WordPress front end.
2. Open Forms → Entries in Gravity Forms.
3. Confirm a new entry appears, dated within the last minute.
4. If the form has a notification configured, confirm the email arrived (check spam if not).

If an entry doesn’t appear, see Common gotchas below.

Common gotchas

• GF deactivated, plugin still “active.” The plugin loads but every GF API call is gated on class_exists( 'GFAPI' ). With GF off, the plugin is silently inert — no errors, but also no entries, no notifications, no form list. Always check GF first when something stops working.
• Entitlement state of blocked or expired. The constructor exits early on 'blocked' and skips update registration on 'expired'. An expired license still runs the integration, but the plugin won’t auto-update. A blocked license disables the integration entirely.
• No admin UI. This plugin contributes no settings page, no custom post type, no menu entry. If you’re looking for “where do I configure mam-gravity-forms-manager,” the answer is: you don’t — its consumers (other MAM plugins) do the configuration.
• mam-main below 1.9.1. The plugin still loads its hooks, but some downstream MAM behavior may be missing. Update mam-main first.

Variations

Use a Gravity Form to back an in-app feature

See Recipe: Add a Gravity Form to your app.

Hook a web submission into a custom post type

See Recipe: Route a web submission to a custom post type.

Verification

This article was last verified against:

• Plugin: mam-gravity-forms-manager v2.3
• mam-main v1.9.1+ (required for the version compatibility check)
• Gravity Forms (required)

Re-verify whenever the entitlement filter (mam_plugin_entitlement) gating in mam_gravity_forms::__construct() changes, the required mam-main version (1.9.1) in check_version() changes, or the Software list label or activation flow in mam-main changes.

Related articles

• Plugin overview: mam-gravity-forms-manager
• Recipe: Add a Gravity Form to your app
• Recipe: Route a web submission to a custom post type
• Hook: mam_gf_get_form_settings

Metadata