Google Tag Manager - v1.0.0

Every class, facade, directive, and route the package exposes.

Top-level

• GoogleTagManager facade — googleTagManager() helper and static access
• SnippetRenderer — the class behind @gtmSnippet
• TagManagerClient — the Tag Manager API v2 client
• Fetchers — ContainerOverviewFetcher and TagListFetcher
• Data Objects — the typed DTOs returned by the client and fetchers
• HTTP Routes — the endpoints backing the React and Vue components
• Blade Directives — every @gtm* directive
• CmsFramework wrappers — the ContainerOverviewWidget and TagListWidget classes
• Exceptions — ApiException and BaseNotInstalledException

Package boot flow

The GoogleTagManagerServiceProvider boots in this order:

1. mergeConfigFrom on the package config
2. Binds SnippetRenderer, TagManagerClient, GoogleConnectionResolver, and GoogleTagManager as singletons
3. Publishes config, views, and js groups
4. Loads the package's Blade views under the google-tag-manager:: namespace
5. Registers the @gtmSnippet, @gtmSnippetHead, @gtmSnippetBody, and @gtmRoutes directives
6. When the base is installed and routes.enabled is true, loads the HTTP routes
7. When the base is installed and the hooks helpers exist, contributes scopes via the ap.google.scopes filter
8. When Livewire is installed, registers google-tag-manager::container-overview and google-tag-manager::tag-list
9. When both cms-framework and Livewire are installed, registers the CMS admin widget wrappers on the CMS AdminWidgetManager (deferred until booted)

Every "when X is installed" branch degrades silently — the package boots cleanly on hosts without the base package, Livewire, or the CMS framework.

Related

• Testing — writing tests against the API surface
• Configuration — the config keys these classes read