The CMX Engage is a location intelligence, digital customer acquisition and multi-channel engagement platform that enables companies to connect, know, and engage with visitors at their physical business locations.
The major features of the CMX Engage 3.2.11 release are as follows:
Age Gating support for captive portals.
The following new features are added to the CMX Engage Runtime:
GDPR-Age Gating Support
The CMX Engage captive portals now support Age gating. This feature enables you to restrict customers below certain age accessing the internet through your captive portals. For a captive portal, you can configure any of the following methods for specifying the age:
Strict Mode : During customer acquisition, the customer has to specify the month and year of the birth to access the internet. If the customer provides the age as less than 16, an alert message is shown, and the customer cannot proceed further to access the internet. However, the customer will be provided an option to change the date of birth, if required.
Moderate Mode : During customer acquisition, the customer has to acknowledge that the age is 16 or above to proceed further.
Currently there is no dashboard support for this feature. You can contact the CMX Engage support team to avail this feature.
The following enhancements are made to the CMX Engage Dashboard:
Network Synchronization Server
The CMX Engage now supports to configure Meraki domains for various regions so that it can synchronize with Meraki in all regions. Certain regions such as US and China have specific Meraki domains, and the CMX Engage to synchronize with the Meraki needs to support these domains.
CMX Engage Runtime
The following enhancements are made to the CMX Engage Runtime:
Tags for Captive Portals with No Authentication
The Captive Portals configured with “No Authentication” now support the tags selected or defined in a Captive Portal Rule. This enhancement helps you to group and target devices with the tags applied to them. Previously tags configured in the captive portal rules were not supported for captive portals configured with "No Authentication".
Table 1 Resolved Issues in the CMX Engage 3.2.11
CMX Engage Dashboard
For Engagement Rule, for Trigger API, the data format displayed in the “Json Data” text box is incorrect.
Table 2 Open Issues in the CMX Engage 3.2.11
There are no open issues for this release.
You can access the support documentation using the Help button in the CMX Engage Dashboard.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.