Debug a marketing tag that never fires

A signup form succeeds, but no conversion event appears in your debugging session. Repeatedly pressing Publish in the tag manager does not reveal which condition is failing.

Why this happens

The tag may be in the wrong container, the trigger may not match the actual event, or consent requirements may prevent execution. A form that submits through JavaScript may not emit the browser event you assumed.

Step-by-step solution

1. Confirm the page contains the intended container and that you are testing the correct environment and published version.

2. Use preview mode to inspect the event timeline. Check the exact trigger variables and compare them with the values produced by a successful submission.

3. Trigger the event only after the application confirms success. Inspect consent requirements and blocked tags without bypassing the visitor’s choice.

Worked example

If the application emits signup_success but the trigger expects form_submit, align the agreed event contract. A button click alone is insufficient because validation or the server may still reject the form.

Verify the fix

Run one successful signup and one rejected submission. Only the successful flow should send the intended event, with no duplicate requests.

Prevent a repeat

Keep test cases for client-side validation, server errors and single-page navigation. Preview the final published container, not only an unpublished workspace.

Reference

Official documentation or standards guidance

An original Gistmax troubleshooting guide. Scenarios and sample values are illustrative; configuration depends on your software version and environment. Cover diagram: Gistmax Tutorials.