Google Tag Manager Installation
Create a draft, review it and publish the GTM container yourself.
Content and code last checked 2026-10-06 by ConsentEase product documentation. This is a review of the written content and code, not a test on a live third-party platform.
Guided installation
Open Installation → Google Tag Manager for the selected website. Connect a Google account with access to the intended GTM account/container. Review the requested permissions; a successful OAuth connection does not publish anything.
Review the proposed changes
Follow the wizard and inspect the ConsentEase template/tag, website public ID, trigger and consent configuration. Initialize consent before tags that depend on it. The official workflow is based on the GTM consent template; template availability/review and a saved draft are not proof that your production container changed.
Test before publishing
Use GTM Preview/Tag Assistant to inspect defaults, updates and tag consent checks. Test Google and third-party tags separately. Confirm no competing consent tag or manual/plugin banner remains.
Publish explicitly
Review the container changes and publish a version in GTM yourself. ConsentEase never automatically publishes the container. A connected account, saved template or wizard completion must not be treated as a live runtime verification.
Maintain the connection
Use the account/container that owns the installation. Reconnect if access is revoked or tokens fail. Re-check published versions after another administrator edits the container. Agency Google access and client website management are separate permissions.
Read the separate Consent Mode guide for Basic versus Advanced expectations. Neither mode is automatically a legal approval.
Verify the published site
Use separate fresh browser contexts for no choice, accept, reject and custom preferences. Check tag consent requirements, network traffic, storage and reopening preferences. Test relevant routes and mobile layouts. A theme installation does not prove coverage of checkout, embedded frames or hosted third-party pages.