Trigger Rules

Tag Manager fires a tag, like an analytics snippet or an ad pixel, only when a trigger condition is met, such as a page load or a button click. A Beam agent watches the account's tag firing history and, under an approved rule, checks that expected tags are firing on the pages they should. It does not set up new triggers itself. A tag that stops firing on a page where it used to, or one firing on pages it should not touch, is routed to a person to check the trigger setup and correct it in the container.

Container Versioning

Every change in Tag Manager is saved as a new version of the container, which can be published live or rolled back. A Beam agent reads the version history and, under an approved rule, ships a pre-approved version to the live container at a scheduled time, such as after a marketing team signs off on a change in a linked ticket. It does not edit tag configurations itself. A version with an unresolved warning, or one nobody has signed off on in the linked ticket, is routed to a person before it goes live.

Preview Mode

Preview mode lets someone test a container's tags on a live site before the change goes out, showing which tags fired and with what data. A Beam agent checks the preview results attached to a pending version and, under an approved rule, confirms that the expected tags fired correctly before flagging the version as ready to ship. It reports the preview outcome rather than approving the change itself. Any preview showing a tag misfiring, or a required tag missing entirely, is routed to a person to fix before the version moves forward.