Apr 4, 2019 — Updates to mPulse and Real User Monitoring (RUM)

The latest Property Manager release includes the following changes for RUM customers:

For new properties, the mPulse behavior is automatically turned on in the property configuration with a default (blank) mPulse app API key. Leaving this mPulse API key blank automatically creates a new mPulse app that corresponds to the property. After the property is active on the Akamai production network, all of your data (beacons) are directed to your mPulse app. mPulse replaces all product templates that previously had RUM as the default behavior with mPulse (with the default API key).

If you have RUM on an existing property, and wish to use mPulse, remove the RUM behavior from the property.

RUM and mPulse should not coexist on the same property. If you choose to use both RUM and mPulse, you need to explicitly provide an API key for the mPulse behavior. To locate the API Key of an existing mPulse app, log in to mPulse, select the mPulse app from the Home page, then click the General tab to view the API Key.