Click on the mGage box under the Available SMS Service Providers (SSP) section. In the configuration modal, enter the following information of your mGage account: Host, Port, Aid, Pin.

You will also have to name the configuration on WebEngage to identify the added SSP account. Please choose any user-friendly name for the Name Your Configuration field. The Configuration Name helps you identify the relevant SSP account you should use during the SMS campaign creation process (especially helpful when you have multiple accounts with the same SSP that you have configured and added to WebEngage).

As soon as you have added mGage as an SSP in WebEngage, there are a few more steps remaining before you can start using mGage as an SSP in WebEngage. You will have to copy the WebEngage Webhook in mGage so that WebEngage can start receiving delivery and failure information about your messages from mGage. To do this, open the menu for your the mGage configuration on WebEngage and click on the View Webhook URL link to view and copy the Webhook.

In your mGage dashboard, navigate to the Settings section and paste the Webhook URL in the relevant field and save your settings.

Updated 8 months ago


mGage


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.