Verify script implementation

desktop and mobile web environment

  1. Open your browser’s Developer Tools and go to the Network tab.
  2. Apply a filter for the relevant script or resource (e.g., brandmetrics).
  3. Navigate to a page where the script should be delivered.
  4. Verify that the script request (e.g., your_site.js) is present and returns 200 OK.
  5. After the initial script request, check for a request to a numeric bundle script (e.g., 65568.js) and ensure it loads successfully.
  6. Once the bundle is loaded, you may see a collector request (e.g., c.js?site…), which is used by the script for survey-related checks.
  7. If you can confirm that these three requests occur in sequence, your implementation is likely functioning correctly.

image.png

Force a survey

Normally a survey only goes to a user who has been exposed to the campaign and falls in the frequency group we want to retarget. _forcesurvey skips those two checks so you can test the survey flow without being exposed first.

It does not skip the measurement setup. The measurement still has to be active with surveys switched on for your test site, otherwise the backend answers "Survey is not active" and nothing happens.

Before you start

  1. Select or create a measurement that is active (green in the Portal).
  2. Activate surveys in the Portal. On the Survey Configuration tab, set “Show surveys in” to the site you want to test on. Do this in the Portal, not the Measurement Hub; the Hub edit modal doesn't have the activation option for new collection measurements yet.