Find integration errors without changing statistics

Measurement debugger checks whether a proposed event would be accepted for an owned counter. It does not send a normal event or increase visitor, goal, event or revenue totals. This makes it useful for configuration errors while keeping the distinction between a diagnostic result and a real measurement.

Run the first diagnostic check

1. Connect the counter through My counters and open Dashboard and tools.
2. Open Measurement debugger. Enter a stable value in Event name, such as signup for a manual event.
3. Select the matching Measurement type and whether the event name is automatically generated. A form success and a manual event use different settings.
4. Leave Predefined properties (JSON object, optional) as {} unless predefined properties are actually configured. Never enter form contents or personal information.
5. Choose Test without counting and read the result and normalized event name.

Interpret a rejection before changing code

A disabled automatic category requires enabling the corresponding measurement setting. An invalid or personal-looking name requires a stable category name rather than a visitor identifier. A new-name limit means that repeatedly inventing event names will not solve the problem. Check the result shown on the page instead of assuming all failures are network errors.

Properties must match the predefined configuration. The diagnostic reports their acceptance without echoing submitted values. Goal information distinguishes a matching goal from a counted human visit: a configured goal alone does not guarantee that a goal visitor would be added.

Test the diagnostic connection from the website

1. In Test on your website, use Copy test code to copy the generated diagnostic code.
2. Open the owned website that contains the counter and run that code in browser developer tools as described on the debugger page.
3. Read the console result. The generated test permission expires after fifteen minutes; reload the owner debugger page to obtain a fresh one when needed.

Use the generated temporary permission, not the private owner key in a handwritten script. Changing the owner key also invalidates the diagnostic permission. The diagnostic endpoint uses a request limit, but it does not create normal tracking data.

Check the normal integration separately

An accepted diagnostic means the proposed event would be eligible at that moment. It does not test the normal tracker’s rate limit, later database writes, a browser blocker affecting the normal request, successful form processing or ordered funnel progress.

1. Inspect whether s4u.js loads on the intended website page and whether normal tracking requests are blocked or fail.
2. Check the counter number, enabled category and report date range.
3. For a form, confirm the application’s actual successful processing before expecting its success event.

Keep the diagnostic result and the normal request result separate in any error report. A missing measurement cannot be explained reliably by a single green diagnostic response.

Next step

Open the owned counter and start with a diagnostic event that contains no personal data.

Open My counters