Consult these guidelines if Script Management is not behaving as expected.

Empty dashboard

If no beacon data is available the View and Edit Configuration table on the Script Management dashboard will be empty. To resolve this issue check that both Script Management and mPulse are enabled in your Property Manager configuration, and that the configuration is activated in production. Once you confirm that both are enabled allow some time for data collection. If the table remains empty, contact customer support.

Missing data in the dashboard

Previously, those scripts generated enough beacons for Script Management to detect them, and the policy deferred or blocked them. In the most recent data collection period, however, there are not enough beacons to provide data.

Scripts not deferred or blocked

If the policy is not in effect or the service worker is not functioning scripts that the policy should defer or block might be allowed to run on your site.

  • Check that the browser you are using supports service workers.
  • Check that the policy is active in the environment where you are testing (staging or production).
  • Check that you are testing on the same hostname selected in the policy.
  • Confirm that you followed all of the instructions correctly when you enabled Script Management in your Property Manager configuration.

After to perform these checks, allow a few minutes for the policy to propagate and reload the page in the browser. If this does not resolve the issue, contact customer support.

A script set to No Action stops working

If functionality on your site stops working, although the script that runs it is set to No Action in the policy it might be because one JavaScript is referencing another. The script that you want to run might be dependent on a script that you blocked or deferred.

Slow network simulation stops working

If some functionality on your site stops working only when simulating a slow network connection Single-Point-of-Failure Protection might be intervening with scripts because of the network conditions.

Check the timeout range limits, located in the Advanced settings:

  1. Disable Single-Point-of-Failure Protection.

  2. If that resolves the issue, increase the lower limit of the timeout range and re-enable the policy.