During the January 7, 2026 kickoff call, the Asymmetric team identified and resolved a Google Tag Manager permissions issue that had been blocking all tracking setup. With access corrected, the plan is to implement a clean tag stack via GTM and remove legacy tracking code embedded directly in Webflow's custom code settings.
Related context: [1] | [2]
AviaryAI's GTM account had been shared with the Asymmetric team at Read permission level, which prevented creating or editing tags. During the call, Justin Dwyer updated the container permissions to Admin, unblocking all tag work.
"We're going to create a Google tag here, we're going to create some GA4 tags, we're going to create a Clarity tag, we're going to create, you know, six or eight tags, and we'll configure them all and set them here." — Mark Hope
How to log in: Use the team Google account credentials. The GTM container is listed under the AviaryAI account.
Webflow access was also restricted on initial login. The fix: always use "Login with Google" when accessing the AviaryAI Webflow workspace. Logging in via email/password results in reduced privileges and no access to site settings or custom code injection.
| Tag | Purpose |
|---|---|
| Google Tag (base) | Foundation tag; connects GTM to Google properties |
| GA4 Configuration | Sends pageview and event data to the new GA4 property |
| Microsoft Clarity | Session recording and heatmap data |
| Additional tags | To be added as needed (e.g., LinkedIn Insight, ad conversion pixels) |
The GA4 property is new — there is no historical data. All baseline metrics begin from the point of implementation.
Prior tracking snippets were added directly to Webflow's Site Settings → Custom Code section (head/body). These include:
Action: Replace all legacy custom code with the single GTM container snippet. All tags should be managed through GTM going forward — not hardcoded into Webflow. Confirm with Justin/Aaron before removing the Apollo tag, as Aaron confirmed it is still in active use.