A tag can fire without producing the data your report needs. It can send the wrong event, omit a parameter, or send the same action twice. Checking only the tag status leaves these failures unresolved.
A useful tracking check follows one controlled action through the system. Establish what should happen, inspect each stage, and stop at the first difference between the expectation and the evidence.
Write an expectation that can fail
Consider a hypothetical website with a downloadable CSV report. The requirement is to record report_export when the application confirms that an export is ready. The event must contain export_format with the value csv. This is an illustrative specification, not a tested implementation.
Use three cases: one successful CSV export, one rejected export, and one successful PDF export. If the requirement covers only CSV, the expected number of report_export events is one. Neither a button click nor an unsuccessful attempt meets the success condition.
Record the test environment, browser, consent state, container version, destination measurement ID, and approximate action time. Use non-sensitive sample data. Keep each case separate so that unrelated visitors and earlier actions cannot explain the result.
Separate the website event from the tag
Start with the website’s evidence of success. In this example, the application could push report_exported to the data layer when the export is ready. Inspect that message at the relevant action. Confirm that export_format belongs to this event and has the expected value.
If the success message is absent, investigate the website integration before changing a GTM trigger. If the message contains pdf after a CSV export, the trigger cannot repair the incorrect source value. A stale value from an earlier action can also make a tag appear correct.
Next, select that event in Tag Assistant. Inspect the trigger conditions, resolved variable values, and fired or unfired tags. Google’s explains how to inspect firing and processing. Preview can use the current workspace draft, so record which configuration you are testing.
