Define the interaction
Before configuring a tag, describe the action you want to observe. A click on a CTA, a valid form submission and an order confirmation are not the same thing. Write down when the event must happen, and when it must not.
Separate the roles
The site describes what happened, the trigger identifies the condition and the tag handles the intended dispatch. Keeping these steps apart makes it easier to tell whether a problem starts in the interface, in the data or in the configuration.
Try a negative case
A useful check also includes an action that should not produce the event. For a form, try a missing field; for an order, try a refresh. Record the expected and observed results in a checklist.
THINK IT THROUGH
From the concept to a concrete case
Pick a page of the laboratory. Which interaction do you want to observe? Write the event name, two parameters and one case where it should not fire.
Download the checklist ↗