AviaryAI GTM, GA4 & Clarity Implementation
Overview
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]
Access Resolution
Google Tag Manager
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
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.
Implementation Plan
Tags to Create in GTM
| 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.
Legacy Code Cleanup in Webflow
Prior tracking snippets were added directly to Webflow's Site Settings → Custom Code section (head/body). These include:
- An old GA4 snippet tied to a previous property
- A legacy Apollo tracking tag (still in use by Aaron for sales, but secondary to Asymmetric's work)
- Possibly other orphaned tags
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.
Key Decisions
- GTM is the single tag management layer — no tracking code should be added directly to Webflow custom code going forward.
- Apollo tag: Leave in place for now; Aaron uses it for sales call recording. Coordinate before touching.
- GA4 property is net-new — no data migration needed, but stakeholders should be aware there is no historical baseline.
- Clarity is included in the initial tag rollout alongside GA4.
Action Items
- [ ] Implement GTM container snippet in Webflow Site Settings → Custom Code, replacing legacy tags (@Mark Hope)
- [ ] Create GA4 Configuration tag in GTM and publish (@Mark Hope)
- [ ] Create Microsoft Clarity tag in GTM and publish (@Mark Hope)
- [ ] Create base Google Tag in GTM (@Mark Hope)
- [ ] Confirm with Aaron before removing or modifying the Apollo tracking snippet (@Mark Hope)
- [ ] Verify all tags are firing correctly via GTM Preview mode and GA4 DebugView
Notes
- The AviaryAI GTM account had an unusual state: the account-level role was set to Administrator but the container-level permission was Read. This is a known GTM quirk — account role and container permission are set independently.
- Webflow stores custom code per-site under Site Settings → Custom Code. There may also be page-level custom code on specific pages; audit both locations.
- AviaryAI's DNS is currently at GoDaddy. If Google Search Console verification is needed via TXT record, email the record details to Justin Dwyer and he will add it manually until the [3] is completed.